[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1DE4295A-1D25-4FAD-8DAB-45BD97E511C9@walle.cc>
Date: Thu, 07 Nov 2019 08:47:25 +0100
From: Michael Walle <michael@...le.cc>
To: Andrew Lunn <andrew@...n.ch>
CC: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
netdev@...r.kernel.org, Rob Herring <robh@...nel.org>,
David Miller <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>,
Simon Horman <simon.horman@...ronome.com>,
Oleksij Rempel <o.rempel@...gutronix.de>
Subject: Re: [PATCH v2 4/6] net: phy: at803x: mention AR8033 as same as AR8031
Am 7. November 2019 03:04:36 MEZ schrieb Andrew Lunn <andrew@...n.ch>:
>On Wed, Nov 06, 2019 at 11:36:15PM +0100, Michael Walle wrote:
>> The AR8033 is the AR8031 without PTP support. All other registers are
>> the same. Unfortunately, they share the same PHY ID. Therefore, we
>> cannot distinguish between the one with PTP support and the one
>without.
>
>Not nice. I suppose there might be a PTP register you can read to
>determine this, but that is not very helpful.
I tried that actually.. There is a PTP enable bit. It's default is 1 (according to the AR8031 datasheet). Now guess what it's value is on the AR8033.. its also 1. Not enough.. I also tried to enable the realtime counter. well that worked too.
And yes. I've double checked the package marking. It definitely was an AR8033. So either I was just lucky, or maybe.. the AR8033 is just a relabled AR8031 ;)
-michael
Powered by blists - more mailing lists