From: Tim Lunn <tim@feathertop.org>
To: linux-rockchip@lists.infradead.org
Cc: Andy Yan <andyshrk@163.com>,
Chris Morgan <macromorgan@hotmail.com>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, Jagan Teki <jagan@edgeble.ai>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Ondrej Jirman <megi@xff.cz>, Rob Herring <robh+dt@kernel.org>,
Tianling Shen <cnsztl@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: arm: rockchip: Correct vendor for Orange Pi RK3399 board
Date: Thu, 15 Feb 2024 10:45:39 +1100 [thread overview]
Message-ID: <0e6cee7c-9726-4d45-a06a-a8882e271e7b@feathertop.org> (raw)
In-Reply-To: <20240214040731.3069111-2-tim@feathertop.org>
On 2/14/24 15:07, Tim Lunn wrote:
> The vendor for this board was incorrectly listed as Rockchip. Fix this
> now while they are not used anywhere, in the future they may be used by
> bootloader to select dts.
>
> Update the vendor to Xunlong.
>
> Signed-off-by: Tim Lunn <tim@feathertop.org>
Fixes: 08b64bd2c681 ("arm64: dts: rockchip: Add support for the Orange
Pi RK3399 board")
> ---
>
> Documentation/devicetree/bindings/arm/rockchip.yaml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
> index 5cf5cbef2cf5..29f922f3ca4e 100644
> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> @@ -626,9 +626,9 @@ properties:
> - const: openailab,eaidk-610
> - const: rockchip,rk3399
>
> - - description: Orange Pi RK3399 board
> + - description: Xunlong Orange Pi RK3399 board
> items:
> - - const: rockchip,rk3399-orangepi
> + - const: xunlong,rk3399-orangepi
> - const: rockchip,rk3399
>
> - description: Phytec phyCORE-RK3288 Rapid Development Kit
next prev parent reply other threads:[~2024-02-14 23:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 4:07 [PATCH 0/4] Fix vendor strings on Rockchip boards Tim Lunn
2024-02-14 4:07 ` [PATCH 1/4] dt-bindings: arm: rockchip: Correct vendor for Orange Pi RK3399 board Tim Lunn
2024-02-14 23:45 ` Tim Lunn [this message]
2024-02-15 15:09 ` Rob Herring
2024-02-14 4:07 ` [PATCH 2/4] dt-bindings: arm: rockchip: Correct vendor for Banana Pi R2 Pro Tim Lunn
2024-02-14 23:37 ` Tim Lunn
2024-02-15 15:10 ` Rob Herring
2024-02-14 4:07 ` [PATCH 3/4] arm64: dts: rockchip: adjust vendor on Banana Pi R2 Pro board Tim Lunn
2024-02-14 4:07 ` [PATCH 4/4] arm64: dts: rockchip: adjust vendor on orangepi rk3399 board Tim Lunn
2024-02-14 4:14 ` [PATCH 0/4] Fix vendor strings on Rockchip boards Dragan Simic
2024-02-14 4:27 ` Tim Lunn
2024-02-14 18:12 ` Conor Dooley
2024-02-14 18:30 ` Dragan Simic
2024-02-15 0:28 ` Tim Lunn
2024-02-27 23:13 ` Heiko Stuebner
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=0e6cee7c-9726-4d45-a06a-a8882e271e7b@feathertop.org \
--to=tim@feathertop.org \
--cc=andyshrk@163.com \
--cc=cnsztl@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jagan@edgeble.ai \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=megi@xff.cz \
--cc=robh+dt@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).