diff options
| author | Sungbo Eo <mans0n@gorani.run> | 2022-02-20 00:19:31 +0900 |
|---|---|---|
| committer | Sungbo Eo <mans0n@gorani.run> | 2022-02-27 21:40:32 +0900 |
| commit | 952de38ef4fbb466c8f31b7d55516ba23955975a (patch) | |
| tree | ef3aef0c3e81d5e75eb802f2b86551e528fab387 /target/linux/ramips/dts/rt5350_asiarf_awm002-evb.dtsi | |
| parent | abf8209d7f200fd9cd732a2d535699830d89f57c (diff) | |
| download | upstream-952de38ef4fbb466c8f31b7d55516ba23955975a.tar.gz upstream-952de38ef4fbb466c8f31b7d55516ba23955975a.tar.bz2 upstream-952de38ef4fbb466c8f31b7d55516ba23955975a.zip | |
Revert "ramips: increase spi-max-frequency for ipTIME mt7620 devices"
This reverts commit 13a185bf8acb67da4a68873e560876c0e60b1a87.
There was a report that one A1004ns device fails to detect its flash
chip correctly:
[ 1.470297] spi-nor spi0.0: unrecognized JEDEC id bytes: e0 10 0c 40 10 08
[ 1.484110] spi-nor: probe of spi0.0 failed with error -2
It also uses a different flash chip model:
* in my hand: Winbond W25Q128FVSIG (SOIC-8)
* reported: Macronix MX25L12845EMI-10G (SOP-16)
Reducing spi-max-frequency solved the detection failure. Hence revert.
Reported-by: Koasing <koasing@gmail.com>
Tested-by: Koasing <koasing@gmail.com>
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
(cherry picked from commit 9968a909c248169064446ed40e66d18986d93d11)
Diffstat (limited to 'target/linux/ramips/dts/rt5350_asiarf_awm002-evb.dtsi')
0 files changed, 0 insertions, 0 deletions