From: Josef Schlehofer <pepe.schlehofer@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Peter Griffin <peter.griffin@linaro.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ARM: dts: samsung: Add support for Hardkernel ODROID-U2
Date: Sun, 18 Oct 2026 14:44:57 +0200 [thread overview]
Message-ID: <20261018124459.3026-1-pepe.schlehofer@gmail.com> (raw)
This series introduces device tree support for Hardkernel's ODROID-U2
single board computer, based on the Samsung Exynos4412 Prime SoC.
ODROID-U2 is the predecessor of ODROID-U3 and shares most of its hardware
design (2 GB LPDDR2 RAM, LAN9730 10/100 Ethernet on HSIC0, USB3503A hub
on HSIC1, MAX98090 audio codec with headphone jack and on-board MEMS DMIC,
MAX77686 PMIC, PWM-controlled cooling fan header, blue heartbeat LED).
Key differences from ODROID-U3:
- The micro-USB (DWC2 / hsotg) port does not have a VBUS supply switch,
so it operates only in peripheral mode (dr_mode = "peripheral").
- The 3.5 mm jack is headphone only, and the board features an on-board
MEMS digital microphone (DMIC) rather than an analog mic input.
- There is no expansion header with SPI.
Hardware verification was performed on a physical ODROID-U2 board running
Linux 6.12:
- DWC2 USB: verified in peripheral mode via /sys/class/udc and dmesg.
- Ethernet: SMSC LAN9730 detected on HSIC0, link up at 100 Mbps Full-Duplex.
- Storage: microSD (mmcblk2) detected and functional. eMMC was not tested,
as no eMMC module was available.
- Thermal: /sys/class/thermal/cooling_device0/type shows pwm-fan (no fan
was attached).
- Audio:
* Stereo headphone playback verified with speaker-test and aplay.
* On-board digital MEMS microphone (DMIC) recording verified with:
amixer -c OdroidU2 cset name='DMIC Mux' DMIC
arecord -D hw:OdroidU2,0 -f S16_LE -r 48000 -c 2 -d 5 /tmp/dmic.wav
aplay -D hw:OdroidU2,0 /tmp/dmic.wav
Audio routing includes "Mixer DAI RX", "HiFi Capture" connecting the
MAX98090 codec capture to the Exynos I2S controller.
- LED: blue:heartbeat blinking with heartbeat trigger.
Josef Schlehofer (2):
dt-bindings: arm: samsung: Add Hardkernel ODROID-U2
ARM: dts: samsung: Add Hardkernel ODROID-U2
.../bindings/arm/samsung/samsung-boards.yaml | 1 +
arch/arm/boot/dts/samsung/Makefile | 1 +
.../dts/samsung/exynos4412-odroid-common.dtsi | 6 +-
.../boot/dts/samsung/exynos4412-odroidu2.dts | 139 ++++++++++++++++++
4 files changed, 144 insertions(+), 3 deletions(-)
create mode 100644 arch/arm/boot/dts/samsung/exynos4412-odroidu2.dts
base-commit: 58161ead29e50d70a317ea26b472e0c7508e69da
--
2.54.0 (Apple Git-157)
next reply other threads:[~2026-10-18 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 12:44 Josef Schlehofer [this message]
2026-10-18 12:44 ` [PATCH 1/2] dt-bindings: arm: samsung: Add " Josef Schlehofer
2026-10-19 14:05 ` Henrik Grimler
2026-10-18 12:44 ` [PATCH 2/2] ARM: dts: " Josef Schlehofer
2026-10-19 14:01 ` Henrik Grimler
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=20261018124459.3026-1-pepe.schlehofer@gmail.com \
--to=pepe.schlehofer@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=peter.griffin@linaro.org \
--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
all inboxes | Powered by JetHome®