From: Svyatoslav Ryhel <clamor95@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Shubhi Garg <shgarg@nvidia.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Tegra114: switch Tegra Note 7 from tn7 to tegratab
Date: Mon, 12 Feb 2024 09:18:41 +0200 [thread overview]
Message-ID: <20240212071843.6679-1-clamor95@gmail.com> (raw)
Currently Tegra Note 7 uses tn7 compatible and device tree name which is
not quite correct. This device has proper codename which is tegratab.
Switch tn7 in compatible to tegratab and set a better device tree name
tegra114-nvidia-tegratab which aligns with newer trees.
Svyatoslav Ryhel (2):
ARM: tegra: set correct naming for Tegra Note 7
dt-bindings: arm: tegra: document NVIDIA Tegra Note 7 properly
Documentation/devicetree/bindings/arm/tegra.yaml | 5 ++++-
arch/arm/boot/dts/nvidia/Makefile | 4 ++--
.../{tegra114-tn7.dts => tegra114-nvidia-tegratab.dts} | 5 +++--
3 files changed, 9 insertions(+), 5 deletions(-)
rename arch/arm/boot/dts/nvidia/{tegra114-tn7.dts => tegra114-nvidia-tegratab.dts} (98%)
--
2.40.1
next reply other threads:[~2024-02-12 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 7:18 Svyatoslav Ryhel [this message]
2024-02-12 7:18 ` [PATCH v1 1/2] ARM: tegra: set correct naming for Tegra Note 7 Svyatoslav Ryhel
2024-02-12 7:33 ` Krzysztof Kozlowski
2024-02-12 16:14 ` Jon Hunter
2024-02-12 16:50 ` Thierry Reding
2024-02-12 7:18 ` [PATCH v1 2/2] dt-bindings: arm: tegra: document NVIDIA Tegra Note 7 properly Svyatoslav Ryhel
2024-02-12 7:32 ` Krzysztof Kozlowski
2024-02-12 16:13 ` [PATCH v1 0/2] Tegra114: switch Tegra Note 7 from tn7 to tegratab Jon Hunter
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=20240212071843.6679-1-clamor95@gmail.com \
--to=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shgarg@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®