From: xypron.glpk@gmx.de (Heinrich Schuchardt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1 v2] imx6q-wandboard-revb1.dts: use unique machine name
Date: Mon, 8 Feb 2016 01:25:15 +0100 [thread overview]
Message-ID: <56B7E06B.2060701@gmx.de> (raw)
In-Reply-To: <CAOCHtYiHUgcw6Vzdp8EmD_5+d52fhpuj-oSCFwt_3J5xAncCGw@mail.gmail.com>
On 08.02.2016 00:52, Robert Nelson wrote:
> On Sat, Feb 6, 2016 at 6:06 AM, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>> Downstream packages like Debian flash-kernel use
>> /proc/device-tree/model
>> to determine which dtb file to install.
>>
>> Hence each dts in the Linux kernel should provide a unique model identifier.
>>
>> https://lkml.org/lkml/2014/7/8/579 created the new file
>> imx6q-wandboard-revb1.dts but used the same model identifier
>> as in imx6q-wandboard.dts.
>>
>> This patch provides a unique model identifier for revision B1 of
>> the Wandboard Quad.
>>
>> v2:
>> correct name of referenced Debian package
>>
>> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
>> ---
>> arch/arm/boot/dts/imx6q-wandboard-revb1.dts | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/imx6q-wandboard-revb1.dts b/arch/arm/boot/dts/imx6q-wandboard-revb1.dts
>> index 20bf3c2..9207d80 100644
>> --- a/arch/arm/boot/dts/imx6q-wandboard-revb1.dts
>> +++ b/arch/arm/boot/dts/imx6q-wandboard-revb1.dts
>> @@ -13,7 +13,7 @@
>> #include "imx6qdl-wandboard-revb1.dtsi"
>>
>> / {
>> - model = "Wandboard i.MX6 Quad Board";
>> + model = "Wandboard i.MX6 Quad Board rev B1";
>
> Okay, this seems a little silly....
>
> The wandboard has 5 versions:
>
> solo: imx6dl-wandboard-revb1.dts
>
> model = "Wandboard i.MX6 Dual Lite Board";
>
> dual rev b: imx6dl-wandboard-revb1.dts
>
> model = "Wandboard i.MX6 Dual Lite Board";
>
> dual rev c: imx6dl-wandboard.dts
>
> model = "Wandboard i.MX6 Dual Lite Board";
>
> quad rev b: imx6q-wandboard-revb1.dts
> model = "Wandboard i.MX6 Quad Board"; - > model = "Wandboard i.MX6
> Quad Board rev B1";
>
> quad rev c: imx6q-wandboard.dts
> model = "Wandboard i.MX6 Quad Board";
>
>
> Do you guys see the issue? Either we change them "ALL", rev b or rev c...
>
> Or "flash-kernel" needs to learn to copy more then one dtb (in this
> case 5 *.dtb's)
>
> PS, u-boot already can boot on all these with the same SPL/u-boot
> image and detect which board and load the correct device tree binary..
>
> Regards,
>
Hello Robert,
I only see four dts files mentioned in your mail (solo using the same as
dual rev B1).
We do not know if imx6dl-wandboard.dts and imx6q-wandboard.dts
will support future revisions of the boards. So it doesn't make
much sense to mark them as restricted to revision C1.
You are right in that we should add a change to
imx6dl-wandboard-revb1.dts to the same patch.
Best regards
Heinrich Schuchardt
next prev parent reply other threads:[~2016-02-08 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 11:30 [PATCH 1/1] imx6q-wandboard-revb1.dts: use unique machine name Heinrich Schuchardt
2016-02-06 12:06 ` [PATCH 1/1 v2] " Heinrich Schuchardt
2016-02-07 15:19 ` Fabio Estevam
2016-02-07 23:52 ` Robert Nelson
2016-02-08 0:25 ` Heinrich Schuchardt [this message]
2016-02-08 0:55 ` [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Heinrich Schuchardt
2016-02-14 7:02 ` Shawn Guo
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=56B7E06B.2060701@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).