From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Roger Quadros <rogerq@ti.com>,
Benoit Cousson <bcousson@baylibre.com>,
Tony Lindgren <tony@atomide.com>,
Enric Balletbo i Serra <eballetbo@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/3] ARM: dts: omap3-igep0020: Add HS USB Host support
Date: Mon, 7 Oct 2013 12:22:03 +0200 [thread overview]
Message-ID: <CAAwP0s0XHN+ynMH2Mrn4oNuDo1js86wY2vxkZ=+MG_2=Sgrt9Q@mail.gmail.com> (raw)
In-Reply-To: <52527B21.5040602@collabora.co.uk>
On Mon, Oct 7, 2013 at 11:13 AM, Javier Martinez Canillas
<javier.martinez@collabora.co.uk> wrote:
> On 10/07/2013 11:06 AM, Roger Quadros wrote:
>>>
>>> Well that's a very good question indeed.
>>>
>>> The thing is that the IGEP0030 is a Computer-on-Module [1] that is used in
>>> conjunction with expansion boards and some of them have USB HOST support such as
>>> IGEP Paris [2] and IGEP Berlin [3].
>>>
>>> Support for this expansion boards is still not in mainline but there are plans
>>> to add them using Device Tree overlays [4] once/if this land on mainline.
>>>
>>
>> Why would your boards need Device Tree overlays? From the looks of it, the configuration
>> of SOM + base board don't seem to change at runtime.
>>
>
> Indeed, a static configuration (DTS) would be enough now that I think about it.
>
Hi Roger,
Now that I had coffee I remember why I think that even when Device
Tree overlays are not strictly required for a SOM + base board it
could be handy to use. If we use a static configuration (DTB) then the
same firmware can't be used by any IGEP COM Module user. She would
have to choose a DTB to pass to the kernel on boot.
While using DT overlays the same firmware that provides a minimal DTB
can be used regardless of the base board used (as long as there are
all the needed fragment/overlays hooks in the DTS).
After all the SOM has a NAND flash memory and a uSD/MMC slot so a
minimal DTB is needed to boot and the support for all the peripherals
present on the base board can be added by triggering a device tree
overlay load from user-space.
Or maybe I'm misunderstanding the use case for DT overlays since I had
just read about it but I don't have practical experience with it.
Thanks a lot and best regards,
Javier
next prev parent reply other threads:[~2013-10-07 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1380931479-16142-1-git-send-email-javier.martinez@collabora.co.uk>
[not found] ` <1380931479-16142-3-git-send-email-javier.martinez@collabora.co.uk>
[not found] ` <525271D5.9070009@ti.com>
[not found] ` <525275C8.2050208@collabora.co.uk>
[not found] ` <525275C8.2050208-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2013-10-07 9:06 ` [PATCH 2/3] ARM: dts: omap3-igep0020: Add HS USB Host support Roger Quadros
2013-10-07 9:13 ` Javier Martinez Canillas
2013-10-07 10:22 ` Javier Martinez Canillas [this message]
2013-10-07 10:42 ` Roger Quadros
2013-10-07 11:53 ` Javier Martinez Canillas
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='CAAwP0s0XHN+ynMH2Mrn4oNuDo1js86wY2vxkZ=+MG_2=Sgrt9Q@mail.gmail.com' \
--to=martinez.javier@gmail.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@gmail.com \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@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 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).