PD#174543
PD#172587
Problem:
new added function for tl1
Solution:
add vdin afbce support for tl1
Verify:
verified on PTM
Change-Id: I42054b8228161713ac10446491ebdb50a71975ad
Signed-off-by: shihong.zheng <shihong.zheng@amlogic.com>
PD#172587
Problem:
do not suppoert for tl1
Solution:
add backlight support for fl1
Verify:
verified on PTM
Change-Id: I052a7ef93ec9cb21a544e4823a4c9a339d38b5f9
Signed-off-by: Evoke Zhang <evoke.zhang@amlogic.com>
PD#172587
Problem:
not support tl1
Solution:
add tl1 support
Verify:
test pass on PTM
Change-Id: I5a9073fc08a98ae95d4961297a7427864d92279b
Signed-off-by: Evoke Zhang <evoke.zhang@amlogic.com>
PD#SWPL-848
Problem:
ioctrl set the same gamma value again
Solution:
if the gamma value is same as the ioctrl userspace value, do not set again
Verify:
txlx
Change-Id: I6f17f5ff234513c5a886004aedea81b9945c5b98
Signed-off-by: Bencheng Jing <bencheng.jing@amlogic.com>
PD#172438
Problem:
1. return a negative when parsing the dts property
"output-high/output-low"
2. the prefix "bt565" don't meet corepinmux document
Solution:
1. add break statement in case PIN_CONFIG_OUTPUT to avoid
returning a negative value.
2. rename the "bt565" to "bt656" according to corepinmux document
Verify:
test pass on U200
Change-Id: Ieeb98367e2269007a6774592abac86ef05ee8f64
Signed-off-by: Xingyu Chen <xingyu.chen@amlogic.com>
PD#SWPL-922
Problem:
the existing gpio IRQ driver(porting from the upstream) does not
double-edge detection
Solution:
add a new gpio IRQ driver to support the double-edge detection,
the new driver is with different software structure but compatible
with functions of the existing driver
Verify:
test pass on s400
Change-Id: Id69dd0b4459eef20a6755947c7d95a24d7b17fa9
Signed-off-by: Xingyu Chen <xingyu.chen@amlogic.com>
PD#SWPL-869
Problem:
new feature, add hdr10 plus support
Solution:
1. add hdr10 plus metadat parser
2. add hdr10 plus code support
3. add hdr10 plus bypass mode
Verify:
verify on U200
Change-Id: I957954ce148021882e17f2913dd2552e64f1298c
Signed-off-by: MingLiang Dong <mingliang.dong@amlogic.com>
After reduce the size of boot loader area to fit in 1MB, MPT partition table
can be fit at 2048 LBA and this partition table would be used by Android
for numerous partitions other than Linux based platforms.
Change-Id: Ic8b8defedb4103abf547bae7f533036904578b59
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
To fix an issue caused by the initialization process
of framebuffer console driver with built-in option
(CONFIG_FRAMEBUFFER_CONSOLE=y)
Change-Id: I8a84f206b1f73776ccc188193aa217d39d61f16f
The 'MPT' partition table is non-standard type which contains the partitions
at certain blocks on eMMC device to provide many partitions more than MBR
partition. When this partition table is discovered, standard partitions
such as MBR are ignored such that only the partitions from MPT are valid.
But there is a kernel crash bug when 'MPT' partition table is not exist.
This patch will check if 'MPT' partition is exist while checking its magic
number and proceed further more if it's valid.
Since Android needs to use 'MPT' partition, this cannot be simply eliminated.
Change-Id: Ic27fef3e28eab009affbb0f11a12472d58a373f6
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
After reduce the size of boot loader area to fit in 1MB, MPT partition table
can be fit at 2048 LBA and this partition table would be used by Android
for numerous partitions other than Linux based platforms.
Change-Id: Ic8b8defedb4103abf547bae7f533036904578b59
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
Conflicts:
drivers/mmc/card/block.c
It has two main use cases:
1) Allow drivers to reset their hardware via a GPIO line in a standard fashion
as supplied by the reset framework.
This allows adhoc driver code requesting GPIOs etc to be replaced with a
single call to device_reset().
2) Allow hardware on discoverable busses to be rest via a GPIO line
without driver modifications.
Examples of the second use case include:
* SDIO wifi modules
* USB hub chips with a reset line
In this second use case the reset has to be done externally to the driver
managing the hardware since resetting the device from the driver's probe()
method will either do nothing (if the device needs to be reset before
ennumeration will work) or cause racy beahviour (when the device disappears
from the bus during probe()).
So, in addition to providing a gpio based reset controller implementation
it is also possible to reset devices at boot via a DT property or from
userspace on request via sysfs attributes.
Change-Id: I316f9e622d99cff7167b57e8fd5ff73a34dc2a81
Signed-off-by: Martin Fuzzey <mfuzzey@parkeon.com>
Signed-off-by: Kevin Kim <ckkim@hardkernel.com>
