devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	netdev@vger.kernel.org, Rob Herring <robh@kernel.org>,
	David Miller <davem@davemloft.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Simon Horman <simon.horman@netronome.com>,
	Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH v2 4/6] net: phy: at803x: mention AR8033 as same as AR8031
Date: Thu, 07 Nov 2019 15:28:19 +0100	[thread overview]
Message-ID: <89dcabd5a1b38e8106d70173922c391b@walle.cc> (raw)
In-Reply-To: <20191107125547.GB22978@lunn.ch>

Hi Andrew,


Am 2019-11-07 13:55, schrieb Andrew Lunn:
>> 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 ;)
> 
> O.K, thanks for trying. We really only need to solve this mystery if
> anybody actually tries to make use of PTP.

That might be the next thing on my list; but depends if there is an 
usable interrupt for the PHY on my board..

-michael

  reply	other threads:[~2019-11-07 14:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 22:36 [PATCH v2 0/6] net: phy: at803x device tree binding Michael Walle
2019-11-06 22:36 ` [PATCH v2 1/6] net: phy: at803x: fix Kconfig description Michael Walle
2019-11-07  1:50   ` Andrew Lunn
2019-11-06 22:36 ` [PATCH v2 2/6] dt-bindings: net: phy: Add support for AT803X Michael Walle
2019-11-07  1:51   ` Andrew Lunn
2019-11-06 22:36 ` [PATCH v2 3/6] net: phy: at803x: add device tree binding Michael Walle
2019-11-06 22:36 ` [PATCH v2 4/6] net: phy: at803x: mention AR8033 as same as AR8031 Michael Walle
2019-11-07  2:04   ` Andrew Lunn
2019-11-07  7:47     ` Michael Walle
2019-11-07 12:55       ` Andrew Lunn
2019-11-07 14:28         ` Michael Walle [this message]
2019-11-06 22:36 ` [PATCH v2 5/6] net: phy: at803x: fix the PHY names Michael Walle
2019-11-07  2:05   ` Andrew Lunn
2019-11-06 22:36 ` [PATCH v2 6/6] net: phy: at803x: remove config_init for AR9331 Michael Walle
2019-11-07  2:05   ` Andrew Lunn
2019-11-07  5:42 ` [PATCH v2 0/6] net: phy: at803x device tree binding David Miller

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=89dcabd5a1b38e8106d70173922c391b@walle.cc \
    --to=michael@walle.cc \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=simon.horman@netronome.com \
    /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).