Building with 'make W=1' shows a harmless -Wempty-body warning:
drivers/video/rockchip/iep/hw_iep_reg.c: In function 'iep_soft_rst':
drivers/video/rockchip/iep/hw_iep_reg.c:1313:49: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body]
1313 | IEP_DBG("soft reset timeout.\n");
| ^
Change the empty debug macros to no_printk(), which avoids the
warnings and adds useful format string checks.
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Change-Id: Ifff86aeab7cc988d5af694d8709fb4b9c634b044
Using the "start_decom" node requires complex preparation,
such as modifying UBOOT code, adding partitions, modifying
reserved memory. To quickly set up a testing environment,
we introduced the "dynamic_buf_decom" node which only requires
placing test files in the /data/data/ directory to begin
testing hardware decompression
The testing command similar to "start_decom"
echo mode > /sys/devices/platform/fea80000.decompress/dynamic_buf_decom
Change-Id: Ibfa1ec2a7c3e74b5c58392458827a9542c907e23
Signed-off-by: Simon Xue <xxm@rock-chips.com>
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data in a single step.
Change-Id: I713eea70b5fc6751a2b1f9cbd1334a5cd32d2611
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data in a single step.
Change-Id: Ibfc529fcc4709f0ac684a6dd4f79196af4f161dd
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data in a single step.
Change-Id: I1db708801f98f00e92f30b690ec0f222d14420d7
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data in a single step.
Change-Id: I1ef68ac7b68ed86f06f4df13e57bb4d6092c49ff
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data in a single step.
Change-Id: If1ce1ef3a34aa9acbc2438e89031f0b94f459257
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data in a single step.
Change-Id: Ic61c69ed5028dc45e62b58cc3c4aa6368978d2e4
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data in a single step.
Change-Id: I770517a2c472135c334719d677f474e345ede4aa
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Take RK3588 as an example to show how to test decompress:
echo mode > /sys/devices/platform/fea80000.decompress/start_decom
“mode” means the compressed package format has following three types:
0 - LZ4
1 - GZIP
2 - ZLIB
Change-Id: Ibd264dcce964c142abb603c1a5e8ca4c14e9fe1e
Signed-off-by: Simon Xue <xxm@rock-chips.com>
From chip design point of view, ATS support wasn't implemented in EP mode,
but leaving ATS cap available for both of EP and RC mode is totally broken
if servers active IOMMU and ATS support.
Reports state the problem are:
(1)When running the rk3588 in endpoint mode, with an Intel host with IOMMU
enabled, the host side prints:
DMAR: VT-d detected Invalidation Time-out Error: SID 0
(2)When running the rk3588 in endpoint mode, with an AMD host with IOMMU
enabled, the host side prints:
iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=63:00.0 address=0x42b5b01a0]
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
Change-Id: I7763f304bb3b71c11a67579803b2531ab7538133
For RK3588/RK3576, eDP IP can support not only eDP v1.3 but also
DP v1.2.
According to the SI test result, the new RBR and HBR pe/vs
configurations can better meet the DP v1.2 signal specification
requirements.
Change-Id: I3dfc1facebe0bf5fb7bc1d35b9fd397aefa71948
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
The bridge drivers is various, so the check of switching the
eDP/DP mode may not cover all application scenario.
Therefore, we add a property of the eDP node to support forced
switching to eDP mode, and the DT setting may be like:
&edp {
edp-mode;
};
Change-Id: I4f808b57def701e96d63d2470c2ec904e0ab29a5
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
Some bridges support to convert DP into display interfaces that support
the panel, such as RGB, LVDS, MIPI and so on. For instance, the LT7211B
and LT7911D from Lontium can offer this functionality.
Therefore, we add a property of the eDP node to support forced switching
to DP mode, and the DT setting may be like:
&edp0 {
dp-mode;
};
Change-Id: I0f7c2598f86fb9d5ebedc945e3acd66388215d16
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
Since the Analogix IP can support both eDP v1.3 and DP v1.2, it is
sensible to first check whether the last bridge is connected to a
panel in order to determine and pass on the eDP/DP submodes to the
PHY, which can help separate the eDP/DP configurations in the PHY
driver.
Change-Id: I86e1c52e15f9348ff9524caaa159f92e5c6fc5de
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
For RK3588/RK3576, eDP IP can support not only eDP v1.3 but also
DP v1.2, which has the different PHY configurations to separate
eDP and DP mode.
Change-Id: I04d72c1230e939b647c5f79c0351f621ade5510d
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
The VDD_LOGIC of rk3308-evb-v11 is fixed, so do not enable dmc.
Change-Id: I17bf982d8d4107f8ce474b80c9e80d3e610d6029
Signed-off-by: Liang Chen <cl@rock-chips.com>
