From: Krishna Yarlagadda <kyarlagadda@nvidia.com>
To: <broonie@kernel.org>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <linux-spi@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <ashishsingha@nvidia.com>,
<robh+dt@kernel.org>
Cc: <skomatineni@nvidia.com>, <ldewangan@nvidia.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Krishna Yarlagadda" <kyarlagadda@nvidia.com>
Subject: [Patch V2 0/3] spi: tegra quad: Add Tegra Grace features
Date: Fri, 13 May 2022 13:38:25 +0530 [thread overview]
Message-ID: <20220513080828.22079-1-kyarlagadda@nvidia.com> (raw)
Add multiple chip select lines supported on Tegra 241
Changes in v2:
Split Wait polling changes to be handled later
Change chip name to convention followed (Grace to 241)
Add tegra qspi peripherals yaml file
Krishna Yarlagadda (3):
spi: tegra210-quad: Multi-cs support
spi: dt-bindings: split peripheral prods
spi: dt-bindings: Add compatible for Tegra241 QSPI
...nvidia,tegra210-quad-peripheral-props.yaml | 45 +++++++++++++++++++
.../bindings/spi/nvidia,tegra210-quad.yaml | 33 +-------------
.../bindings/spi/spi-peripheral-props.yaml | 1 +
drivers/spi/spi-tegra210-quad.c | 33 +++++++++++++-
4 files changed, 78 insertions(+), 34 deletions(-)
create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra210-quad-peripheral-props.yaml
--
2.17.1
next reply other threads:[~2022-05-13 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 8:08 Krishna Yarlagadda [this message]
2022-05-13 8:08 ` [Patch V2 1/3] spi: tegra210-quad: Multi-cs support Krishna Yarlagadda
2022-05-13 8:08 ` [Patch V2 2/3] spi: dt-bindings: split peripheral prods Krishna Yarlagadda
2022-05-13 12:33 ` Rob Herring
2022-05-13 16:44 ` Jon Hunter
2022-05-16 17:25 ` Rob Herring
2022-05-13 8:08 ` [Patch V2 3/3] spi: dt-bindings: Add compatible for Tegra241 QSPI Krishna Yarlagadda
2022-06-13 17:24 ` [Patch V2 0/3] spi: tegra quad: Add Tegra Grace features 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=20220513080828.22079-1-kyarlagadda@nvidia.com \
--to=kyarlagadda@nvidia.com \
--cc=ashishsingha@nvidia.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.