Compatible with cif only have single dma mode in driver
Change-Id: I5f2296549e20e3db1d8883474936e2892afc3ff0
Signed-off-by: Xu Hongfei <xuhf@rock-chips.com>
64bit SoCs with 32bit code need some different configs, eg. textofs...
So we need a independent defconfig.
Change-Id: I76b6259078991d2936a568b43fe1ed67247de995
Signed-off-by: Liang Chen <cl@rock-chips.com>
This patch tuning lane 0 TX driver swing for USB 3.0 to
get larger swing for LFPS.
Test on RK1808-stick board:
offset[0x21b8] 5G LFPS Peak-Peak Differential Output Voltage
0xd9 Actual Value: 807.9mv Margin: 2.0%
0xe9 Actual Value: 832.2mv Margin: 8.1%
0xf9 Actual Value: 842.7mv Margin: 10.7%
We set PHY register offset[0x21b8] to 0xe9 in this patch.
Change-Id: Ic1878fbea5c0b67ce943544e9d9afdf912341b45
Signed-off-by: William Wu <william.wu@rock-chips.com>
When the clients are 32 bits while the kernel is 64 bits,
we need to translate the memory address before accessing.
The previous commit was refreshed by ddk update.
Change-Id: I7f47ab94da258e9d170613252aae9b396623cf48
Signed-off-by: Randy Li <randy.li@rock-chips.com>
Client applications are forbidden to run before supplicant
application is ready. Detection of supplicant application
status is added at the entry of open operation.
Change-Id: Ief4106bcd75251790b82d76e4d69092900af29e3
Signed-off-by: Elon Zhang <zhangzj@rock-chips.com>
According to commit "mmap: introduce sane default mmap limits",
just as the same as commit 18166b6556 ("Mali: midgard:
set "FMODE_UNSIGNED_OFFSET" bit in file flags of mali device file")
Change-Id: Ic03fd03c94c7ac1ae0da59d0a69c519dc5e2810c
Signed-off-by: Zhen Chen <chenzhen@rock-chips.com>
The note /dev/vendor_storage include api to update loader,
this node must config root user access only, but some
project set this node`s owner as bluetooth ,it is a high
risk that the loader data will be corrupted.
Disable this api by default.
Change-Id: I6beb1b3cf51bffebd0ae05368d8c266439a61f91
Signed-off-by: Yifeng Zhao <zyf@rock-chips.com>
When handing the SETUP packet by composite_setup(), we will release the
dwc->lock. If we get the 'USB_GADGET_DELAYED_STATUS' result from setup
function, which means we need to delay handling the STATUS phase.
But during the lock release period, maybe the request for handling delay
STATUS phase has been queued into list before we set 'dwc->delayed_status'
flag or entering 'EP0_STATUS_PHASE' phase, then we will miss the chance
to handle the STATUS phase. Thus we should check if the request for delay
STATUS phase has been enqueued when entering 'EP0_STATUS_PHASE' phase in
dwc3_ep0_xfernotready(), if so, we should handle it.
Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
(cherry picked from commit 538967983b)
Change-Id: I75b28733518ad97f94a2f5564b53b7b6909741d5
Signed-off-by: David Wu <david.wu@rock-chips.com>
Currently the link_state is uninitialized and the default value is 0(U0)
before the first time we start the udc, and after we start the udc then
stop the udc, the link_state will be undefined.
We may have the following warnings if we start the udc again with
an undefined link_state:
WARNING: CPU: 0 PID: 327 at drivers/usb/dwc3/gadget.c:294 dwc3_send_gadget_ep_cmd+0x304/0x308
dwc3 100e0000.hidwc3_0: wakeup failed --> -22
[...]
Call Trace:
[<c010f270>] (unwind_backtrace) from [<c010b3d8>] (show_stack+0x10/0x14)
[<c010b3d8>] (show_stack) from [<c034a4dc>] (dump_stack+0x84/0x98)
[<c034a4dc>] (dump_stack) from [<c0118000>] (__warn+0xe8/0x100)
[<c0118000>] (__warn) from [<c0118050>](warn_slowpath_fmt+0x38/0x48)
[<c0118050>] (warn_slowpath_fmt) from [<c0442ec0>](dwc3_send_gadget_ep_cmd+0x304/0x308)
[<c0442ec0>] (dwc3_send_gadget_ep_cmd) from [<c0445e68>](dwc3_ep0_start_trans+0x48/0xf4)
[<c0445e68>] (dwc3_ep0_start_trans) from [<c0446750>](dwc3_ep0_out_start+0x64/0x80)
[<c0446750>] (dwc3_ep0_out_start) from [<c04451c0>](__dwc3_gadget_start+0x1e0/0x278)
[<c04451c0>] (__dwc3_gadget_start) from [<c04452e0>](dwc3_gadget_start+0x88/0x10c)
[<c04452e0>] (dwc3_gadget_start) from [<c045ee54>](udc_bind_to_driver+0x88/0xbc)
[<c045ee54>] (udc_bind_to_driver) from [<c045f29c>](usb_gadget_probe_driver+0xf8/0x140)
[<c045f29c>] (usb_gadget_probe_driver) from [<bf005424>](gadget_dev_desc_UDC_store+0xac/0xc4 [libcomposite])
[<bf005424>] (gadget_dev_desc_UDC_store [libcomposite]) from[<c023d8e0>] (configfs_write_file+0xd4/0x160)
[<c023d8e0>] (configfs_write_file) from [<c01d51e8>] (__vfs_write+0x1c/0x114)
[<c01d51e8>] (__vfs_write) from [<c01d5ff4>] (vfs_write+0xa4/0x168)
[<c01d5ff4>] (vfs_write) from [<c01d6d40>] (SyS_write+0x3c/0x90)
[<c01d6d40>] (SyS_write) from [<c0107400>] (ret_fast_syscall+0x0/0x3c)
Change-Id: Ib36cc28674fb34c5ca050681ad0d8b07067b070f
Signed-off-by: Zeng Tao <prime.zeng@hisilicon.com>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Signed-off-by: William Wu <william.wu@rock-chips.com>
(cherry picked from commit 88b1bb1f3b)
When a read command is issued in video mode, gen_rd_cmd_busy
timeout delay needs to be increased to one frame.
Change-Id: Ic8070431c3d365f40da5f4758e578cece231e669
Signed-off-by: Wyon Bi <bivvy.bi@rock-chips.com>
support the mipi vc multi-channel input in cif driver
for rk1808
Change-Id: I432c628b30e6f6f23e8515158dcf516e499bf79a
Signed-off-by: Xu Hongfei <xuhf@rock-chips.com>
From the suggest of IP vendor, we need more delays to
adapt to the playing scene in different temperature
environments.
Change-Id: I95abe2bac43de19241092d6e785f28960760dacd
Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
Split DT source files to separate out android firmware for Android Pie & Oreo
Change-Id: I9ab950ec8c5c60b0ae4f74d5734ae4f4b05d6cf4
Signed-off-by: Bian Jin chen <kenjc.bian@rock-chips.com>
