aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips
diff options
context:
space:
mode:
authorSungbo Eo <mans0n@gorani.run>2022-02-20 00:19:31 +0900
committerSungbo Eo <mans0n@gorani.run>2022-02-20 13:47:57 +0900
commit9968a909c248169064446ed40e66d18986d93d11 (patch)
tree0950885106d3c9714deb8fac05e46d52ca8bb081 /target/linux/ramips
parent19a90262df89f8419b058cf9a00dc9e8d465088b (diff)
downloadupstream-9968a909c248169064446ed40e66d18986d93d11.tar.gz
upstream-9968a909c248169064446ed40e66d18986d93d11.tar.bz2
upstream-9968a909c248169064446ed40e66d18986d93d11.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>
Diffstat (limited to 'target/linux/ramips')
-rw-r--r--target/linux/ramips/dts/mt7620a_iptime.dtsi2
1 files changed, 1 insertions, 1 deletions
diff --git a/target/linux/ramips/dts/mt7620a_iptime.dtsi b/target/linux/ramips/dts/mt7620a_iptime.dtsi
index 3e2378aa60..2672789371 100644
--- a/target/linux/ramips/dts/mt7620a_iptime.dtsi
+++ b/target/linux/ramips/dts/mt7620a_iptime.dtsi
@@ -21,7 +21,7 @@
flash@0 {
compatible = "jedec,spi-nor";
reg = <0>;
- spi-max-frequency = <50000000>;
+ spi-max-frequency = <40000000>;
partitions {
compatible = "fixed-partitions";