From: Kuldeep Singh <kuldeep.singh@nxp.com>
To: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Ashish Kumar <ashish.kumar@nxp.com>,
Kuldeep Singh <kuldeep.singh@nxp.com>
Subject: [Patch v2 0/4] NXP Flexspi driver patches
Date: Tue, 2 Mar 2021 18:19:32 +0530 [thread overview]
Message-ID: <20210302124936.1972546-1-kuldeep.singh@nxp.com> (raw)
Hi Mark,
This patchset involves changes in NXP Flexspi driver.
Patch1 adds support for disabling AHB and enabling IP read only using a
quirk which is later used by patch3 and patch4.
Patch3 and Patch4 are not related to each and are rather dependent on
patch1 and that's why I kept them in series. This also helps in easy
application of series.
Patch1: Enables IP read in flexspi
Patch2: Do bindings document for imx8dxl
Patch3: Add imx8dxl driver support
Patch4: Errata workaround for LS1028A
v2:
- Add new patch for bindings document for imx8dxl
Han Xu (1):
spi: spi-nxp-fspi: Add imx8dxl driver support
Kuldeep Singh (3):
spi: spi-nxp-fspi: Add support for IP read only
dt-bindings: spi: spi-nxp-fspi: Add imx8dxl support
spi: spi-nxp-fspi: Implement errata workaround for LS1028A
.../devicetree/bindings/spi/spi-nxp-fspi.txt | 1 +
drivers/spi/spi-nxp-fspi.c | 114 ++++++++++++++++--
2 files changed, 104 insertions(+), 11 deletions(-)
--
2.25.1
next reply other threads:[~2021-03-02 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 12:49 Kuldeep Singh [this message]
2021-03-02 12:49 ` [Patch v2 1/4] spi: spi-nxp-fspi: Add support for IP read only Kuldeep Singh
2021-03-02 12:49 ` [Patch v2 2/4] dt-bindings: spi: spi-nxp-fspi: Add imx8dxl support Kuldeep Singh
2021-03-02 12:49 ` [Patch v2 3/4] spi: spi-nxp-fspi: Add imx8dxl driver support Kuldeep Singh
2021-03-02 12:49 ` [Patch v2 4/4] spi: spi-nxp-fspi: Implement errata workaround for LS1028A Kuldeep Singh
2021-03-04 0:56 ` [Patch v2 0/4] NXP Flexspi driver patches Mark Brown
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=20210302124936.1972546-1-kuldeep.singh@nxp.com \
--to=kuldeep.singh@nxp.com \
--cc=ashish.kumar@nxp.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@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).