[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230328101517.1595738-1-tudor.ambarus@linaro.org>
Date: Tue, 28 Mar 2023 10:15:13 +0000
From: Tudor Ambarus <tudor.ambarus@...aro.org>
To: nicolas.ferre@...rochip.com, claudiu.beznea@...rochip.com
Cc: alexandre.belloni@...tlin.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
tudor.ambarus@...aro.org
Subject: [PATCH v3 0/4] ARM: dts: at91: Set sst26vf064b SPI NOR flash at its maxumum frequency
Changes in v3: Update S-o-b tag to match author's email.
Changes in v2: update value of spi-cs-setup-ns as it was changed to u32
since the first proposal.
v1 at: https://lore.kernel.org/linux-mtd/20221117105249.115649-1-tudor.ambarus@microchip.com/
---
SPI NOR flashes have specific cs-setup time requirements without which
they can't work at frequencies close to their maximum supported frequency,
as they miss the first bits of the instruction command. Unrecognized
commands are ignored, thus the flash will be unresponsive. Introduce the
spi-cs-setup-ns property to allow spi devices to specify their cs setup
time.
Tudor Ambarus (4):
ARM: dts: at91-sama5d27_wlsom1: Set sst26vf064b SPI NOR flash at its
maximum frequency
ARM: dts: at91-sama5d27_som1: Set sst26vf064b SPI NOR flash at its
maximum frequency
ARM: dts: at91: sama5d2_icp: Set sst26vf064b SPI NOR flash at its
maximum frequency
ARM: dts: at91: sam9x60ek: Set sst26vf064b SPI NOR flash at its
maximum frequency
arch/arm/boot/dts/at91-sam9x60ek.dts | 3 ++-
arch/arm/boot/dts/at91-sama5d27_som1.dtsi | 3 ++-
arch/arm/boot/dts/at91-sama5d27_wlsom1.dtsi | 3 ++-
arch/arm/boot/dts/at91-sama5d2_icp.dts | 3 ++-
4 files changed, 8 insertions(+), 4 deletions(-)
--
2.40.0.348.gf938b09366-goog
Powered by blists - more mailing lists