rk808 setting voltage had a overshoot question
so we set voltage must step by step.
support 12.5mv/step.
Change-Id: Idfce7b57d6717e51afaff2c170eff7bd16de23af
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit cccf1792d7b70cffa3d2f424cdf4dafa50729741)
If we direct to use primary screen to init extern screen, the dsp_lut
is not NULL, this will lead to enable gamma lut.
Change-Id: I0934d57927b4b031a4484630120e3be0cfb14969
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit b8ad7796e40a74af85295ac900ddc3e58bdfb49c)
If the lcd dtsi file doesn't define dsp_lut and user open BizLineAdjust.apk
to adjust brightness or contrast will lead to display issue, now fix it.
Change-Id: Ieac8e8bb497b3c750b94cf23830524477153a717
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 01d294f51fa76b01605498ba1b4935ae5448ff47)
dclk_lcdc set freq error,when lcdc1 as PRMRY(LCD),
lcdc0 as EXTEND(HDMI).
the software only consider the lcdc0 as PRMRY(LCD),
lcdc1 as EXTEND(HDMI)
Change-Id: Iebe1bf94ad61e030a8dffe6c55c0cd8485a6b311
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit dd3e226d1769dbbd06c66714cde2f2f5c29eaf16)
when lcdc1 and lcdc0 the same clk source,
set dclk_lcdc1 will recalculate the clk cpll,
then make the dclk_lcdc0 change.
Change-Id: Ie166ea21da2235a03e3fdb3e0e55e67c8594f1b9
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 6f1511438970ae12f9efb6b68042362a6403ad3d)
The power off sequence is behind of i2c bus shutdown func,
it would prevent the rk818 to do power off action. The irq was
disabled when rk818 power off, it could let rk818 to power off
through i2c bus.
Change-Id: Ia6155f137ab2fa36dbe19e06878b0228670b1398
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 67e6de73b6b9336ef515c4d5a075251fb94ff6dc)
If parsing 1st block edid failed, we think it is good
only when there is more than one external block.
Change-Id: I1eb11405dade41ebb2ad041ba909de0c7ea120f8
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 1d9b35e9d10839a9d513eed551034fd02e855f92)
When multiple same type display interface is registered, such as TV, named TV, TV1, TV2.
Change-Id: I33f7e12c4942c3bf7eb29cca8ef6037f9e78d1af
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit c196bbf342cdee23591522a545db6c42d9a008ea)
There is no difference between mid and box on setting
RK_FBIOSET_CONFIG_DONE.
Change-Id: I8a454a318ad8663b5e0f94ac05c067c6b386801a
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 495b4a8232528251ee9276964014d6dd87e3ee22)
If hdmi_submit_work work in synchronous mode, the malloced delayed_work
is free by caller, not by hdmi_work_queue, to prevent delayed_work is
free before flush_delayed_work fucntion is executed.
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 71a461a76455cc8b3082c0125f5d0be3287f1420)
if rk818 driver's shutdown func called, it should not do i2c transfer.
And rk818's shutdown func is behind of i2c driver's shutdown func.
Change-Id: Iec96ad4640894f604493d8c764a2f98e75397885
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit d07484d381d9c7ffa79745b345aa2af35582a8fb)
If hdmi is inserted or removed before android is launched, screen
size is changed and uboot logo is showing on wrong screen position.
For example, screen size is 720x576 in uboot, hdmi is inserted during
kernel is booting, screen size is changed to 1920x1080, logo size
is still 720x576 and shown on left-top.
This case is occurred on box, mid has no problem. So we need to resize
uboot logo to new screen size.
Change-Id: I6247bf8e77d181687986815c960ec72d4c59a757
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 92e7da2818b9dd75d125d017898e30ec4f9c9ee0)
dev_set_name()
When we use of_device_add() to create platform_device and add it to device
hierarchy, the platform_device.name and device's name will point to the same
memory.
Later we use dev_set_name() to change the device's name, it will alloc new
memory to store name and free old device's name. After it, the
platform_device.name will point to an freed memory, access platform_device.name
maybe lead to unpredictable exceptions.
So, we alloc new memory for platform_device.name in of_device_add()
Change-Id: I59bf0941ee4e094053971d41d386206e47fddcaa
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit a51927d3ac36b6f5ec741040d7b694e73f0fbeaf)
Thinking about the PWM remote-ctrl is used by box, we should
put this into box dts.
Meanwhile, that PWM configure will break the normal PWM driver.
This patch will fix it.
Change-Id: I14878332631f94f512412ced5ceb8689f8bfbe46
Signed-off-by: Firefly <service@t-firefly.com>
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 74a24fe1b7e7529f618c32b085177f2be3394c6b)
We are assuming that PWM need use the property, we can support the
SPI interrupts for PWM.
At the moment, we can find the remotectl pwm is needed on box.
We can add the property for all PWMs. AFAIK, the pwm driver don't use it
but the drivers/input/remotectl/rockchip_pwm_remotectl.c
Change-Id: Ia223e6cc0e882477614b555bd09c86fd4bf8dbd7
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 16b7b284618d1652e694f6286f575ce82f5f03e5)
If uboot_vic has HDMI_UBOOT_NOT_INIT flag, it means uboot just
pass the preset vic value, registers has not been set in uboot.
If not, hdmi has been power up in uboot, should not operate phy
register again.
Change-Id: I64f48bd878ec124a94f25a752a74dc9bae502b2b
Signed-off-by: Firefly <service@t-firefly.com>
(cherry picked from commit 468345a5026c858f295dedfc5644c8b63a5948c8)
