From: Kevin Hilman <khilman@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: "Christian Hewitt" <christianshewitt@gmail.com>,
"Andreas Färber" <afaerber@suse.de>,
"Jerôme Brunet" <jbrunet@baylibre.com>
Subject: Re: [PATCH v7 3/3] arm64: dts: meson: add support for the SmartLabs SML-5442TW
Date: Mon, 16 Mar 2020 09:36:43 -0700 [thread overview]
Message-ID: <7ha74gw92c.fsf@baylibre.com> (raw)
In-Reply-To: <1583987886-6288-4-git-send-email-christianshewitt@gmail.com>
Christian Hewitt <christianshewitt@gmail.com> writes:
> The SmartLabs SML-5442TW is broadly similar to the P231 reference design
> but with the following differences:
Can you can create a P231 .dtsi that can be shared between the two?
I'd really like to keep all of these designs that are based on Amlogic
ref designs using shared .dtsi whereever possible.
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-03-16 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 4:38 [PATCH v7 0/3] arm64: dts: meson: add dts/bindings for SmartLabs SML-5442TW Christian Hewitt
2020-03-12 4:38 ` [PATCH v7 1/3] dt-bindings: add vendor prefix for SmartLabs LLC Christian Hewitt
2020-03-12 4:38 ` [PATCH v7 2/3] dt-bindings: arm: amlogic: add support for the SmartLabs SML-5442TW Christian Hewitt
2020-03-12 4:38 ` [PATCH v7 3/3] arm64: dts: meson: " Christian Hewitt
2020-03-13 8:51 ` Neil Armstrong
2020-03-16 16:36 ` Kevin Hilman [this message]
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=7ha74gw92c.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=afaerber@suse.de \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@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).