From: Neil Armstrong <narmstrong@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: amlogic: add support for the Tanix TX5 Max
Date: Tue, 3 Mar 2020 15:49:02 +0100 [thread overview]
Message-ID: <ab65c3db-1b8b-3148-efcf-a9cfae9ae9f7@baylibre.com> (raw)
In-Reply-To: <1582991214-85209-2-git-send-email-christianshewitt@gmail.com>
On 29/02/2020 16:46, Christian Hewitt wrote:
> The Oranth (Tanix) TX5 Max is based on the Amlogic U200 reference
> board with an S905X2 chip.
>
> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/amlogic.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/amlogic.yaml b/Documentation/devicetree/bindings/arm/amlogic.yaml
> index f74aba4..4003206 100644
> --- a/Documentation/devicetree/bindings/arm/amlogic.yaml
> +++ b/Documentation/devicetree/bindings/arm/amlogic.yaml
> @@ -136,6 +136,7 @@ properties:
> - amediatech,x96-max
> - amlogic,u200
> - seirobotics,sei510
> + - oranth,tx5-max
> - const: amlogic,g12a
>
> - description: Boards with the Amlogic Meson G12B A311D SoC
>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
next prev parent reply other threads:[~2020-03-03 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 15:46 [PATCH 0/2] arm64: dts: meson: add dts/bindings for Tanix TX5 Max Christian Hewitt
2020-02-29 15:46 ` [PATCH 1/2] dt-bindings: arm: amlogic: add support for the " Christian Hewitt
2020-03-03 14:49 ` Neil Armstrong [this message]
2020-03-10 18:59 ` Rob Herring
2020-02-29 15:46 ` [PATCH 2/2] arm64: dts: meson-g12a-tanix-tx5max: add initial device tree Christian Hewitt
2020-03-03 14:48 ` Neil Armstrong
2020-03-05 8:15 ` Jerome Brunet
2020-03-16 16:49 ` Kevin Hilman
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=ab65c3db-1b8b-3148-efcf-a9cfae9ae9f7@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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).