From: Svyatoslav Ryhel <clamor95@gmail.com>
To: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Maxim Schwalm <maxim.schwalm@gmail.com>,
David Heidelberg <david@ixit.cz>, Ion Agorria <ion@agorria.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] ARM: tegra: Add device-tree for Asus Portable AiO P1801-T
Date: Mon, 16 Jun 2025 10:39:45 +0300 [thread overview]
Message-ID: <20250616073947.13675-1-clamor95@gmail.com> (raw)
Add a device-tree for the Asus Portable AiO P1801-T, which is a NVIDIA
Tegra30-based 2-in-1 detachable tablet, originally running Android.
Device tree contains "mstar,tsumu88adt3-lf-1" compatible, a simple bridge
which was submitted a while ago here [1] but was not applied yet.
[1] https://lore.kernel.org/lkml/CAPVz0n1udjVZY3400hYMY07DjNKfOt4bwpW6He6A4qo_3pXtqQ@mail.gmail.com/T/#mb50632e269d89275d97c485037da8893239b5410
Maxim Schwalm (1):
dt-bindings: arm: tegra: Add Asus Portable AiO P1801-T
Svyatoslav Ryhel (1):
ARM: tegra: Add device-tree for Asus Portable AiO P1801-T
.../devicetree/bindings/arm/tegra.yaml | 4 +
arch/arm/boot/dts/nvidia/Makefile | 1 +
.../boot/dts/nvidia/tegra30-asus-p1801-t.dts | 2087 +++++++++++++++++
3 files changed, 2092 insertions(+)
create mode 100644 arch/arm/boot/dts/nvidia/tegra30-asus-p1801-t.dts
--
2.48.1
next reply other threads:[~2025-06-16 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 7:39 Svyatoslav Ryhel [this message]
2025-06-16 7:39 ` [PATCH v1 1/2] dt-bindings: arm: tegra: Add " Svyatoslav Ryhel
2025-06-26 23:53 ` Rob Herring (Arm)
2025-06-16 7:39 ` [PATCH v1 2/2] ARM: tegra: Add device-tree for " Svyatoslav Ryhel
2025-06-16 21:46 ` [PATCH v1 0/2] " Rob Herring (Arm)
2025-07-11 15:13 ` Thierry Reding
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=20250616073947.13675-1-clamor95@gmail.com \
--to=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=ion@agorria.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maxim.schwalm@gmail.com \
--cc=robh@kernel.org \
--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®