public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: FUKAUMI Naoki <naoki@radxa.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: rockchip: add support for Radxa ROCK Pi E v3.0
Date: Wed, 14 Aug 2024 13:32:36 +0200	[thread overview]
Message-ID: <10385642.ICPdZLu4VQ@diego> (raw)
In-Reply-To: <8FF4228B18A1DFEE+d359188b-64e9-4ce6-8796-f3fecd6a0781@radxa.com>

Am Mittwoch, 14. August 2024, 12:25:54 CEST schrieb FUKAUMI Naoki:
> Hi,
> 
> On 8/14/24 18:57, FUKAUMI Naoki wrote:
> > Radxa ROCK Pi E v3.0 is a compact networking SBC[1] using the Rockchip
> > RK3328 chip.
> > 
> > [1] https://radxa.com/products/rockpi/pie
> > 
> > Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>
> > ---
> > Changes in v4:
> > - update compatible string for OpenWrt
> 
> this is for https://github.com/openwrt/openwrt/issues/16168

I this because openwrt used some out-of-tree devicetree?

For people reading along, all the other rockpi devices follow a

	radxa,rockpi-foo

naming scheme in their compatibles while _this_ new entry uses

	 radxa,rock-pi-e-v3


Heiko



  reply	other threads:[~2024-08-14 11:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14  9:57 [PATCH v4 1/2] dt-bindings: arm: rockchip: add support for Radxa ROCK Pi E v3.0 FUKAUMI Naoki
2024-08-14  9:57 ` [PATCH v4 2/2] arm64: dts: " FUKAUMI Naoki
2024-08-14 10:25 ` [PATCH v4 1/2] dt-bindings: arm: " FUKAUMI Naoki
2024-08-14 11:32   ` Heiko Stübner [this message]
2024-08-14 20:18     ` FUKAUMI Naoki
2024-08-14 11:30 ` Heiko Stübner
2024-08-14 20:04   ` FUKAUMI Naoki
2024-08-14 21:53     ` Heiko Stübner
2024-08-14 21:55       ` FUKAUMI Naoki
2024-08-14 15:48 ` 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=10385642.ICPdZLu4VQ@diego \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=naoki@radxa.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