From: Christian Riesch <christian.riesch@omicron.at>
To: "Mugunthan V N" <mugunthanvnm@ti.com>,
"\"Sørensen, Stefan\"" <Stefan.Sorensen@spectralink.com>,
"ben@decadent.org.uk" <ben@decadent.org.uk>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] net:cpsw: Pass unhandled ioctl's on to generic phy ioctl
Date: Wed, 05 Feb 2014 11:49:57 +0100 [thread overview]
Message-ID: <52F21755.90101@omicron.at> (raw)
In-Reply-To: <52F1F3E3.2050906@ti.com>
On 2014-02-05 09:18, Mugunthan V N wrote:
> On Wednesday 05 February 2014 12:58 PM, Sørensen, Stefan wrote:
>> The CPSW only supports timestamping which is only one part of the PTP
>> functionality. Some PHYs (like the dp83630 that we use with the CPSW)
>> also has external event generation and detection.
> CPSW also has External event detection upto 4 events and newer SoCs upto
> 8 events, currently no boards came with this pins pinned out, so it is
> not supported as of now. If we have a board design with this we can
> support external event generation.
But for external event generation it would be useful to adjust the clock
frequency of the PHC. IIRC this is broken on some silicon like the
AM335x, right?
Christian
next prev parent reply other threads:[~2014-02-05 10:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 7:50 [PATCH] net:cpsw: Pass unhandled ioctl's on to generic phy ioctl Stefan Sørensen
2014-02-04 10:50 ` Ben Hutchings
2014-02-04 15:08 ` Sørensen, Stefan
2014-02-04 21:51 ` Ben Hutchings
2014-02-05 7:12 ` Richard Cochran
2014-02-05 10:23 ` Ben Hutchings
2014-02-05 11:06 ` Christian Riesch
2014-02-05 11:26 ` Richard Cochran
2014-02-05 7:28 ` Sørensen, Stefan
2014-02-05 8:18 ` Mugunthan V N
2014-02-05 10:49 ` Christian Riesch [this message]
2014-02-05 14:15 ` Mugunthan V N
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=52F21755.90101@omicron.at \
--to=christian.riesch@omicron.at \
--cc=Stefan.Sorensen@spectralink.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.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).