From: Greg KH <gregkh@linuxfoundation.org>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: stable@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, Dinh Nguyen <dinguyen@kernel.org>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 5.15 0/2] ARM: socfpga: fix broken QuadSPI support
Date: Fri, 29 Apr 2022 11:05:28 +0200 [thread overview]
Message-ID: <YmuqWLwyO2s/+FJf@kroah.com> (raw)
In-Reply-To: <20220427105407.40167-1-abbotti@mev.co.uk>
On Wed, Apr 27, 2022 at 11:54:05AM +0100, Ian Abbott wrote:
> Write support on the Cadence QSPI controller on the Intel SoCFPGA
> platform was broken by 9cb2ff111712 ("spi: cadence-quadspi: Disable
> Auto-HW polling) and fixed by 98d948eb8331 ("spi: cadence-quadspi: fix
> write completion support") and 36de991e9390 ("ARM: dts: socfpga: change
> qspi to "intel,socfpga-qspi").
>
> 1) spi: cadence-quadspi: fix write completion support
> 2) ARM: dts: socfpga: change qspi to "intel,socfpga-qspi"
>
> arch/arm/boot/dts/socfpga.dtsi | 2 +-
> arch/arm/boot/dts/socfpga_arria10.dtsi | 2 +-
> arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi | 2 +-
> arch/arm64/boot/dts/intel/socfpga_agilex.dtsi | 2 +-
> drivers/spi/spi-cadence-quadspi.c | 24 ++++++++++++++++++++---
> 5 files changed, 25 insertions(+), 7 deletions(-)
>
Both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-04-29 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 10:54 [PATCH 5.15 0/2] ARM: socfpga: fix broken QuadSPI support Ian Abbott
2022-04-27 10:54 ` [PATCH 5.15 1/2] spi: cadence-quadspi: fix write completion support Ian Abbott
2022-04-27 10:54 ` [PATCH 5.15 2/2] ARM: dts: socfpga: change qspi to "intel,socfpga-qspi" Ian Abbott
2022-04-29 9:05 ` Greg KH [this message]
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=YmuqWLwyO2s/+FJf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.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).