From: afaerber@suse.de (Andreas Färber)
To: linus-amlogic@lists.infradead.org
Subject: [RFC PATCH 0/3] ARm64: amlogic: Introduce common GX family dtsi
Date: Mon, 29 Aug 2016 20:38:31 +0200 [thread overview]
Message-ID: <2983d731-82fd-63fc-7541-8c1d6a929416@suse.de> (raw)
In-Reply-To: <CAOQ7t2YGbASh7v25wgDspKNWgFOcRsikJs_WZptn+LkVXmaHig@mail.gmail.com>
Am 29.08.2016 um 10:01 schrieb Carlo Caione:
> On Mon, Aug 29, 2016 at 9:56 AM, Neil Armstrong <narmstrong@baylibre.com> wrote:
>> The new Amlogic GLX SoCs (S905X and S905D) are part of the Meson GX family so
>> they share some basic characteritics that can be described in a common GX
>> dtsi file used by the Meson GXBB and Meson GXL dtsi.
>>
>> This patchset introduces the common dtsi and switches the GLX and GXBB to use
>> the common dtsi, the GXBB dtsi is reformated to handle this situation.
>>
>> This patchset depends on Carlo Caione "ARM64: dts: amlogic: Add basic support for Amlogic S905X" [1]
>>
>> [1] http://lkml.kernel.org/r/1472382113-10754-1-git-send-email-carlo at caione.org
>>
>> Neil Armstrong (3):
>> ARM64: dts: amlogic: Add Meson GX Family common dtsi
>> ARM64: dts: amlogic: Switch Meson GXL dtsi to use common GX dtsi
>> ARM64: dts: amlogic: Switch Meson GXBB dtsi to use common GX dtsi
>
> FWIW
> Acked-by: Carlo Caione <carlo@endlessm.com>
Adding an unused .dtsi duplicating GXBB makes me uneasy.
Any chance we can simplify this to at most two steps?
1) Move code from gxbb to gx (1/3 + 3/3)
2) Add gxl using gx ("Add basic support for Amlogic S905X" + 2/3)
Alternatively:
1) "Add basic support for Amlogic S905X"
2) Factor out common bits (1/3 + 2/3 + 3/3)
As for bike-shedding, is there a GX family as well or could we drop
-common? .dtsi is always something common - compare Exynos or i.MX.
Since there are meson8b and meson8 I was anticipating that after gxbb
would come gx, not gxl.
Do you know what the L in GXL is for? Should we consider renaming gxbb
to gxb, and then also insert -s905 as suggested by Kevin, for symmetry?
U-Boot is still in an early stage with $fdtfile issues remaining that I
need to iterate over; DT compatible strings would need to remain though.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2016-08-29 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 7:56 Neil Armstrong
2016-08-29 7:56 ` [RFC PATCH 1/3] ARM64: dts: amlogic: Add Meson GX Family common dtsi Neil Armstrong
2016-08-29 7:56 ` [RFC PATCH 2/3] ARM64: dts: amlogic: Switch Meson GXL dtsi to use common GX dtsi Neil Armstrong
2016-08-29 7:56 ` [RFC PATCH 3/3] ARM64: dts: amlogic: Switch Meson GXBB " Neil Armstrong
2016-08-29 8:01 ` [RFC PATCH 0/3] ARm64: amlogic: Introduce common GX family dtsi Carlo Caione
2016-08-29 18:38 ` Andreas Färber [this message]
2016-08-29 19:50 ` Carlo Caione
2016-08-29 20:15 ` Andreas Färber
2016-08-30 8:33 ` Neil Armstrong
2016-08-31 19:32 ` 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=2983d731-82fd-63fc-7541-8c1d6a929416@suse.de \
--to=afaerber@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®