From: Thierry Reding <thierry.reding@gmail.com>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: broonie@kernel.org, jonathanh@nvidia.com,
linux-spi@vger.kernel.org, linux-tegra@vger.kernel.org,
ashishsingha@nvidia.com, skomatineni@nvidia.com,
ldewangan@nvidia.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
p.zabel@pengutronix.de
Subject: Re: [PATCH v4] arm64: tegra: Add QSPI controllers on Tegra234
Date: Wed, 6 Apr 2022 15:28:39 +0200 [thread overview]
Message-ID: <Yk2VhxRrGfc1iSna@orome> (raw)
In-Reply-To: <20220308183026.66394-1-kyarlagadda@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
On Wed, Mar 09, 2022 at 12:00:26AM +0530, Krishna Yarlagadda wrote:
> From: Ashish Singhal <ashishsingha@nvidia.com>
>
> This adds the QSPI controllers on the Tegra234 SoC and populates the
> SPI NOR flash device for the Jetson AGX Orin platform.
>
> Signed-off-by: Ashish Singhal <ashishsingha@nvidia.com>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
> ---
> v4:
> sort definitions in include and dt files
>
> .../boot/dts/nvidia/tegra234-p3701-0000.dtsi | 12 ++++++++
> arch/arm64/boot/dts/nvidia/tegra234.dtsi | 28 +++++++++++++++++++
> include/dt-bindings/clock/tegra234-clock.h | 8 ++++++
> include/dt-bindings/reset/tegra234-reset.h | 2 ++
> 4 files changed, 50 insertions(+)
Applied, thanks. I may need to split this up at a later point if there
are conflicts in those include/dt-bindings files. Next time, please send
these kinds of changes as two separate patches: 1) dt-bindings include
changes and 2) DT changes.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-04-06 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 18:30 [PATCH v4] arm64: tegra: Add QSPI controllers on Tegra234 Krishna Yarlagadda
2022-03-09 9:00 ` Jon Hunter
2022-03-09 14:02 ` Rob Herring
2022-04-06 13:28 ` Thierry Reding [this message]
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=Yk2VhxRrGfc1iSna@orome \
--to=thierry.reding@gmail.com \
--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=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=skomatineni@nvidia.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