From: Andrew Lunn <andrew@lunn.ch>
To: Jie Luo <luoj@codeaurora.org>
Cc: Michael Walle <michael@walle.cc>,
davem@davemloft.net, hkallweit1@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
netdev@vger.kernel.org, sricharan@codeaurora.org
Subject: Re: [PATCH] net: phy: add qca8081 ethernet phy driver
Date: Wed, 18 Aug 2021 19:09:13 +0200 [thread overview]
Message-ID: <YR0+uXdKoXrFEhpZ@lunn.ch> (raw)
In-Reply-To: <9aa1543b-e1b8-fba2-1b93-c954dd2e3e50@codeaurora.org>
On Wed, Aug 18, 2021 at 09:34:40PM +0800, Jie Luo wrote:
>
> On 8/18/2021 3:41 PM, Michael Walle wrote:
> > > qca8081 supports IEEE1588 feature, the IEEE1588 code may be submitted in
> > > the near future,
> > >
> > > so it may be a good idea to keep it out from at803x code.
> > The AR8031 also supports PTP. Unfortunately, there is no public datasheet
> > for the QCA8081, so I can't have a look if both are similar.
> >
> > See also,
> > https://lore.kernel.org/netdev/20200228180226.22986-1-michael@walle.cc/
> >
> > -michael
>
> Hi Michael,
>
> Thanks for this comment. it is true that AR8031 supports basic PTP features.
>
> please refer to the following link for the outline features of qca801.
>
> https://www.qualcomm.com/products/qca8081
Is the PTP hardware in the qca8081 the same as the ar8031? When you
add PTP support, will it be for both PHYs?
What about the cable diagnostics? The at803x already has this
implemented. Will the same work for the qca8081?
Andrew
next prev parent reply other threads:[~2021-08-18 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 11:34 [PATCH] net: phy: add qca8081 ethernet phy driver Luo Jie
2021-08-16 13:56 ` Andrew Lunn
2021-08-17 13:10 ` Jie Luo
2021-08-17 13:33 ` Andrew Lunn
2021-08-18 13:21 ` Jie Luo
2021-08-17 14:32 ` Russell King (Oracle)
2021-08-18 7:41 ` Michael Walle
2021-08-18 13:34 ` Jie Luo
2021-08-18 17:09 ` Andrew Lunn [this message]
2021-08-19 10:30 ` Jie Luo
2021-08-16 14:01 ` Russell King (Oracle)
2021-08-17 13:16 ` Jie Luo
2021-08-16 15:27 ` Heiner Kallweit
2021-08-17 14:27 ` Jie Luo
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=YR0+uXdKoXrFEhpZ@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luoj@codeaurora.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=sricharan@codeaurora.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