From: Lukas Timmermann <linux@timmermann.space>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
alim.akhtar@samsung.com, linux@armlinux.org.uk
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Timmermann <linux@timmermann.space>
Subject: [PATCH 0/3] Add support for exynos5250-samsung-nexus10-manta (Google Nexus 10)
Date: Thu, 20 Nov 2025 21:19:58 +0100 [thread overview]
Message-ID: <20251120201958.1970828-1-linux@timmermann.space> (raw)
This patch series adds initial support for the samsung-manta board, known
as Google Nexus 10 to users. The device is powered by
the Exynos 5250 SoC. The notification led driver (as3668) is already
in the kernel mailing list and can be found here:
https://lore.kernel.org/linux-leds/20251117020008.316648-1-linux@timmermann.space/
The first two patches add the necessary device tree files and
bindings, while the last patch makes a small modification to
allow CPU1 to boot, as it requires a call to it's underlying firmware.
This first iteration only provides basic support to get the board
up and running and usable via UART. We will upstream additional
features in future patches. All patches have been tested on real hardware.
Signed-off-by: Lukas Timmermann <linux@timmermann.space>
Alexandre Marquet (3):
dt-bindings: ARM: samsung: Add Samsung Manta (Google Nexus 10)
ARM: dts: exynos: Add Samsung Manta (Google Nexus 10)
ARM: samsung: exynos5250: Allow CPU1 to boot
.../bindings/arm/samsung/samsung-boards.yaml | 1 +
arch/arm/boot/dts/samsung/Makefile | 1 +
.../exynos5250-samsung-nexus10-manta.dts | 516 ++++++++++++++++++
arch/arm/mach-exynos/firmware.c | 4 +-
4 files changed, 520 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/boot/dts/samsung/exynos5250-samsung-nexus10-manta.dts
--
2.52.0
reply other threads:[~2025-11-20 20:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251120201958.1970828-1-linux@timmermann.space \
--to=linux@timmermann.space \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh@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