From: Conor Dooley <conor@kernel.org>
To: Jonas Jelonek <jelonek.jonas@gmail.com>
Cc: "Oleksij Rempel" <o.rempel@pengutronix.de>,
"Kory Maincent" <kory.maincent@bootlin.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Daniel Golle" <daniel@makrotopia.org>,
"Bjørn Mork" <bjorn@mork.no>
Subject: Re: [PATCH net-next v6 1/4] dt-bindings: net: pse-pd: add bindings for Realtek PSE MCU
Date: Fri, 10 Jul 2026 16:10:31 +0100 [thread overview]
Message-ID: <20260710-divinely-sharpie-1d415917c850@spud> (raw)
In-Reply-To: <20260709194125.2784507-2-jelonek.jonas@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
On Thu, Jul 09, 2026 at 07:41:20PM +0000, Jonas Jelonek wrote:
> ---
> .../bindings/net/pse-pd/realtek,pse-mcu.yaml | 176 ++++++++++++++++++
> 1 file changed, 176 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/pse-pd/realtek,pse-mcu.yaml
Typically, we want filenames that match the compatibles used within. In
this case, probably pick the oldest and simplest one?
>
> +properties:
> + compatible:
> + oneOf:
> + # UART
> + - items:
> + - enum:
> + - zyxel,gs1900-10hp-a1-pse
> + - const: realtek,pse-mcu-gen1
IOW, this. Otherwise,
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: changes-requested
Thanks,
Conor.
> +
> + # I2C, SMBus framing
> + - items:
> + - enum:
> + - zyxel,gs1920-24hp-v2-pse
> + - const: realtek,pse-mcu-gen1-smbus
> +
> + # UART
> + - items:
> + - enum:
> + - zyxel,gs1900-10hp-b1-pse
> + - zyxel,xmg1915-10ep-pse
> + - const: realtek,pse-mcu-gen2
> +
> + # I2C, SMBus framing
> + - items:
> + - enum:
> + - zyxel,xs1930-12hp-pse
> + - const: realtek,pse-mcu-gen2-smbus
> +
> + # I2C, raw framing
> + - items:
> + - enum:
> + - linksys,lgs328mpc-v2-pse
> + - const: realtek,pse-mcu-gen2-i2c
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-10 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 19:41 [PATCH net-next v6 0/4] net: pse-pd: add Realtek PSE MCU support Jonas Jelonek
2026-07-09 19:41 ` [PATCH net-next v6 1/4] dt-bindings: net: pse-pd: add bindings for Realtek PSE MCU Jonas Jelonek
2026-07-10 15:10 ` Conor Dooley [this message]
2026-07-09 19:41 ` [PATCH net-next v6 2/4] net: pse-pd: add Realtek PSE MCU core Jonas Jelonek
2026-07-09 19:41 ` [PATCH net-next v6 3/4] net: pse-pd: realtek-pse-mcu: add I2C transport Jonas Jelonek
2026-07-09 19:41 ` [PATCH net-next v6 4/4] net: pse-pd: realtek-pse-mcu: add UART transport Jonas Jelonek
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=20260710-divinely-sharpie-1d415917c850@spud \
--to=conor@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bjorn@mork.no \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jelonek.jonas@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@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