From: Kevin Hilman <khilman@baylibre.com>
To: Andrew Lunn <andrew@lunn.ch>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, jbrunet@baylibre.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: amlogic: remove ethernet-phy-idAAAA.BBBB compatible strings
Date: Tue, 14 May 2019 17:01:42 -0700 [thread overview]
Message-ID: <7hv9ycd1qx.fsf@baylibre.com> (raw)
In-Reply-To: <20190511195150.GI4889@lunn.ch>
Andrew Lunn <andrew@lunn.ch> writes:
> On Sat, May 11, 2019 at 07:45:34PM +0200, Martin Blumenstingl wrote:
>> The Ethernet PHY documentation
>> (Documentation/devicetree/bindings/net/phy.txt) states that:
>> If the PHY reports an incorrect ID (or none at all) then the
>> "compatible" list may contain an entry with the correct PHY ID in the
>> form: "ethernet-phy-idAAAA.BBBB"
>>
>> An older version of the documentation suggested that the compatible
>> string can be used when the PHY ID is known.
>>
>> Remove the ethernet-phy-id compatible string and add a comment with the
>> PHY ID instead.
>> This is a no-op on boards which are shipped with the PHY that was
>> listed (= all known cases). However, if a board manufacturer decides to
>> ship a different PHY we will now load and use the correct driver because
>> we ask the PHY to identify itself.
>>
>> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Queuing for v5.3,
Thanks,
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-05-15 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 17:45 [PATCH] arm64: dts: amlogic: remove ethernet-phy-idAAAA.BBBB compatible strings Martin Blumenstingl
2019-05-11 19:51 ` Andrew Lunn
2019-05-15 0:01 ` Kevin Hilman [this message]
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=7hv9ycd1qx.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.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).