It makes sense to check whether the assigned cursor plane can be
attached to a specific VP, as there may be an invalid DTS assignment
for 'cursor-win-id'.
The logs may be like:
......
[ 2.178737][ T81] rockchip-vop2 27d00000.vop: [drm:vop2_create_crtc] *ERROR* Assigned cursor plane: Esmart3 can not attach to VP0
[ 2.178753][ T81] [drm] failed to init cursor plane for vp0
[ 2.178823][ T81] rockchip-vop2 27d00000.vop: [drm:vop2_create_crtc] *ERROR* Assigned cursor plane: Esmart2 can not attach to VP1
[ 2.178838][ T81] [drm] failed to init cursor plane for vp1
......
Change-Id: If18c4db1e8b295e72dae0c23bd0dd41203c4e3ac
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
RK3528/RK3562/RK3576 use the VOP3 architecture, which supports
flexible switching of planes between different VP. User can switch
planes between different CRTCs based on the &drm_plane.possible_crtcs
in userspace, and the plane-mask does not need to be assigned by
default in DTS.
However, for some Linux systems, there may still be scenarios where
it is necessary to specify the primary and cursor planes specifically
used on a VP.
Therefore, the valid plane-mask assignment will change the
&drm_plane.possible_crtcs and establish a fixed binding relationship
between planes and CRTCs, which means that the flexible switching of
planes is not available in the case.
Change-Id: I156f71ceb238c5945a92f48c0024f398711ea811
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
Adds the proper MODULE_IMPORT_NS(DMA_BUF) line to the file to get it to
build properly.
Fixes: 5452a06eed ("usb: gadget: uvc: support zero copy with rockchip encoder")
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Change-Id: Iab7fe8977389cd7b3e624a231011ea07d7b6d936
Add const qualifier to rockchip_drm_driver for immutability and safety.
Signed-off-by: Sandy Huang <hjc@rock-chips.com>
Change-Id: I9d461c702432cf976a0c1413ae1c257faf405f10
The DP_EDP_CONFIGURATION_SET should be configured instead of the
DP_LANE_COUNT_SET register to disable ASSR.
Fixes: 3ae279210e ("drm/bridge: analogix_dp: add support for ASSR mode")
Change-Id: I1dc36bd3dbfdeb09cde761c6905e22feba52558a
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
If clock is directly turned off during doing soft resetting, NOC may
encountering error, and other IPs will issue some error.
Signed-off-by: Johnson Ding <johnson.ding@rock-chips.com>
Change-Id: I5df74c68faa042a231bc84df3de4d362830bc7c5
Even if colorspace of hdr video is not bt2020, it can be
seamlessly switched to yuv422 10bit in scenarios where
sink supports yuv422.
Change-Id: Ieb2c9a3c17183349caa70d5a3ba07ccf1b14252a
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
Added power sequence control for shutdown, suspend and wakeup.
These configurations are hardware-dependent, any modifications should be
consulted with hardware engineers for recommendations.
Change-Id: Id3f72f27e952b4cc2573a45f1a3363b6923daf87
Signed-off-by: Shengfei Xu <xsf@rock-chips.com>
(sched_priority = MAX_RT_PRIO - 1) is highest priority of the RT
thread, it may affect RT performance, so use sched_set_fifo_low()
will be better.
Change-Id: I1de7aa5fbc20bd40fbc68956863dfd8c76e7f363
Signed-off-by: Liang Chen <cl@rock-chips.com>
Resolve the crash issue caused by closing serdes pinctrl configuration
in dts.
Change-Id: I0473785d128bf655df9117dc819c502267ffec1e
Signed-off-by: Zitong Cai <zitong.cai@rock-chips.com>
If an extcon event is reported when hdmi is enabled/disabled
while playing hdr videos, Some player app will self-destruct
and restart after receiving the event. This leads to an endless
loop of switching hdmi enable and disable.
The extcon event is normally sent when hdmi plug. Previously,
the extcon event reporting was placed in hdmi enable/disable
to resolve issues related to audio transparent transmission.
The current code has hdmi_codec_plugged_cb has solved the audio
transmission problem, so extcon event is changed back to be
called only when hdmi plug/unplug
Change-Id: I613a0c99a0d33e133280cc6ba3d74760532c7f2f
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
The buffer write address ADR_BSBS of VEPU580 differs from
other IPs and requires separate definition.
Change-Id: I8a97f26ffd64ac74cedeed84de408e3ec952fd52
Signed-off-by: Yanjun Liao <yanjun.liao@rock-chips.com>
Some USB Readers base on the keyboard boot protocol, but
they don't properly set the data toggle in the status stage
when set the LED request.
The known abnormal usb hid devices include:
[1] idVendor=413d, idProduct=2107
[2] idVendor=ffff, idProduct=0035
This cause xHCI died on Rockchip platforms with the following
typical log.
[ 38.564579] usb 5-1: new full-speed USB device number 3 using xhci-hcd
[ 38.707763] usb 5-1: New USB device found, idVendor=413d, idProduct=2107, bcdDevice= 0.00
[ 38.707829] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 38.707855] usb 5-1: Product: USB Reader
[ 38.707880] usb 5-1: Manufacturer: DXTeco
[ 38.707903] usb 5-1: SerialNumber: 2008-07-15
......
[ 43.325848] usb 5-1: USB disconnect, device number 3
[ 48.481188] xhci-hcd xhci-hcd.1.auto: xHCI host not responding to stop endpoint command.
[ 48.491454] xhci-hcd xhci-hcd.1.auto: xHCI host controller not responding, assume dead
[ 48.491617] xhci-hcd xhci-hcd.1.auto: HC died; cleaning up
In fact, the USB Readers don't support LED control, so it
can ignore set Led for USB Readers to avoid xHCI died issue.
Change-Id: Ie2cb6f8204055035d434f32dea548461c58c5ab1
Signed-off-by: William Wu <william.wu@rock-chips.com>
