From: Andre Przywara <andre.przywara@arm.com>
To: Ivan Uvarov <i.uvarov@cognitivepilot.com>
Cc: devicetree@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Maxime Ripard <mripard@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Icenowy Zheng <icenowy@aosc.io>
Subject: Re: [PATCH v2 3/4] dt-bindings: arm: add compatible strings for Forlinx OKA40i-C
Date: Mon, 22 Mar 2021 16:27:06 +0000 [thread overview]
Message-ID: <20210322162706.2cd9d32a@slackpad.fritz.box> (raw)
In-Reply-To: <20210322105538.3475183-4-i.uvarov@cognitivepilot.com>
On Mon, 22 Mar 2021 13:55:37 +0300
Ivan Uvarov <i.uvarov@cognitivepilot.com> wrote:
Hi,
> The OKA40i-C is a carrier/development board for the Forlinx FETA40i-C SoM
> based on the Allwinner R40/A40i SoC.
>
> This patch adds the relevant dt-binding documentation in preparation for
> the next patch, which adds a devicetree for the SoM and board.
>
> Signed-off-by: Ivan Uvarov <i.uvarov@cognitivepilot.com>
>
> 2 files changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/sunxi.yaml b/Documentation/devicetree/bindings/arm/sunxi.yaml
> index 08607c7ec1..096405aedc 100644
> --- a/Documentation/devicetree/bindings/arm/sunxi.yaml
> +++ b/Documentation/devicetree/bindings/arm/sunxi.yaml
> @@ -224,6 +224,11 @@ properties:
> - const: empire-electronix,m712
> - const: allwinner,sun5i-a13
>
> + - description: Forlinx OKA40i-C Development board
> + items:
> + - const: forlinx,oka40i-c
I think you should add the SoM name in here, compare:
arch/arm64/boot/dts/allwinner/sun50i-a64-sopine-baseboard.dts
Cheers,
Andre
> + - const: allwinner,sun8i-r40
> +
> - description: FriendlyARM NanoPi A64
> items:
> - const: friendlyarm,nanopi-a64
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index f6064d84a4..e2ea1a731e 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -403,6 +403,8 @@ patternProperties:
> description: Firefly
> "^focaltech,.*":
> description: FocalTech Systems Co.,Ltd
> + "^forlinx,.*":
> + description: Baoding Forlinx Embedded Technology Co., Ltd.
> "^frida,.*":
> description: Shenzhen Frida LCD Co., Ltd.
> "^friendlyarm,.*":
next prev parent reply other threads:[~2021-03-22 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 10:55 [PATCH v2 0/4] add devicetree for Forlinx FETA40i-C & OKA40i-C Ivan Uvarov
2021-03-22 10:55 ` [PATCH v2 1/4] ARM: dts: sun8i: r40: add /omit-if-no-ref/ to pinmux nodes for UARTs 0&3 Ivan Uvarov
2021-03-22 16:18 ` Andre Przywara
2021-03-23 9:59 ` Ivan Uvarov
2021-03-25 14:12 ` Maxime Ripard
2021-03-22 10:55 ` [PATCH v2 2/4] ARM: dts: sun8i: r40: add pinmux settings for MMC3 and UARTs 2,4,5&7 Ivan Uvarov
2021-03-22 16:24 ` Andre Przywara
2021-03-22 10:55 ` [PATCH v2 3/4] dt-bindings: arm: add compatible strings for Forlinx OKA40i-C Ivan Uvarov
2021-03-22 16:27 ` Andre Przywara [this message]
2021-03-22 10:55 ` [PATCH v2 4/4] ARM: dts: sun8i: r40: add devicetree for Forlinx FETA40i-C & OKA40i-C Ivan Uvarov
2021-03-22 16:47 ` Andre Przywara
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=20210322162706.2cd9d32a@slackpad.fritz.box \
--to=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=i.uvarov@cognitivepilot.com \
--cc=icenowy@aosc.io \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).