From: Rob Herring <robh@kernel.org>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: broonie@kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-spi@vger.kernel.org,
linux-tegra@vger.kernel.org, ashishsingha@nvidia.com,
skomatineni@nvidia.com, ldewangan@nvidia.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch V3 2/3] spi: dt-bindings: split peripheral prods
Date: Thu, 9 Jun 2022 14:13:15 -0600 [thread overview]
Message-ID: <20220609201315.GA24169-robh@kernel.org> (raw)
In-Reply-To: <20220607114659.54314-3-kyarlagadda@nvidia.com>
On Tue, Jun 07, 2022 at 05:16:58PM +0530, Krishna Yarlagadda wrote:
> Move peripheral properties for Tegra QSPI controller to
> nvidia,tegra210-quad-peripheral-props.yaml and add reference
> to spi-peripheral-props.yaml file.
What are 'peripheral prods'?
>
> Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
> ---
> ...nvidia,tegra210-quad-peripheral-props.yaml | 33 +++++++++++++++++++
> .../bindings/spi/nvidia,tegra210-quad.yaml | 21 ------------
> .../bindings/spi/spi-peripheral-props.yaml | 1 +
> 3 files changed, 34 insertions(+), 21 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra210-quad-peripheral-props.yaml
Otherwise,
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-06-09 20:13 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 [this message]
2022-06-07 11:46 ` [Patch V3 3/3] spi: dt-bindings: Add compatible for Tegra241 QSPI Krishna Yarlagadda
2022-06-09 20:13 ` 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=20220609201315.GA24169-robh@kernel.org \
--to=robh@kernel.org \
--cc=ashishsingha@nvidia.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kyarlagadda@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=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.