From: Andrew Lunn <andrew@lunn.ch>
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: "Alvin Šipraga" <ALSI@bang-olufsen.dk>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"tobias@waldekranz.com" <tobias@waldekranz.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"vladimir.oltean@nxp.com" <vladimir.oltean@nxp.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>
Subject: Re: [PATCH net-next] net: dsa: realtek: add compatible strings for RTL8367RB-VB
Date: Fri, 15 Apr 2022 16:35:28 +0200 [thread overview]
Message-ID: <YlmCsMk/GekmdewG@lunn.ch> (raw)
In-Reply-To: <CAJq09z5hG7VkhkxdhVTUvA-dMJr6_ajkHYBZ6N2ROFXLz0gijQ@mail.gmail.com>
> Now, about dt-bindings, I don't know what is the best approach. As
> device-tree should not focus on Linux, it is strange to use a
> compatible "rtl8365mb" just because it is the Linux subdriver name and
> that name was just because it was the first device supported.
What you are trying to express is, how do you access the ID
register. There is no obvious One True Compatible string for that. So
just picking one switch name for that is O.K. There is nothing Linux
specific in that, FreeBSD or whatever can use the label as a clue
where to find the ID register.
> + realtek,rtl8365mb:
> + Use with models RTL8363NB, RTL8363NB-VB, RTL8363SC, RTL8363SC-VB,
> + RTL8364NB, RTL8364NB-VB, RTL8365MB, RTL8366SC, RTL8367RB-VB, RTL8367S,
> + RTL8367SB, RTL8370MB, RTL8310SR
> + realtek,rtl8367rb:
> + Use with models RTL8366RB, RTL8366S
So to me, this is fine. But i might add a bit more detail, that the
compatible is used by the driver to find the ID register, and the
driver then uses to ID register to decide how to drive the switch. The
problem i had with the mv88e6xxx binding was until i spelt this out in
the binding, people kept submitting patches adding new compatible
strings, rather than extend the documented list of switches supported
by a compatible.
Andrew
next prev parent reply other threads:[~2022-04-15 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 21:04 [PATCH net-next] net: dsa: realtek: add compatible strings for RTL8367RB-VB Luiz Angelo Daros de Luca
2022-04-12 0:18 ` Andrew Lunn
2022-04-12 4:12 ` Luiz Angelo Daros de Luca
2022-04-12 12:43 ` Andrew Lunn
2022-04-12 13:30 ` Alvin Šipraga
2022-04-13 18:29 ` Luiz Angelo Daros de Luca
2022-04-13 18:40 ` Andrew Lunn
2022-04-14 1:40 ` Alvin Šipraga
2022-04-12 10:50 ` Alvin Šipraga
2022-04-13 18:38 ` Luiz Angelo Daros de Luca
2022-04-14 1:45 ` Alvin Šipraga
2022-04-14 2:32 ` Luiz Angelo Daros de Luca
2022-04-14 11:37 ` Alvin Šipraga
2022-04-14 13:48 ` Andrew Lunn
2022-04-15 7:48 ` Luiz Angelo Daros de Luca
2022-04-15 14:35 ` Andrew Lunn [this message]
2022-04-16 6:27 ` Luiz Angelo Daros de Luca
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=YlmCsMk/GekmdewG@lunn.ch \
--to=andrew@lunn.ch \
--cc=ALSI@bang-olufsen.dk \
--cc=arinc.unal@arinc9.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.com \
--cc=vladimir.oltean@nxp.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).