From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Tudor Ambarus <tudor.ambarus@linaro.org>, <claudiu.beznea@microchip.com>
Cc: <alexandre.belloni@bootlin.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] ARM: dts: at91: Set sst26vf064b SPI NOR flash at its maxumum frequency
Date: Thu, 30 Mar 2023 20:53:46 +0200 [thread overview]
Message-ID: <3fc2611e-3cd8-d9ae-5ff4-d33fda8c0099@microchip.com> (raw)
In-Reply-To: <20230328101517.1595738-1-tudor.ambarus@linaro.org>
On 28/03/2023 at 12:15, Tudor Ambarus wrote:
> 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.
Now that it's tested:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
to the whole series and I'll queue them on at91-dt branch and changed
your email address when doing so.
Thanks for your patches Tudor, it's appreciated! Best regards,
Nicolas
> 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
>
--
Nicolas Ferre
next prev parent reply other threads:[~2023-03-30 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 10:15 [PATCH v3 0/4] ARM: dts: at91: Set sst26vf064b SPI NOR flash at its maxumum frequency Tudor Ambarus
2023-03-28 10:15 ` [PATCH v3 1/4] ARM: dts: at91-sama5d27_wlsom1: Set sst26vf064b SPI NOR flash at its maximum frequency Tudor Ambarus
2023-03-28 10:23 ` Tudor Ambarus
2023-03-28 10:15 ` [PATCH v3 2/4] ARM: dts: at91-sama5d27_som1: " Tudor Ambarus
2023-03-28 10:15 ` [PATCH v3 3/4] ARM: dts: at91: sama5d2_icp: " Tudor Ambarus
2023-03-30 18:41 ` Nicolas Ferre
2023-03-28 10:15 ` [PATCH v3 4/4] ARM: dts: at91: sam9x60ek: " Tudor Ambarus
2023-03-30 18:53 ` Nicolas Ferre [this message]
2023-03-31 9:57 ` [PATCH v3 0/4] ARM: dts: at91: Set sst26vf064b SPI NOR flash at its maxumum frequency Tudor Ambarus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fc2611e-3cd8-d9ae-5ff4-d33fda8c0099@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tudor.ambarus@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).