From: Nishanth Menon <nm@ti.com>
To: florian.vaussard@epfl.ch, "Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>
Cc: Tero Kristo <t-kristo@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
Kevin Hilman <khilman@linaro.org>,
Mike Turquette <mturquette@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: dts: Add support for both OMAP35xx and OMAP36xx Overo/Tobi
Date: Thu, 6 Feb 2014 09:18:21 -0600 [thread overview]
Message-ID: <52F3A7BD.70805@ti.com> (raw)
In-Reply-To: <52F3A681.9050300@epfl.ch>
On 02/06/2014 09:13 AM, Florian Vaussard wrote:
[...]
>>> +#include "omap34xx.dtsi"
>>> +#include "omap3-overo-tobi-common.dtsi"
>>> +
>>> +/ {
>>> + model = "OMAP35xx Gumstix Overo on Tobi";
>>> + compatible = "gumstix,omap3-overo-tobi", "gumstix,omap3-overo", "ti,omap3";
>> To reduce any future problems, I suggest:
>> compatible = "gumstix,omap3-overo-tobi", "gumstix,omap3-overo",
>> "ti,omap3430", "ti,omap3";
>>
>
> This was also my first thought, but "ti,omap3430" is not documented in
> Documentation/devicetree/bindings/arm/omap/omap.txt. It is said that
> "ti,omap3" defaults to OMAP3430. I do not know if omap35xx would be more
> accurate, as these Overo are using OMAP3503 and OMAP3530.
3430 should have been now documented with commit
89b6eef0d859bad4bcf7ad64560aa2891d6a37a0
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/arm/omap/omap.txt#n64
We have not pulled out 3730 or 3530 separately out in linux as of
today as they are nothing but a packaging difference for larger board
community - there should be no internal differences - the only
functional variation has been am3517 - which got it's own compatible
property.
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: Add support for both OMAP35xx and OMAP36xx Overo/Tobi
Date: Thu, 6 Feb 2014 09:18:21 -0600 [thread overview]
Message-ID: <52F3A7BD.70805@ti.com> (raw)
In-Reply-To: <52F3A681.9050300@epfl.ch>
On 02/06/2014 09:13 AM, Florian Vaussard wrote:
[...]
>>> +#include "omap34xx.dtsi"
>>> +#include "omap3-overo-tobi-common.dtsi"
>>> +
>>> +/ {
>>> + model = "OMAP35xx Gumstix Overo on Tobi";
>>> + compatible = "gumstix,omap3-overo-tobi", "gumstix,omap3-overo", "ti,omap3";
>> To reduce any future problems, I suggest:
>> compatible = "gumstix,omap3-overo-tobi", "gumstix,omap3-overo",
>> "ti,omap3430", "ti,omap3";
>>
>
> This was also my first thought, but "ti,omap3430" is not documented in
> Documentation/devicetree/bindings/arm/omap/omap.txt. It is said that
> "ti,omap3" defaults to OMAP3430. I do not know if omap35xx would be more
> accurate, as these Overo are using OMAP3503 and OMAP3530.
3430 should have been now documented with commit
89b6eef0d859bad4bcf7ad64560aa2891d6a37a0
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/arm/omap/omap.txt#n64
We have not pulled out 3730 or 3530 separately out in linux as of
today as they are nothing but a packaging difference for larger board
community - there should be no internal differences - the only
functional variation has been am3517 - which got it's own compatible
property.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-02-06 15:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 9:10 [PATCH 0/3] ARM: dts: Fixes for Overo/Tobi against 3.14-rc1 Florian Vaussard
2014-02-06 9:10 ` Florian Vaussard
2014-02-06 9:10 ` [PATCH 1/3] ARM: dts: omap3-tobi: Fix boot with OMAP36xx-based Overo Florian Vaussard
2014-02-06 9:10 ` Florian Vaussard
2014-02-06 9:10 ` [PATCH 2/3] ARM: dts: omap3-tobi: Use the correct vendor prefix Florian Vaussard
2014-02-06 9:10 ` Florian Vaussard
2014-02-06 9:10 ` [PATCH 3/3] ARM: dts: Add support for both OMAP35xx and OMAP36xx Overo/Tobi Florian Vaussard
2014-02-06 9:10 ` Florian Vaussard
2014-02-06 14:35 ` Nishanth Menon
2014-02-06 14:35 ` Nishanth Menon
2014-02-06 15:13 ` Florian Vaussard
2014-02-06 15:13 ` Florian Vaussard
2014-02-06 15:18 ` Nishanth Menon [this message]
2014-02-06 15:18 ` Nishanth Menon
2014-02-06 17:09 ` [PATCH 0/3] ARM: dts: Fixes for Overo/Tobi against 3.14-rc1 Kevin Hilman
2014-02-06 17:09 ` Kevin Hilman
2014-02-11 13:07 ` Florian Vaussard
2014-02-11 13:07 ` Florian Vaussard
2014-02-11 16:47 ` Kevin Hilman
2014-02-11 16:47 ` 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=52F3A7BD.70805@ti.com \
--to=nm@ti.com \
--cc=bcousson@baylibre.com \
--cc=florian.vaussard@epfl.ch \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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.