From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro
Date: Wed, 18 Jan 2017 14:27:19 -0800 [thread overview]
Message-ID: <m237ggypfc.fsf@baylibre.com> (raw)
In-Reply-To: <3005a457-b7cf-393b-42ff-4149e080321c@suse.de> ("Andreas Färber"'s message of "Wed, 18 Jan 2017 00:06:07 +0100")
Andreas F?rber <afaerber@suse.de> writes:
> Am 17.01.2017 um 04:06 schrieb Andreas F?rber:
>> diff --git a/arch/arm64/boot/dts/amlogic/Makefile b/arch/arm64/boot/dts/amlogic/Makefile
>> index 0d7bfbf7d922..66bc809a5eae 100644
>> --- a/arch/arm64/boot/dts/amlogic/Makefile
>> +++ b/arch/arm64/boot/dts/amlogic/Makefile
>> @@ -12,6 +12,7 @@ dtb-$(CONFIG_ARCH_MESON) += meson-gxl-nexbox-a95x.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-s912-q200.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-s912-q201.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-nexbox-a1.dtb
>
> What is the logic behind meson-gxm-s912-q201 vs. meson-gxm-nexbox-a1?
> Should it be renamed to include -s912 for consistency?
Oops, I think it should be renamed for consistency.
I believe there's only one chip in the GXM family (S912) so it might be
that we could either drop the -s912 from the q20x boards or, add it to
the nexbox.
I lean towards dropping the -s912 since there's a single chip in GXM.
(FWIW, GXL has more than one chip in the family so we added the chip
there.)
>> +dtb-$(CONFIG_ARCH_MESON) += meson-gxm-rbox-pro.dtb
>
> Should this new board use meson-gxm-s912-?
No. Unless Neil or you thing otherwise, I think we should send a patch
to drop the -s912 from the q20x boards instead. (where "we" == Neil) ;)
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro
Date: Wed, 18 Jan 2017 14:27:19 -0800 [thread overview]
Message-ID: <m237ggypfc.fsf@baylibre.com> (raw)
In-Reply-To: <3005a457-b7cf-393b-42ff-4149e080321c@suse.de> ("Andreas Färber"'s message of "Wed, 18 Jan 2017 00:06:07 +0100")
Andreas F?rber <afaerber@suse.de> writes:
> Am 17.01.2017 um 04:06 schrieb Andreas F?rber:
>> diff --git a/arch/arm64/boot/dts/amlogic/Makefile b/arch/arm64/boot/dts/amlogic/Makefile
>> index 0d7bfbf7d922..66bc809a5eae 100644
>> --- a/arch/arm64/boot/dts/amlogic/Makefile
>> +++ b/arch/arm64/boot/dts/amlogic/Makefile
>> @@ -12,6 +12,7 @@ dtb-$(CONFIG_ARCH_MESON) += meson-gxl-nexbox-a95x.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-s912-q200.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-s912-q201.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-nexbox-a1.dtb
>
> What is the logic behind meson-gxm-s912-q201 vs. meson-gxm-nexbox-a1?
> Should it be renamed to include -s912 for consistency?
Oops, I think it should be renamed for consistency.
I believe there's only one chip in the GXM family (S912) so it might be
that we could either drop the -s912 from the q20x boards or, add it to
the nexbox.
I lean towards dropping the -s912 since there's a single chip in GXM.
(FWIW, GXL has more than one chip in the family so we added the chip
there.)
>> +dtb-$(CONFIG_ARCH_MESON) += meson-gxm-rbox-pro.dtb
>
> Should this new board use meson-gxm-s912-?
No. Unless Neil or you thing otherwise, I think we should send a patch
to drop the -s912 from the q20x boards instead. (where "we" == Neil) ;)
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-amlogic@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Carlo Caione <carlo@caione.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro
Date: Wed, 18 Jan 2017 14:27:19 -0800 [thread overview]
Message-ID: <m237ggypfc.fsf@baylibre.com> (raw)
In-Reply-To: <3005a457-b7cf-393b-42ff-4149e080321c@suse.de> ("Andreas Färber"'s message of "Wed, 18 Jan 2017 00:06:07 +0100")
Andreas Färber <afaerber@suse.de> writes:
> Am 17.01.2017 um 04:06 schrieb Andreas Färber:
>> diff --git a/arch/arm64/boot/dts/amlogic/Makefile b/arch/arm64/boot/dts/amlogic/Makefile
>> index 0d7bfbf7d922..66bc809a5eae 100644
>> --- a/arch/arm64/boot/dts/amlogic/Makefile
>> +++ b/arch/arm64/boot/dts/amlogic/Makefile
>> @@ -12,6 +12,7 @@ dtb-$(CONFIG_ARCH_MESON) += meson-gxl-nexbox-a95x.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-s912-q200.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-s912-q201.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-nexbox-a1.dtb
>
> What is the logic behind meson-gxm-s912-q201 vs. meson-gxm-nexbox-a1?
> Should it be renamed to include -s912 for consistency?
Oops, I think it should be renamed for consistency.
I believe there's only one chip in the GXM family (S912) so it might be
that we could either drop the -s912 from the q20x boards or, add it to
the nexbox.
I lean towards dropping the -s912 since there's a single chip in GXM.
(FWIW, GXL has more than one chip in the family so we added the chip
there.)
>> +dtb-$(CONFIG_ARCH_MESON) += meson-gxm-rbox-pro.dtb
>
> Should this new board use meson-gxm-s912-?
No. Unless Neil or you thing otherwise, I think we should send a patch
to drop the -s912 from the q20x boards instead. (where "we" == Neil) ;)
Kevin
next prev parent reply other threads:[~2017-01-18 22:27 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 3:06 [PATCH 0/2] ARM64: meson-gxm: R-Box Pro enablement Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-17 22:54 ` [PATCH 1/3] Documentation: devicetree: Add Kingnovel vendor prefix Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 23:38 ` Kevin Hilman
2017-01-18 23:38 ` Kevin Hilman
2017-01-18 23:38 ` Kevin Hilman
2017-01-18 23:38 ` Kevin Hilman
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-17 22:54 ` [PATCH 3/3] ARM64: dts: meson-gxm-rbox-pro: Add board compatible string Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-21 20:01 ` [PATCH 1/3] Documentation: devicetree: Add Kingnovel vendor prefix Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-17 23:06 ` [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-18 22:27 ` Kevin Hilman [this message]
2017-01-18 22:27 ` Kevin Hilman
2017-01-18 22:27 ` Kevin Hilman
2017-01-19 8:10 ` Neil Armstrong
2017-01-19 8:10 ` Neil Armstrong
2017-01-19 8:10 ` Neil Armstrong
2017-01-17 3:06 ` [PATCH 2/2] ARM64: dts: meson-gxm-rbox-pro: Enable Bluetooth Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` 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=m237ggypfc.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.