From: Dragan Simic <dsimic@manjaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Jonas Karlman <jonas@kwiboo.se>, Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@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 3/4] dt-bindings: arm: rockchip: Add Radxa ROCK 3B
Date: Mon, 06 May 2024 13:46:15 +0200 [thread overview]
Message-ID: <c306b46bc695a256c35e506d98a08e47@manjaro.org> (raw)
In-Reply-To: <ade304a1-ea43-46cb-b425-b08055db49dc@linaro.org>
Hello Krzysztof,
On 2024-05-06 12:48, Krzysztof Kozlowski wrote:
> On 05/05/2024 15:41, Jonas Karlman wrote:
>> Add devicetree binding documentation for the Radxa ROCK 3B board.
>>
>> The Radxa ROCK 3B is a single-board computer based on the Pico-ITX
>> form
>> factor (100mm x 75mm). Two versions of the ROCK 3B exists, a community
>> version based on the RK3568 SoC and an industrial version based on the
>> RK3568J SoC.
>>
>> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
>> ---
>> 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 51cdaabaf0d9..41f2ab79e612 100644
>> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
>> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
>> @@ -799,6 +799,11 @@ properties:
>> - const: radxa,rock3a
>> - const: rockchip,rk3568
>>
>> + - description: Radxa ROCK 3B
>
> Does not look like it matches recent fixups for names.
Actually, I can confirm that "Radxa ROCK 3B" conforms to the recently
employed naming scheme for Radxa boards.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-05-06 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 13:41 [PATCH 0/4] arm64: dts: rockchip: Add Radxa ROCK 3B Jonas Karlman
2024-05-05 13:41 ` [PATCH 1/4] dt-bindings: mfd: rk809: Fix vcc8 and vcc9-supply description Jonas Karlman
2024-05-06 10:44 ` Krzysztof Kozlowski
2024-05-05 13:41 ` [PATCH 2/4] dt-bindings: mfd: rk809: Add audio codec properties Jonas Karlman
2024-05-05 14:21 ` Rob Herring (Arm)
2024-05-06 10:47 ` Krzysztof Kozlowski
2024-05-06 16:14 ` Jonas Karlman
2024-05-06 20:08 ` Krzysztof Kozlowski
2024-05-05 13:41 ` [PATCH 3/4] dt-bindings: arm: rockchip: Add Radxa ROCK 3B Jonas Karlman
2024-05-06 10:48 ` Krzysztof Kozlowski
2024-05-06 11:46 ` Dragan Simic [this message]
2024-05-06 20:09 ` Krzysztof Kozlowski
2024-05-05 13:41 ` [PATCH 4/4] arm64: dts: " Jonas Karlman
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=c306b46bc695a256c35e506d98a08e47@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@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