From: Krzysztof Kozlowski <krzk@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: heiko@sntech.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Fabio Estevam <festevam@nabladev.com>
Subject: Re: [PATCH 10/11] dt-bindings: arm: rockchip: Add Onion RV1103B Omega4
Date: Sat, 7 Feb 2026 11:56:58 +0100 [thread overview]
Message-ID: <20260207-quixotic-ochre-tiger-b1760f@quoll> (raw)
In-Reply-To: <20260206181309.2696095-11-festevam@gmail.com>
On Fri, Feb 06, 2026 at 03:13:08PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@nabladev.com>
>
> Onion Omega4 board is a board based on the RV1103B SoC.
>
> Signed-off-by: Fabio Estevam <festevam@nabladev.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 ae77ded9fe47..40c6f7f90755 100644
> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> @@ -793,6 +793,11 @@ properties:
> - lunzn,fastrhino-r68s
> - const: rockchip,rk3568
>
> + - description: Onion RV1103B Omega4 board
What's with the sorting? Why is this between L and M?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-07 10:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 18:12 [PATCH 00/11] ARM: rockchip: Add initial RV1103B and Omega4 board support Fabio Estevam
2026-02-06 18:12 ` [PATCH 01/11] dt-bindings: clock: rockchip: Add RV1103B clock and reset unit Fabio Estevam
2026-02-07 10:54 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 02/11] dt-bindings: clk: rockchip: Add RV1103B clock header Fabio Estevam
2026-02-06 20:15 ` Jonas Karlman
2026-02-07 11:00 ` Krzysztof Kozlowski
2026-02-07 11:01 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 03/11] clk: rockchip: Add clock controller for the RV1103B Fabio Estevam
2026-02-06 18:13 ` [PATCH 04/11] dt-bindings: pinctrl: Add RV1103B pinctrl support Fabio Estevam
2026-02-06 18:13 ` [PATCH 05/11] pinctrl: rockchip: " Fabio Estevam
2026-02-06 18:13 ` [PATCH 06/11] dt-bindings: mmc: rockchip-dw-mshc: Add compatible string for R1103B Fabio Estevam
2026-02-07 10:58 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 07/11] dt-bindings: serial: snps-dw-apb-uart: Add support for RV1103B Fabio Estevam
2026-02-07 10:59 ` Krzysztof Kozlowski
2026-02-07 11:09 ` Greg Kroah-Hartman
2026-02-06 18:13 ` [PATCH 08/11] dt-bindings: soc: rockchip: Add RV1103B IOC and GRF entries Fabio Estevam
2026-02-07 11:03 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 09/11] ARM: dts: rockchip: Add support for RV1103B Fabio Estevam
2026-02-06 18:13 ` [PATCH 10/11] dt-bindings: arm: rockchip: Add Onion RV1103B Omega4 Fabio Estevam
2026-02-07 10:56 ` Krzysztof Kozlowski [this message]
2026-02-06 18:13 ` [PATCH 11/11] ARM: dts: " Fabio Estevam
2026-02-06 20:50 ` Jonas Karlman
2026-02-07 10:55 ` [PATCH 00/11] ARM: rockchip: Add initial RV1103B and Omega4 board support Krzysztof Kozlowski
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=20260207-quixotic-ochre-tiger-b1760f@quoll \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=festevam@nabladev.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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