devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Clark <inindev@gmail.com>
To: heiko@sntech.de
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	nicolas.frattaroli@collabora.com, detlev.casanova@collabora.com,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, John Clark <inindev@gmail.com>
Subject: [PATCH v1 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576
Date: Fri,  2 May 2025 16:55:30 -0400	[thread overview]
Message-ID: <20250502205533.51744-1-inindev@gmail.com> (raw)

This series adds device tree support for the Luckfox Omni3576 Carrier Board
with Core3576 Module, developed by Shenzhen Luckfox Technology Co., Ltd., based
on the Rockchip RK3576 SoC. The board supports various peripherals, with this
initial implementation enabling essential functionality for booting Linux and
basic connectivity.

Supported and tested features (on Linux 6.15-rc4):
- UART: Serial console operational.
- SD card: Mounts and reads/writes successfully.
- PCIe: NVMe SSD detected via lspci.
- Ethernet 0: Functional with RGMII PHY.
- USB: Host ports detect devices.
- RTC: Timekeeping and wake-up tested.
- LED: Heartbeat trigger works.

Disabled features:
- eMMC: Not populated on the tested board; believed to be functional but disabled.
- HDMI: Disabled due to mainline driver maturity issues (basic 1080p output works; audio and 4K untested).
- Ethernet 1: Disabled as it does not come up, possibly due to PHY configuration or driver issues.

Patch 1: Add luckfox vendor prefix for Shenzhen Luckfox Technology Co., Ltd.
Patch 2: Add luckfox,omni3576 binding to rockchip.yaml
Patch 3: Add rk3576-luckfox-omni3576.dts and Makefile update

The new DTS is covered by the existing ROCKCHIP ARCHITECTURE entry in MAINTAINERS.

I am aware of ongoing RK3576 upstreaming efforts (e.g., by Collabora) and
welcome feedback or collaboration to align with mainline driver development.

Signed-off-by: John Clark <inindev@gmail.com>

             reply	other threads:[~2025-05-02 20:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 20:55 John Clark [this message]
2025-05-02 20:55 ` [PATCH v1 1/3] dt-bindings: vendor-prefixes: Add luckfox prefix John Clark
2025-05-02 20:55 ` [PATCH v1 2/3] dt-bindings: arm: rockchip: Add Luckfox Omni3576 board John Clark
2025-05-02 20:55 ` [PATCH v1 3/3] arm64: dts: rockchip: Add Luckfox Omni3576 Carrier Board with Core3576 Module John Clark
2025-05-02 21:51   ` Andrew Lunn
2025-05-03 23:39 ` [PATCH v1 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576 Nicolas Frattaroli
2025-05-04  8:08   ` Heiko Stübner
2025-05-04 10:24 ` [PATCH v2 " John Clark
2025-05-04 10:24   ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add luckfox prefix John Clark
2025-05-04 17:53     ` Krzysztof Kozlowski
2025-05-04 10:24   ` [PATCH v2 2/3] dt-bindings: arm: rockchip: Add Luckfox Omni3576 board John Clark
2025-05-04 17:54     ` Krzysztof Kozlowski
2025-05-04 10:24   ` [PATCH v2 3/3] arm64: dts: rockchip: Add Luckfox Omni3576 Board support John Clark
2025-05-04 13:26     ` Jonas Karlman
2025-05-04 14:12       ` Andrew Lunn
2025-05-04 21:02         ` John Clark
2025-05-04 23:01           ` Andrew Lunn
2025-05-04 23:06             ` John Clark
2025-05-04 23:41             ` John Clark
2025-05-05  0:45               ` Andrew Lunn
2025-05-05  0:52                 ` John Clark
2025-05-05 13:22                   ` Diederik de Haas
2025-05-05 14:01                     ` Andrew Lunn
2025-05-05 10:36                 ` John Clark
2025-05-05 12:38                   ` Andrew Lunn
2025-05-05 12:14     ` Jonas Karlman
2025-05-05 14:44   ` [PATCH v2 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576 Rob Herring (Arm)

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=20250502205533.51744-1-inindev@gmail.com \
    --to=inindev@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=detlev.casanova@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=nicolas.frattaroli@collabora.com \
    --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;
as well as URLs for NNTP newsgroup(s).