diff options
| author | Michael Walle <[email protected]> | 2026-03-18 15:29:17 +0100 |
|---|---|---|
| committer | Peng Fan <[email protected]> | 2026-03-23 14:27:24 +0800 |
| commit | 1f305f99d2001e96daa7e93da4da2bf56da9278e (patch) | |
| tree | aaac3707938564271582b2ea566e66ed99069ad9 /doc | |
| parent | a5e46ecc3593960c2fe763a598a6fd804912f05b (diff) | |
armv7: ls102xa: fix SPI flash clock
Commit bb6f3c0f7634 ("armv7: ls102xa: Update SCFG_QSPI_CLKSEL value")
broke the SPI boot on the LS1021ATSN board (ls1021atsn_qspi_defconfig)
at least.
The commit message reads
Update SCFG_QSPI_CLKSEL value : 0xC -> 0x5
which means ClusterPLL/16
The original submitted patch had the following description:
Value 0xC is reserved. Replace it with correct value 0x5 which
is ClusterPLL/16
Unfortunatly, the little information which was there, was stripped even
further. Why is 0x5 the "correct" value? In fact, it seems that the
upper bit is just ignored and thus the value 0xC translates to 0x4 which
is ClusterPLL/20. This, will result in a SPI clock of 60MHz (if the PLL
is clocked at 1.2GHz). But even that is too much for the (default) 03h
read opcode (max 50MHz). Set the value to ClusterPLL/24 which is 50MHz.
Link: https://lore.kernel.org/r/[email protected]/
Fixes: bb6f3c0f7634 ("armv7: ls102xa: Update SCFG_QSPI_CLKSEL value")
Signed-off-by: Michael Walle <[email protected]>
Reviewed-by: Vladimir Oltean <[email protected]>
Signed-off-by: Peng Fan <[email protected]>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions
