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 V3 3/3] spi: dt-bindings: Add compatible for Tegra241 QSPI
Date: Tue, 7 Jun 2022 17:16:59 +0530 [thread overview]
Message-ID: <20220607114659.54314-4-kyarlagadda@nvidia.com> (raw)
In-Reply-To: <20220607114659.54314-1-kyarlagadda@nvidia.com>
Add new compatible for Tegra241 QSPI controller which has
multiple chip select lines.
Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
---
Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml b/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
index e79f0b2560a4..6b733e5c1163 100644
--- a/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
+++ b/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
@@ -20,6 +20,7 @@ properties:
- nvidia,tegra186-qspi
- nvidia,tegra194-qspi
- nvidia,tegra234-qspi
+ - nvidia,tegra241-qspi
reg:
maxItems: 1
--
2.17.1
next prev parent reply other threads:[~2022-06-07 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 11:46 [Patch V3 0/3] spi: tegra quad: Add Tegra Grace features Krishna Yarlagadda
2022-06-07 11:46 ` [Patch V3 1/3] spi: tegra210-quad: Multi-cs support Krishna Yarlagadda
2022-06-07 11:46 ` [Patch V3 2/3] spi: dt-bindings: split peripheral prods Krishna Yarlagadda
2022-06-09 20:13 ` Rob Herring
2022-06-07 11:46 ` Krishna Yarlagadda [this message]
2022-06-09 20:13 ` [Patch V3 3/3] spi: dt-bindings: Add compatible for Tegra241 QSPI Rob Herring
2022-06-13 17:24 ` [Patch V3 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=20220607114659.54314-4-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®