From: Andrew Lunn <andrew@lunn.ch>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: "Rob Herring" <robh@kernel.org>,
"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Vivien Didelot" <vivien.didelot@gmail.com>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: net: dsa: realtek-smi: convert to YAML schema
Date: Wed, 9 Feb 2022 18:36:14 +0100 [thread overview]
Message-ID: <YgP7jgswRQ+GR4P2@lunn.ch> (raw)
In-Reply-To: <87zgn0gf3k.fsf@bang-olufsen.dk>
> So, in summary:
>
> - one interrupt for the switch
> - the switch is an interrupt-controller
> - ... and is the interrupt-parent for the phy nodes.
This pattern is pretty common for DSA switches, which have internal
PHYs. You can see this in the mv88e6xxx binding for example.
Andrew
next prev parent reply other threads:[~2022-02-09 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 7:26 [PATCH] dt-bindings: net: dsa: realtek-smi: convert to YAML schema Luiz Angelo Daros de Luca
2022-01-02 6:38 ` Linus Walleij
2022-01-04 23:44 ` Luiz Angelo Daros de Luca
2022-01-10 18:09 ` Rob Herring
2022-01-16 0:15 ` Linus Walleij
2022-01-10 18:20 ` Rob Herring
2022-01-29 16:02 ` Luiz Angelo Daros de Luca
2022-01-29 19:35 ` Arınç ÜNAL
2022-01-29 20:52 ` Luiz Angelo Daros de Luca
2022-01-30 17:35 ` Florian Fainelli
2022-01-31 0:49 ` Luiz Angelo Daros de Luca
2022-02-09 8:37 ` Luiz Angelo Daros de Luca
2022-02-09 15:28 ` Rob Herring
2022-02-09 16:49 ` Alvin Šipraga
2022-02-09 17:36 ` Andrew Lunn [this message]
2022-02-09 18:43 ` Luiz Angelo Daros de Luca
2022-02-09 18:55 ` Florian Fainelli
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=YgP7jgswRQ+GR4P2@lunn.ch \
--to=andrew@lunn.ch \
--cc=ALSI@bang-olufsen.dk \
--cc=arinc.unal@arinc9.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vivien.didelot@gmail.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