[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1369859530.1971.29.camel@bwh-desktop.uk.level5networks.com>
Date: Wed, 29 May 2013 21:32:10 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Richard Cochran <richardcochran@...il.com>
CC: "Keller, Jacob E" <jacob.e.keller@...el.com>,
"Vick, Matthew" <matthew.vick@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
"e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
Subject: Re: [PATCH net-next 4/4] igb: enable auxiliary PHC functions for
the i210.
On Wed, 2013-05-29 at 09:24 +0200, Richard Cochran wrote:
> On Tue, May 28, 2013 at 09:12:02PM +0000, Keller, Jacob E wrote:
> >
> > I think ethtool would be good, but what about using sysfs?
>
> The problem I see with ethtool is that configuring GPIOs (and these
> SDPs are really just GPIOs by a different name) is really the job of
> the device tree. But of course, most x86 users of the i210 don't have
> this option.
>
> Also, using ethtool or sysfs is not really attractive for embedded
> designs (let's not forget the poor embedded guys). I think we need to
> have a way to specify the pin functions at (or before) kernel boot
> time. Barring DT and kconfig, using a module parameter is the only
> way to accomplish this.
On x86 the correct place to put this information would presumably be an
ACPI table. And if the BIOS doesn't provide it, there is
CONFIG_ACPI_CUSTOM_DSDT, though that may be a bit of a sledgehammer...
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists