From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board
Date: Fri, 30 Jan 2015 12:00:16 +0100 [thread overview]
Message-ID: <54CB6440.1010002@gmail.com> (raw)
In-Reply-To: <20150130113118.5523ed68@armhf>
On 30.01.2015 11:31, Jean-Francois Moine wrote:
> On Fri, 30 Jan 2015 10:44:07 +0100
> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
>> I had a closer look on the Compulab website of the SoM [1] and think
>> that we'll have to convert it to dove-cm-a510.dtsi and the baseboard
>> Gabriel is using (maybe SBC-A510 [2]).
>
> I don't understand why the A510 contained in the cm-a510 should be
> different from the one of the other boards (I just noticed a second
> ethernet and a WiFi device - but, is the Compulab document up to date?).
It is not the SoM that is different, but the baseboard it is attached
to. So, the SoM makes a second layer of dtsi around the SoC but is not
sufficient for a board dts.
Regarding the on-SoM WiFi, that will be available on _any_ cm-a510
equipped to _any_ baseboard, so it can be enabled in the som.dtsi.
The second ethernet comes from a PCIe attached NIC, and as you already
said, we simply don't know (yet) if it is actually wired-up on Gabriel's
baseboard. If it is not wired-up on the baseboard, we definitely want
it disabled in DT, too.
> If it is the same, the dove.dtsi should work (and it seems to work for
> Gabriel).
Of course it does work for Gabriel but we don't want to exclusively
mainline Gabriel's setup. In the best case, we want to provide a
dove-cm-a510.dtsi that can be included in any baseboard somebody is
using.
> The only difference with the cm-a510 is the presence or not of the
> connectors. So, all the Dove devices could be enabled in the DT, and,
> if some room is needed in the board, the .config could be adapted
> removing the useless drivers and have a minimal kernel.
Adapting the .config and removing drivers is actually not an option.
IMHO, introducing DT was meant for a single multi-arch kernel that
can be shipped with common Linux distros. Therefore, DT is the place
you enable/disable available resources. You leave most of the SoC (and
SoM) nodes disabled as long as you cannot tell if there is a
corresponding connector available.
Sebastian
next prev parent reply other threads:[~2015-01-30 11:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YH5bU-0005mG-3L@bombadil.infradead.org>
2015-01-30 9:44 ` [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board Sebastian Hesselbarth
2015-01-30 10:31 ` Jean-Francois Moine
2015-01-30 11:00 ` Sebastian Hesselbarth [this message]
2015-01-30 11:41 ` Jean-Francois Moine
2015-01-30 12:03 ` Sebastian Hesselbarth
2015-01-30 12:39 ` Jean-Francois Moine
2015-01-30 12:50 ` Sebastian Hesselbarth
[not found] ` <54CE354F.5090106@gmail.com>
2015-02-05 22:13 ` Sebastian Hesselbarth
2015-02-06 7:58 ` Jean-Francois Moine
2015-02-06 10:05 ` Sebastian Hesselbarth
2015-02-06 10:50 ` Jean-Francois Moine
2015-02-06 10:52 ` Russell King - ARM Linux
2015-02-06 10:48 ` Russell King - ARM Linux
[not found] ` <54D48711.8060903@gmail.com>
2015-02-06 10:00 ` Sebastian Hesselbarth
2015-01-30 12:44 ` David Goodenough
2015-01-30 13:07 ` Sebastian Hesselbarth
2015-01-30 13:32 ` David Goodenough
2015-01-30 6:06 Jean-Francois Moine
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=54CB6440.1010002@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--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).