hw dev_lock for multi device such as mainpath and selfpath output
Change-Id: I905040fee2836e4cc3e36f2bf523f45bb5b226eb
Signed-off-by: Cai YiWei <cyw@rock-chips.com>
Since there is no txdone irq in the Rockchip mailbox IP, invoking
mbox_chan_txdone()/mbox_client_txdone() after mbox_send_message()
to tick the TX would be free the active request which have not been
sent out if the controller returned the EBUSY state before. So amend
the txdone method to polling to fix it.
The TX polling interval can specify in DT with
"rockchip,txpoll-period-ms" property, if it is not set, the driver
would hardcode to 5 milliseconds.
Change-Id: Ic26d3245dd8bd90ebad30fce9ece2f4452814f7f
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
Specify TX Done polling interval in milliseconds with the
"rockchip,txpoll-period-ms" property.
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
Change-Id: I91f25e6b5e6ef05cf90147b2e609c71c6ed61df7
If no need to activate the decompress flow, using CONFIG_ROCKCHIP_THUNDER_BOOT_MMC
should be better.
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
Change-Id: Ic9750ab71cc0d7c5beddd41f11ab71aa4df69bff
when rtk(also some others) wifi/bt combo chips suspend, it
disconnect from bt-remote control unit(RCU). when RCU's
powerkey pressed, it will send ble broadcast to rtk bt chip.
As the rtk chips receive the broadcast, it should wake up
the host, but it can't send bt-hid powerkey to host because
it had lost communication with host.
So,it just send a IRQ pulse to host. The host should resume
from suspend.
Because the RCU just send a IRQ pulse, so rk chips just resume
by IRQ and then go to sleep again for no power-key event.
this is not expected. we expect to power up system wholly.
With this path, we try to power up the system. so we add a
power-up key event when BT IRQ received.
We also can control the "/proc/bluetooth/sleep/powerupkey"
node to enable or disable this function.
Change-Id: Ie59b4a2c4cd2f91820d31835df86565003126465
Signed-off-by: Zou Dengming <marsow.zou@rock-chips.com>
When the hdmi is plugged in and out after uboot but
before kernel initialization, the TV will enter hdmi 1.4 mode,
hdmi 2.0 resolution can't be display.
In this case, we need to disable/enable hdmi again to make TV
into hdmi 2.0 mode again.
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
Change-Id: I39fbe519d54329ae7db57904013bfdef6f5a068e
HWC will set hdmi out of hdr mode then disable hdmi
when hdmi plug out in hdr mode.
If hdmi is disconnect edid is null, mode valid check
is always failed, HWC set hdr disable will failed.
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
Change-Id: I12ebf23539be17b338617131e879296ed20d6a95
The former ECC fail return value -1 is not the correct one, change
to return 0 and let the nand base handle it. The mistake value
causing file system to be unable to detect the ECC fail status and
unable to make corresponding optimization processing.
Change-Id: Ib79d02189de383fa9815cf0524e6bcb89b3c939f
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>
If the controller is powered down and lost its settings of
MSI, host driver should take response of recovering all the
settings.
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
Change-Id: I9f1fd9078e500388f8d9753cc5ab7882b404d142
At VOP3_ESMART_2K_2K_2K_2K_MODE mode, esmart can support:
4k scale down to 2k or 2k scale up to 4k, but can't support 4k to 4k,
current property[INPUT_WIDTH/INPUT_HEIGHT/OUTPUT_WIDTH/OUTPUT_HEIGHT]
can't accurately describe this feature, so we agreement on rules with hwc:
1. when esmart can support 2k->4k/4k->2k, can't support 4k->4k, the property
value is:
INPUT_WIDTH:4096
OUTPUT_WIDTH:2048
2. when esmart can suport 2k->4k/4k->2k/4k->4k, the property value is:
INPUT_WIDTH:4096
OUTPUT_WIDTH:4096
Signed-off-by: Sandy Huang <hjc@rock-chips.com>
Change-Id: If2067f34a36ba77249174e8369eaaccb0a8f700f
vop2->esmart_lb_mode is correct value according driver default value and
dts config.
Signed-off-by: Sandy Huang <hjc@rock-chips.com>
Change-Id: I1c242ebbb47cdf2916a56ae729ba65222d31d0d5
