* Re: Supporting two SMSC9221 interfaces on GPMC in a dts
[not found] ` <CAK8F28=sANBtwDdg45MuVmrE89SBYtzBsZcPZoXo=AhOv0wpOg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2015-01-29 16:20 ` Tony Lindgren
[not found] ` <20150129162020.GA16250-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
0 siblings, 1 reply; 2+ messages in thread
From: Tony Lindgren @ 2015-01-29 16:20 UTC (permalink / raw)
To: Ash Charles
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Florian Vaussard, devicetree-u79uwXL29TY76Z2rM5mHXA
Hi,
Adding devicetree list to Cc as well if somebody has a good solution.
* Ash Charles <ashcharles-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> [150128 18:54]:
> Hi,
>
> The Gumstix Tobi-Duo board has two SMSC9221 NICs attached to the GPMC
> interface of an OMAP3. I'm trying to figure out how best to include
> both interfaces in the device tree file.
> With just one interface, I can #include "omap-gpmc-smsc9221.dtsi", add
> the extra board specific settings in to "ethernet@gpmc" in the board
> file as well as any settings needed for the gpmc.
>
> For two interfaces though, I can setup the gpmc details, configure one
> "ethernet@gpmc" node as before but then, need to manually create (i.e.
> copy the meat from the "omap-gpmc-smsc9221.dtsi") a second node.
Yeah I think this is how we did it for omap3-sbc-*.dts*.
> This works but seems, well, verbose. Is there a way to setup multiple
> interfaces without having to duplicate the omap-gpmc-smsc9221.dtsi
> content?
Hmm I wonder if the "[PATCH] dtc: parser: Add label while overriding
nodes" would help with this too?
I agree it would be nice to be able to have device specific .dtsi
file that can be included multiple times for the most common devices.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Supporting two SMSC9221 interfaces on GPMC in a dts
[not found] ` <20150129162020.GA16250-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
@ 2015-01-29 22:23 ` Ash Charles
0 siblings, 0 replies; 2+ messages in thread
From: Ash Charles @ 2015-01-29 22:23 UTC (permalink / raw)
To: Tony Lindgren
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Florian Vaussard, devicetree-u79uwXL29TY76Z2rM5mHXA
On Thu, Jan 29, 2015 at 8:20 AM, Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> wrote:
> Yeah I think this is how we did it for omap3-sbc-*.dts*.
>
>> This works but seems, well, verbose. Is there a way to setup multiple
>> interfaces without having to duplicate the omap-gpmc-smsc9221.dtsi
>> content?
>
> Hmm I wonder if the "[PATCH] dtc: parser: Add label while overriding
> nodes" would help with this too?
>
> I agree it would be nice to be able to have device specific .dtsi
> file that can be included multiple times for the most common devices.
Thanks Tony.
For now, I'll follow the lead of omap3-sbc-*.dts* for now in lieu of
another technique suggestion. The "[PATCH] dtc: parser: Add label
while overriding nodes" patch definitely looks promising so I'll watch
for that landing in hopes of testing it for this case.
--Ash
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-01-29 22:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAK8F28=sANBtwDdg45MuVmrE89SBYtzBsZcPZoXo=AhOv0wpOg@mail.gmail.com>
[not found] ` <CAK8F28=sANBtwDdg45MuVmrE89SBYtzBsZcPZoXo=AhOv0wpOg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-29 16:20 ` Supporting two SMSC9221 interfaces on GPMC in a dts Tony Lindgren
[not found] ` <20150129162020.GA16250-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-01-29 22:23 ` Ash Charles
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).