* commit '40fac1a66ccf61bdf3afb70c18a5db7791410b22': (220 commits)
Revert "tee: optee: interrupt an RPC when supplicant has been killed"
Revert "tee: optee: interrupt an RPC depend on shutdown flag"
arm64: dts: rockchip: rv1126bp-evb-v14: Adjust the matching voltage
media: rockchip: aiisp: delete one temp buffer to reduce memory
media: rockchip: isp: mp output buf notice to aiisp
media: rockchip: aiisp: modify for aiynr algo
rtc: rockchip: add ready flag for rtc setting time
soc: rockchip: cpuinfo: export chip unique id to userspace
media: rockchip: vpss: offline mode support auto unite output
drm/rockchip: vop2: Add "DIMMING_DATA" property for local dimming
media: rockchip: isp: aiisp switch for offline mode
media: rockchip: isp: aiisp switch for isp35
media: rockchip: isp: support aiisp yuv mode
input: touchscreen: gt1x: prefix global variables and functions with "gt1x_"
MALI: valhall: add gpu mem sysfs entry
drm/rockchip: Make the DRM panel as part of Rockchip DRM sub devices for panel loader protect
drm/rockchip: Pass struct rockchip_drm_sub_dev for &rockchip_drm_sub_dev.loader_protect()
pwm: rockchip: Add &rockchip_pwm_chip.oneshot_valid to indicate validity of configurations
pwm: rockchip: Add comments for why to add delay before disabling the dclk for PWM v4
input: touchscreen: hyn: reduce logs
...
Change-Id: I1b562efca0842173010b2506231d7200a5116e5a
The Linux OS uses the device tree to detect the wifibt module,
particularly the Bluetooth module's UART, identified via
`/sys/firmware/devicetree/base/pinctrl/wireless-bluetooth`.
Some RK3566/RK3568 board configurations redundantly register the pinctrl
for wireless-bluetooth, causing script failures in UART identification.
This commit removes the redundant node to resolve conflicts and ensure
correct UART identification for Bluetooth communication.
Change-Id: Id55c48bda38275c04a365b0ede1f740baf767da2
Signed-off-by: Caesar Wang <wxt@rock-chips.com>
we don't directly enable all evb board to support bt-sco cards
because it may take some i2s/pcm, which may use dma,
but dmas may limit.
so we just prepare this settings, then if any one who want to
support bt-sco, he/she can just add dts in board-level dts.
now, we just enable rk3568-evb1 and rk3566-evb1 just for example.
Diff in "rk3568-evb1-ddr4-v10.dts" is like this:
+&bt_sco {
+ status = "okay";
+};
+
+&bt_sound {
+ status = "okay";
+};
+
+&i2s3_2ch {
+ status = "okay";
+};
The default pcm/i2s setting is:
Format: PCM, dsp_a, MSB first, short sync, rising edge and delay 1 bclk.
rockchip soc: master; Bt controller: slave
Change-Id: I6668bfbb87e4b0ea71a661bbcf8248cbde77974e
Signed-off-by: Zou Dengming <marsow.zou@rock-chips.com>
The pcie supply design is (rk3566 evb2 example)
DC12V
-> VCC12V_PCIE(controlled by GPIO0_C2_H)
-> VCC3V3_PCIE(controlled by GPIO0_C2_H)
-> VCC5V0_SYS
-> VCC3V3_PI6C(controlled by GPIO0_C2_H)
The pci phy driver only want to enable or disable the VCC3V3_PCIE power.
Suggested from pcie owner to ignore the VCC12V_PCIE and VCC3V3_PI6C, so
the dts only need to add regulator node for VCC3V3_PCIE.
Most of time we keep the regulator name same as the hardware design, so
the dts node is
vcc3v3_pcie: gpio-regulator {
compatible = "regulator-fixed";
regulator-name = "vcc3v3_pcie";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
enable-active-high;
gpio = <&gpio0 RK_PB7 GPIO_ACTIVE_HIGH>;
vin-supply = <&dc_12v>;
};
The regulator type is "regulator-fixed" since its voltage always be
3.3v, min and max should be 3300000 make the regulator has a voltage
value.
The regulator can be enabled or disabled by regulator_enable or
regulator_disable function, so make the GPIO0_B7 as "ena_pin" for the
regulator.
The regulator is supplied by DCIN_12V, so add the vin-supply.
Some boards need a delay before enabling trainning for power to be
stable from the measurement.
By measurement, 5ms is enough for power and refclk to be stable.
Change-Id: Iaf70abe9c9e06504af067dc0e3d60b775557c026
Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com>
Should not be zero ahead, otherwise the min voltage is interpreted
as a wrong value by regulator code.
Change-Id: Ia141583f411a54bf26cb88b3992687539f29fec8
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
After changing the drive strength, fix the current
delayline.
Change-Id: I2aca4ddef692214a9c2e2cf7bae261cea04027b1
Signed-off-by: David Wu <david.wu@rock-chips.com>
