From: Andrew Lunn <andrew@lunn.ch>
To: Marek Vasut <marex@denx.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: dsa: mv88e6xxx: Add MV88E6352 DT compatible
Date: Wed, 12 Sep 2018 02:46:02 +0200 [thread overview]
Message-ID: <20180912004602.GA14588@lunn.ch> (raw)
In-Reply-To: <30900c22-1717-c907-7129-f2dcb90bbc6c@denx.de>
On Wed, Sep 12, 2018 at 02:04:54AM +0200, Marek Vasut wrote:
> On 09/12/2018 01:32 AM, Andrew Lunn wrote:
> >> compatible = "marvell,mv88e6352", "marvell,mv88e6085";
> >
> > Just "marvell,mv88e6085";
> >
> > Please take a look at all the other DT files using the Marvell
> > chips. You will only ever find "marvell,mv88e6085" or
> > "marvell,mv88e6190", because everything is compatible to one of these
> > two.
>
> Well, until you find a difference between those chips which you cannot
> discern based solely on the ID register content. Then it's better to
> have a compatible to match on which matches the actual chip.
Hi Marek
We have been around this loop before. The problem with putting in a
more specific compatible is that nothing is validating it. So it is
going to be wrong, simple because people cut/paste, and don't
necessary change it. So when we do need to look at it, we cannot look
at it, because it is wrong.
I would only add a more specific compatible if and when we need it, it
is actually used, and we can verify it is correct.
Andrew
next prev parent reply other threads:[~2018-09-12 5:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 22:15 [PATCH] net: dsa: mv88e6xxx: Add MV88E6352 DT compatible Marek Vasut
2018-09-11 23:12 ` Andrew Lunn
2018-09-11 23:17 ` Marek Vasut
2018-09-11 23:32 ` Andrew Lunn
2018-09-11 23:52 ` Brandon Streiff
2018-09-12 0:04 ` Marek Vasut
2018-09-12 0:46 ` Andrew Lunn [this message]
2018-09-12 8:38 ` Marek Vasut
2018-09-12 12:47 ` Andrew Lunn
2018-09-12 13:10 ` Marek Vasut
2018-09-12 13:32 ` Andrew Lunn
2018-09-12 13:35 ` Marek Vasut
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=20180912004602.GA14588@lunn.ch \
--to=andrew@lunn.ch \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).