From: Conor Dooley <conor@kernel.org>
To: Dmitry Yashin <dmt.yashin@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.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
Subject: Re: [PATCH 1/3] dt-bindings: arm: rockchip: add Forlinx FET3588-C
Date: Sun, 17 Mar 2024 14:53:25 +0000 [thread overview]
Message-ID: <20240317-graded-splicing-0d37dc7429e4@spud> (raw)
In-Reply-To: <2c7a99673ab4840bc7052eb600363d5163c5cfae.1710506373.git.dmt.yashin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
On Fri, Mar 15, 2024 at 07:18:05PM +0500, Dmitry Yashin wrote:
> FET3588-C is an System on Module made by Forlinx based on Rockchip RK3588.
> This SoM used by OK3588-C Board.
>
> FET3588-C features:
> - Rockchip RK3588
> - LPDDR4 4/8 GB
> - eMMC 32/64 GB
>
> Add devicetree binding for Forlinx FET3588-C SoM.
>
> Signed-off-by: Dmitry Yashin <dmt.yashin@gmail.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
> ---
> Documentation/devicetree/bindings/arm/rockchip.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
> index 5cf5cbef2cf5..d87f4955f509 100644
> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> @@ -211,6 +211,13 @@ properties:
> - const: firefly,rk3568-roc-pc
> - const: rockchip,rk3568
>
> + - description: Forlinx FET3588-C SoM
> + items:
> + - enum:
> + - forlinx,ok3588-c
> + - const: forlinx,fet3588-c
> + - const: rockchip,rk3588
> +
> - description: FriendlyElec NanoPi R2 series boards
> items:
> - enum:
> --
> 2.44.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-17 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 14:18 [PATCH 0/3] Add Forlinx OK3588-C Dmitry Yashin
2024-03-15 14:18 ` [PATCH 1/3] dt-bindings: arm: rockchip: add Forlinx FET3588-C Dmitry Yashin
2024-03-17 14:53 ` Conor Dooley [this message]
2024-03-15 14:18 ` [PATCH 2/3] arm64: dts: " Dmitry Yashin
2024-03-15 14:18 ` [PATCH 3/3] arm64: dts: rockchip: add Forlinx OK3588-C Dmitry Yashin
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=20240317-graded-splicing-0d37dc7429e4@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmt.yashin@gmail.com \
--cc=heiko@sntech.de \
--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=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).