From: Rob Herring <robh@kernel.org>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
Suniel Mahesh <sunil@amarulasolutions.com>,
linux-amarula <linux-amarula@amarulasolutions.com>,
linux-kernel@vger.kernel.org,
Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: [PATCH v4 1/4] dt-bindings: arm: rockchip: Update ROCKPi 4 binding
Date: Mon, 17 Aug 2020 16:12:09 -0600 [thread overview]
Message-ID: <20200817221209.GA1667089@bogus> (raw)
In-Reply-To: <20200807094826.12019-1-jagan@amarulasolutions.com>
On Fri, 07 Aug 2020 15:18:23 +0530, Jagan Teki wrote:
> ROCKPi 4 has 3 variants of hardware platforms called
> ROCKPi 4A, 4B, and 4C.
>
> - ROCKPi 4A has no Wif/BT.
> - ROCKPi 4B has AP6256 Wifi/BT, PoE.
> - ROCKPi 4C has AP6256 Wifi/BT, PoE, miniDP, USB Host enabled
> GPIO pin change compared to 4B, 4C
>
> So, update the existing ROCKPi 4 binding to support
> ROCKPi 4A/B/C hardware platforms.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> Changes for v4:
> - update binding to satisfy dt_binding_check.
> Changes for v3:
> - new patch
>
> Documentation/devicetree/bindings/arm/rockchip.yaml | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-08-17 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 9:48 [PATCH v4 1/4] dt-bindings: arm: rockchip: Update ROCKPi 4 binding Jagan Teki
2020-08-07 9:48 ` [PATCH v4 2/4] arm64: dts: rockchip: Mark rock-pi-4 as rock-pi-4a dts Jagan Teki
2020-08-07 9:48 ` [PATCH v4 3/4] arm64: dts: rockchip: Add Radxa ROCK Pi 4B support Jagan Teki
2020-08-07 9:48 ` [PATCH v4 4/4] arm64: dts: rockchip: Add Radxa ROCK Pi 4C support Jagan Teki
2020-08-17 22:12 ` Rob Herring [this message]
2020-08-30 19:42 ` [PATCH v4 1/4] dt-bindings: arm: rockchip: Update ROCKPi 4 binding 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=20200817221209.GA1667089@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael@amarulasolutions.com \
--cc=robh+dt@kernel.org \
--cc=sunil@amarulasolutions.com \
/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).