From: Lukas Timmermann <linux@timmermann.space>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
Lukas Timmermann <linux@timmermann.space>,
Alexandre Marquet <tb@a-marquet.fr>,
Henrik Grimler <henrik@grimler.se>
Subject: [PATCH v4 0/3] Add support for exynos5250-manta (Google Nexus 10)
Date: Tue, 27 Jan 2026 21:40:55 +0100 [thread overview]
Message-ID: <20260127-lat3st-staging-v4-0-797469aaaf9d@timmermann.space> (raw)
This patch series adds initial support for the google-manta board, known
as Google Nexus 10 to users. The device is powered by
the Exynos 5250 SoC. The bindings for the notification led are already
in the linux-next tree and can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/leds/ams,as3668.yaml
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 and with WiFi support. We will upstream additional
features in future patches. All patches have been tested on real hardware.
Changes in v4:
- Changed copyright years to 2026
- Rearranged includes
- Added comments to bmp180 voltage sources
- Refactored serial2 output
- Rearranged multiple properties of nodes. (@krzk)
- Rearranged nodes and subnodes. (@krzk) (@david)
- Fixed mismatch with firmware address.
- Fixed dtb check errors
- Added cpu1 power supply node.
- Renamed multiple subnodes.
- Removed i2c_0 for now as it isn't used.
- Fixed wifi interrupt.
- Added empty lines where applicable. (@krzk) (@david)
- Deactivated serial_1 for now.
- Link to v3: https://lore.kernel.org/r/20251215-lat3st-staging-v3-0-2e4914b64dd8@timmermann.space
Changes in v3:
- Added a better patch description for firmware patch. (@krzk)
- Reorganized nodes in DT. (@krzk)
- Fixed memory node to use separate entries. (@krzk)
- Renamed pwrseq node. (@krzk)
- Fixed firmware checking for old dt compatible string. (@pavel)
- Link to v2: https://lore.kernel.org/all/20251125-google-manta-v2-0-0f097cfff39c@timmermann.space/
Changes in v2:
- Renamed to google-manta (@krzk)
- Link to v1: https://lore.kernel.org/all/20251120144018.961604-2-linux@timmermann.space/
Signed-off-by: Lukas Timmermann <linux@timmermann.space>
---
Alexandre Marquet (3):
dt-bindings: ARM: samsung: Add Google Manta (Nexus 10)
ARM: dts: exynos: Add Google Manta (Nexus 10)
ARM: samsung: exynos5250: Allow CPU1 to boot
.../bindings/arm/samsung/samsung-boards.yaml | 1 +
arch/arm/boot/dts/samsung/Makefile | 1 +
arch/arm/boot/dts/samsung/exynos5250-manta.dts | 564 +++++++++++++++++++++
arch/arm/mach-exynos/firmware.c | 4 +-
4 files changed, 568 insertions(+), 2 deletions(-)
---
base-commit: d5f0e9098499869354aacb5b080f602f0399d396
change-id: 20251215-lat3st-staging-d9c926d8a75f
Best regards,
--
Lukas Timmermann <linux@timmermann.space>
next reply other threads:[~2026-01-27 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 20:40 Lukas Timmermann [this message]
2026-01-27 20:40 ` [PATCH v4 1/3] dt-bindings: ARM: samsung: Add Google Manta (Nexus 10) Lukas Timmermann
2026-01-27 20:40 ` [PATCH v4 2/3] ARM: dts: exynos: " Lukas Timmermann
2026-01-27 20:40 ` [PATCH v4 3/3] ARM: samsung: exynos5250: Allow CPU1 to boot Lukas Timmermann
2026-02-26 21:14 ` (subset) " Krzysztof Kozlowski
2026-01-28 10:58 ` [PATCH v4 0/3] Add support for exynos5250-manta (Google Nexus 10) Krzysztof Kozlowski
2026-02-26 21:13 ` (subset) " Krzysztof Kozlowski
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=20260127-lat3st-staging-v4-0-797469aaaf9d@timmermann.space \
--to=linux@timmermann.space \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=henrik@grimler.se \
--cc=krzk@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=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tb@a-marquet.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).