From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: tegra: Add unit-address for CBB on Tegra194
Date: Tue, 1 Oct 2019 16:42:55 +0200 [thread overview]
Message-ID: <20191001144255.GC3566931@ulmo> (raw)
In-Reply-To: <20190726101618.26896-1-thierry.reding@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 661 bytes --]
On Fri, Jul 26, 2019 at 12:16:16PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The control back-bone (CBB) starts at physical address 0, so give it a
> unit-address to comply with standard naming practices checked for by the
> device tree compiler.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 20 +++++++++----------
> .../boot/dts/nvidia/tegra194-p2972-0000.dts | 2 +-
> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 2 +-
> 3 files changed, 12 insertions(+), 12 deletions(-)
All three patches applied to for-5.5/arm64/dt.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-01 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 10:16 [PATCH 1/3] arm64: tegra: Add unit-address for CBB on Tegra194 Thierry Reding
2019-07-26 10:16 ` [PATCH 2/3] arm64: tegra: Add unit-address for ACONNECT " Thierry Reding
2019-07-26 10:16 ` [PATCH 3/3] arm64: tegra: Fix base address for SOR1 " Thierry Reding
2019-07-26 16:04 ` [PATCH 1/3] arm64: tegra: Add unit-address for CBB " mirq-test
2019-10-01 14:42 ` 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=20191001144255.GC3566931@ulmo \
--to=thierry.reding@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.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).