From: yogeshnarayan.gaur@nxp.com (Yogesh Gaur)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] mtd: fsl-quadspi: Update slave device hwcap based on mode provided in dtsi file
Date: Fri, 2 Feb 2018 11:01:22 +0530 [thread overview]
Message-ID: <1517549484-6024-1-git-send-email-yogeshnarayan.gaur@nxp.com> (raw)
This patch-set added support to update hwcap of slave device connected to
FSL QUADSPI controller by reading values from the device tree files.
Mode information is available via "spi-tx-bus-width" and
"spi-rx-bus-width" nodes of device tree for the connected slave device.
Update read and write hwcap capability for slave device by reading
"spi-rx-bus-width" and "spi-tx-bus-width" respectively.
Added usage example for spi-rx/tx-bus-width properties in spi-bus.txt
Depends on
https://patchwork.ozlabs.org/project/linux-mtd/list/?series=26084
Yogesh Gaur (2):
mtd: fsl-quadspi: Update slave device hwcap based on mode provided in
dtsi file
dt-bindings: spi: updated usage example for spi-rx/tx-bus-width
properties
Changes for v2:
- Drop patch 'dt-bindings: fsl-quadspi: spi-rx/tx-bus-width usage example'
- Added usage example for spi-rx/tx-bus-width properties in spi-bus.txt
Documentation/devicetree/bindings/spi/spi-bus.txt | 2 +
drivers/mtd/spi-nor/fsl-quadspi.c | 56 +++++++++++++++++++++--
2 files changed, 53 insertions(+), 5 deletions(-)
--
1.9.1
next reply other threads:[~2018-02-02 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 5:31 Yogesh Gaur [this message]
2018-02-02 5:31 ` [PATCH v2 1/2] mtd: fsl-quadspi: Update slave device hwcap based on mode provided in dtsi file Yogesh Gaur
2018-02-05 20:48 ` Cyrille Pitchen
2018-02-13 6:45 ` Yogesh Narayan Gaur
2018-02-02 5:31 ` [PATCH v2 2/2] dt-bindings: spi: updated usage example for spi-rx/tx-bus-width properties Yogesh Gaur
2018-02-05 6:09 ` Rob Herring
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=1517549484-6024-1-git-send-email-yogeshnarayan.gaur@nxp.com \
--to=yogeshnarayan.gaur@nxp.com \
--cc=linux-arm-kernel@lists.infradead.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).