From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
aaro.koskinen@nokia.com, olof@lixom.net
Subject: Re: [PATCH net 2/2] DT: phy.txt: Clarify expected compatible values
Date: Wed, 27 Jan 2016 02:57:55 +0100 [thread overview]
Message-ID: <20160127015755.GB4815@lunn.ch> (raw)
In-Reply-To: <56A81C7B.8050201@gmail.com>
> Well, we do now, since that is one of the results used by
> of_mdiobus_child_is_phy(),
It uses it, but do not rely on it, since for backwards compatibility,
we cannot assume it is there.
You can never change an optional parameter to a mandatory parameter in
DT. To do so breaks backwards compatibility.
> What I would prefer seeing though is not removing nodes that have at
> least two compatible strings, including one that is
> "ethernet-phy-ieee802.3-c22", but those which have only one, like the
> marvell ones that you patch, should have either an additional
> "ethernet-phy-ieee802.3-c22", or none.
So you are saying, if there is an "ethernet-phy-ieee802.3-c22" or an
"ethernet-phy-ieee802.3-45" you can also have any other random junk,
which we are going to ignore, since we have no way to verify, hence we
have to assume it is broken, yet we need to be backwards compatible
with it.
Did you notice:
+ { .compatible = "marvell,88e1310", },
+ { .compatible = "marvell,88E1510", },
No consistency with the 'e'. We would just be encouraging people to
add more inconsistent stuff.
Andrew
next prev parent reply other threads:[~2016-01-27 1:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 0:11 [PATCH net 0/2] Part 2 of v4.5-rc1 phylib regression Andrew Lunn
2016-01-27 0:11 ` [PATCH net 1/2] of: of_mdio: Add a whitelist of PHY compatibilities Andrew Lunn
2016-01-27 11:17 ` Aaro Koskinen
2016-01-27 13:51 ` Sergei Shtylyov
2016-01-27 14:03 ` Andrew Lunn
2016-01-27 0:11 ` [PATCH net 2/2] DT: phy.txt: Clarify expected compatible values Andrew Lunn
2016-01-27 0:33 ` Florian Fainelli
2016-01-27 1:06 ` Andrew Lunn
2016-01-27 1:25 ` Florian Fainelli
2016-01-27 1:57 ` Andrew Lunn [this message]
2016-01-27 16:31 ` Florian Fainelli
2016-01-27 16:41 ` Olof Johansson
2016-01-27 17:11 ` Andrew Lunn
2016-01-27 17:32 ` Olof Johansson
2016-01-27 17:36 ` Andrew Lunn
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=20160127015755.GB4815@lunn.ch \
--to=andrew@lunn.ch \
--cc=aaro.koskinen@nokia.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
/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).