From: Rob Herring <robh@kernel.org>
To: Ivan Uvarov <i.uvarov@cognitivepilot.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Icenowy Zheng <icenowy@aosc.io>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Maxime Ripard <mripard@kernel.org>,
Andre Przywara <andre.przywara@arm.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v3 3/4] dt-bindings: arm: add compatible strings for Forlinx OKA40i-C
Date: Thu, 1 Apr 2021 11:59:47 -0500 [thread overview]
Message-ID: <20210401165947.GA608122@robh.at.kernel.org> (raw)
In-Reply-To: <20210331155616.793550-4-i.uvarov@cognitivepilot.com>
On Wed, 31 Mar 2021 18:56:15 +0300, Ivan Uvarov wrote:
> 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, 8 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-04-01 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 15:56 [PATCH v3 0/4] add devicetree for Forlinx FETA40i-C & OKA40i-C Ivan Uvarov
2021-03-31 15:56 ` [PATCH v3 1/4] ARM: dts: sun8i: r40: add /omit-if-no-ref/ to pinmux nodes for UARTs 0&3 Ivan Uvarov
2021-03-31 15:56 ` [PATCH v3 2/4] ARM: dts: sun8i: r40: add pinmux settings for MMC3 and UARTs 2,4,5&7 Ivan Uvarov
2021-04-01 9:39 ` Maxime Ripard
2021-03-31 15:56 ` [PATCH v3 3/4] dt-bindings: arm: add compatible strings for Forlinx OKA40i-C Ivan Uvarov
2021-04-01 9:40 ` Maxime Ripard
2021-04-01 14:55 ` Ivan Uvarov
2021-04-07 7:23 ` Maxime Ripard
2021-04-01 16:59 ` Rob Herring [this message]
2021-03-31 15:56 ` [PATCH v3 4/4] ARM: dts: sun8i: r40: add devicetree for Forlinx FETA40i-C & OKA40i-C Ivan Uvarov
2021-04-01 9:43 ` Maxime Ripard
2021-04-01 14:59 ` Ivan Uvarov
2021-04-07 7:30 ` Maxime Ripard
2021-04-01 14:02 ` 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=20210401165947.GA608122@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=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).