diff options
author | Jakob Unterwurzacher <jakob.unterwurzacher@cherry.de> | 2025-06-27 15:17:12 +0200 |
---|---|---|
committer | Jakob Unterwurzacher <jakob.unterwurzacher@cherry.de> | 2025-06-30 09:48:06 +0200 |
commit | 65d710f7ca3a09b68cdd2b84a5cb0e7dd517f6ff (patch) | |
tree | 30ef34f9829d14cc19d45cb894eb9826507b1876 /rust/compiler_builtins.rs | |
parent | c3677261cdb45af20e9bc2bcdd5f6481933b8b04 (diff) |
FROMLIST: BACKPORT: arm64: dts: rockchip: use cs-gpios for spi1 on ringneck
Hardware CS has a very slow rise time of about 6us,
causing transmission errors when CS does not reach
high between transaction.
It looks like it's not driven actively when transitioning
from low to high but switched to input, so only the CPU
pull-up pulls it high, slowly. Transitions from high to low
are fast. On the oscilloscope, CS looks like an irregular sawtooth
pattern like this:
_____
^ / |
^ /| / |
/| / | / |
/ | / | / |
___/ |___/ |_____/ |___
With cs-gpios we have a CS rise time of about 20ns, as it should be,
and CS looks rectangular.
This fixes the data errors when running a flashcp loop against a
m25p40 spi flash.
With the Rockchip 6.1 kernel we see the same slow rise time, but
for some reason CS is always high for long enough to reach a solid
high.
The RK3399 and RK3588 SoCs use the same SPI driver, so we also
checked our "Puma" (RK3399) and "Tiger" (RK3588) boards.
They do not have this problem. Hardware CS rise time is good.
Fixes: c484cf93f61b ("arm64: dts: rockchip: add PX30-µQ7 (Ringneck) SoM with Haikou baseboard")
Cc: stable@vger.kernel.org
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Link: https://lore.kernel.org/all/20250627131715.1074308-1-jakob.unterwurzacher@cherry.de/
[conflicts: our &pinctrl has sdio-pwrseq causing the hunk to fail.
spi1 block inserted after sdio-pwrseq]
Signed-off-by: Jakob Unterwurzacher <jakob.unterwurzacher@cherry.de>
Diffstat (limited to 'rust/compiler_builtins.rs')
0 files changed, 0 insertions, 0 deletions