From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>
Cc: Hrushiraj Gandhi <hrushirajg23@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/2] arm64: dts: rockchip: add Vicharak Axon board support
Date: Tue, 07 Jul 2026 20:23:47 +0200 [thread overview]
Message-ID: <14045151.uLZWGnKmhe@phil> (raw)
In-Reply-To: <20260707160354.GB3176120-robh@kernel.org>
Am Dienstag, 7. Juli 2026, 18:03:54 Mitteleuropäische Sommerzeit schrieb Rob Herring:
> On Thu, Jul 02, 2026 at 09:04:55PM +0200, Heiko Stuebner wrote:
> >
> > On Mon, 08 Jun 2026 11:39:38 +0530, Hrushiraj Gandhi wrote:
> > > This series adds initial device tree support for the Vicharak Axon
> > > single-board computer, which is based on the Rockchip RK3588 SoC.
> > >
> > > The Vicharak Axon is a feature-rich SBC targeting developer and embedded
> > > use cases. It ships with:
> > >
> > > - Rockchip RK3588 (4x Cortex-A76 + 4x Cortex-A55)
> > > - RK806 PMIC providing all SoC power domains
> > > - eMMC 5.1 (on-board) and microSD slot
> > > - Gigabit Ethernet via RGMII (RTL8211F)
> > > - Dual HDMI 2.1 output and one HDMI 2.0 input (receiver)
> > > - PCIe 3.0 x4 and two PCIe 2.0 slots
> > > - SATA 3.0
> > > - USB 2.0 host ports (EHCI/OHCI)
> > > - NXP PCA9554 I/O expander for status LEDs
> > > - Haoyu HYM8563 RTC
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/2] dt-bindings: arm: rockchip: add Vicharak Axon board
> > commit: e0008b108aaf8c5aa22930b2ceadf8f894562acb
> > [2/2] arm64: dts: rockchip: add Vicharak Axon board
> > commit: e08c3389c78dbefd31a57df8807cf57ef6f3c9b1
>
> Both have issues and should be dropped.
I've dropped both the Axon as well as the Vaaman2 board from the
same vendor now.
The whole thing is confusing.
I should've caught the pinctrl issue, and do remember running a dtbscheck
on at least one Vcharak board - but that must have been the Vaaman2 board
because there the pmic fullfills the binding (and general setup of other
rk3588 boards).
The vendor-prefix is missing indeed. I found earlier versions of the
version-avalanche had it, up until v6 [0] . Though I haven't figured out
yet why it was lost.
Hence I dropped both boards.
Hrushiraj: please start anew with both boards.
But include all the tags you received in previous versions.
Heiko
[0] https://lore.kernel.org/linux-rockchip/20260601162143.170030-2-hrushirajg23@gmail.com/
next prev parent reply other threads:[~2026-07-07 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 6:09 [PATCH v7 0/2] arm64: dts: rockchip: add Vicharak Axon board support Hrushiraj Gandhi
2026-06-08 6:09 ` [PATCH v7 1/2] dt-bindings: arm: rockchip: add Vicharak Axon board Hrushiraj Gandhi
2026-06-08 6:09 ` [PATCH v7 2/2] arm64: dts: " Hrushiraj Gandhi
2026-06-20 5:37 ` [PATCH v7 0/2] arm64: dts: rockchip: add Vicharak Axon board support Hrushiraj Gandhi
2026-07-07 16:02 ` Rob Herring
2026-07-02 19:04 ` Heiko Stuebner
2026-07-07 16:03 ` Rob Herring
2026-07-07 18:23 ` Heiko Stuebner [this message]
2026-07-08 10:21 ` Hrushiraj Gandhi
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=14045151.uLZWGnKmhe@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hrushirajg23@gmail.com \
--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=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