[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140310140511.GD19781@netboy>
Date: Mon, 10 Mar 2014 15:05:11 +0100
From: Richard Cochran <richardcochran@...il.com>
To: Sørensen, Stefan
<Stefan.Sorensen@...ctralink.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bhutchings@...arflare.com" <bhutchings@...arflare.com>,
"christian.riesch@...cron.at" <christian.riesch@...cron.at>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: Re: [PATCH RFC net-next v1 0/9] ptp: dynamic pin control
On Mon, Mar 10, 2014 at 12:52:57PM +0000, Sørensen, Stefan wrote:
> The implementation is limited to a single function for each pin - the
> dp83640 supports an ext_ts and several periodic outputs on the same pin,
> but I do not see that many real-world uses.
So the main use case is to allow users to configure the auxiliary
functions according to their needs. This series provides this without
relying on DT, ACPI, etc. The sysfs control lets you put this into a
boot script, for example.
In addition, there are also less common use cases for re-configuring
pins at run time. One use would be to switch from a PPS output to a
time stamping input during automated PTP testing.
Thanks,
Richard
--
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