From: Christopher Obbard <chris.obbard@collabora.com>
To: Conor Dooley <conor@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: rockchip: add Firefly CORE PX30 JD4
Date: Tue, 16 Jul 2024 17:36:35 +0100 [thread overview]
Message-ID: <9f336131235de9f39a02b6bccb4d3d9a8f296bf3.camel@collabora.com> (raw)
In-Reply-To: <20240716-wrinkly-carving-686b84bc0933@spud>
On Tue, 2024-07-16 at 17:26 +0100, Conor Dooley wrote:
> On Tue, Jul 16, 2024 at 04:51:04PM +0100, Christopher Obbard wrote:
> > The Firefly CORE PX30 JD4 board is a SOM and motherboard bundle from
> > Firefly. Add devicetree binding documentation for it.
> >
> > Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>
> > ---
> > Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml
> > b/Documentation/devicetree/bindings/arm/rockchip.yaml
> > index e04c213a0dee4..19e06e1253e15 100644
> > --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> > +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> > @@ -148,6 +148,11 @@ properties:
> > - const: engicam,px30-core
> > - const: rockchip,px30
> >
> > + - description: Firefly Core PX30 JD4
> > + items:
> > + - const: firefly,core-px30-jd4
> > + - const: rockchip,px30
>
> Not having individual compatibles for the carrier and som seems odd to,
> given there's no requirement to use the som with this particular
> carrier.
Thanks, I will fix that up in V2.
>
> > +
> > - description: Firefly Firefly-RK3288
> > items:
> > - enum:
> >
> > --
> > 2.45.2
> >
next prev parent reply other threads:[~2024-07-16 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 15:51 [PATCH 0/2] Add support for Firefly CORE PX30 JD4 Christopher Obbard
2024-07-16 15:51 ` [PATCH 1/2] dt-bindings: arm: rockchip: add " Christopher Obbard
2024-07-16 16:26 ` Conor Dooley
2024-07-16 16:36 ` Christopher Obbard [this message]
2024-07-16 15:51 ` [PATCH 2/2] arm64: dts: " Christopher Obbard
2024-07-16 17:45 ` [PATCH 0/2] Add support for " Dragan Simic
2024-07-16 20:07 ` Heiko Stübner
2024-07-16 21:12 ` 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=9f336131235de9f39a02b6bccb4d3d9a8f296bf3.camel@collabora.com \
--to=chris.obbard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.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;
as well as URLs for NNTP newsgroup(s).