From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [RFC PATCH] ARM64: dts: Add support for Meson GXM
Date: Mon, 14 Nov 2016 11:17:19 -0800 [thread overview]
Message-ID: <7hlgwl6fcw.fsf@baylibre.com> (raw)
In-Reply-To: <20161114094411.30199-1-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 14 Nov 2016 10:44:11 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Following the Amlogic Linux kernel, it seem the only differences
> between the GXL and GXM SoCs are the CPU Clusters.
>
> Simply add a meson-gxm dtsi and reproduce the P23x to Q20x boards
> dts files since the S905D and S912 SoCs shares the same pinout
> and the P23x and Q20x boards are identical.
Since the P23x and Q20x boards are identical, should we just come up
with a singel dtsi for them all? e.g move the -p23x.dtsi to -pq2xx.dtsi
or something?
I don't think it's a big deal, but it does seem like we should avoid the
copy/paste wherever possible.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM64: dts: Add support for Meson GXM
Date: Mon, 14 Nov 2016 11:17:19 -0800 [thread overview]
Message-ID: <7hlgwl6fcw.fsf@baylibre.com> (raw)
In-Reply-To: <20161114094411.30199-1-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 14 Nov 2016 10:44:11 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Following the Amlogic Linux kernel, it seem the only differences
> between the GXL and GXM SoCs are the CPU Clusters.
>
> Simply add a meson-gxm dtsi and reproduce the P23x to Q20x boards
> dts files since the S905D and S912 SoCs shares the same pinout
> and the P23x and Q20x boards are identical.
Since the P23x and Q20x boards are identical, should we just come up
with a singel dtsi for them all? e.g move the -p23x.dtsi to -pq2xx.dtsi
or something?
I don't think it's a big deal, but it does seem like we should avoid the
copy/paste wherever possible.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: carlo@caione.org, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [RFC PATCH] ARM64: dts: Add support for Meson GXM
Date: Mon, 14 Nov 2016 11:17:19 -0800 [thread overview]
Message-ID: <7hlgwl6fcw.fsf@baylibre.com> (raw)
In-Reply-To: <20161114094411.30199-1-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 14 Nov 2016 10:44:11 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Following the Amlogic Linux kernel, it seem the only differences
> between the GXL and GXM SoCs are the CPU Clusters.
>
> Simply add a meson-gxm dtsi and reproduce the P23x to Q20x boards
> dts files since the S905D and S912 SoCs shares the same pinout
> and the P23x and Q20x boards are identical.
Since the P23x and Q20x boards are identical, should we just come up
with a singel dtsi for them all? e.g move the -p23x.dtsi to -pq2xx.dtsi
or something?
I don't think it's a big deal, but it does seem like we should avoid the
copy/paste wherever possible.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: carlo@caione.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RFC PATCH] ARM64: dts: Add support for Meson GXM
Date: Mon, 14 Nov 2016 11:17:19 -0800 [thread overview]
Message-ID: <7hlgwl6fcw.fsf@baylibre.com> (raw)
In-Reply-To: <20161114094411.30199-1-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 14 Nov 2016 10:44:11 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Following the Amlogic Linux kernel, it seem the only differences
> between the GXL and GXM SoCs are the CPU Clusters.
>
> Simply add a meson-gxm dtsi and reproduce the P23x to Q20x boards
> dts files since the S905D and S912 SoCs shares the same pinout
> and the P23x and Q20x boards are identical.
Since the P23x and Q20x boards are identical, should we just come up
with a singel dtsi for them all? e.g move the -p23x.dtsi to -pq2xx.dtsi
or something?
I don't think it's a big deal, but it does seem like we should avoid the
copy/paste wherever possible.
Kevin
next prev parent reply other threads:[~2016-11-14 19:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 9:44 [RFC PATCH] ARM64: dts: Add support for Meson GXM Neil Armstrong
2016-11-14 9:44 ` Neil Armstrong
2016-11-14 9:44 ` Neil Armstrong
2016-11-14 19:17 ` Kevin Hilman [this message]
2016-11-14 19:17 ` Kevin Hilman
2016-11-14 19:17 ` Kevin Hilman
2016-11-14 19:17 ` Kevin Hilman
2016-11-16 0:13 ` Rob Herring
2016-11-16 0:13 ` Rob Herring
2016-11-16 0:13 ` Rob Herring
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=7hlgwl6fcw.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.