public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Théo Lebrun" <theo.lebrun@bootlin.com>
To: "Charles Perry" <charles.perry@microchip.com>, <netdev@vger.kernel.org>
Cc: "Conor Dooley" <conor.dooley@microchip.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>,
	"Nicolas Ferre" <nicolas.ferre@microchip.com>,
	"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v3 1/3] dt-bindings: net: cdns,macb: add a compatible for Microchip pic64hpsc
Date: Tue, 17 Mar 2026 16:31:55 +0100	[thread overview]
Message-ID: <DH55ZAW09CJW.18CMNS7Z3UWOY@bootlin.com> (raw)
In-Reply-To: <20260313140610.3681752-2-charles.perry@microchip.com>

On Fri Mar 13, 2026 at 3:06 PM CET, Charles Perry wrote:
> Add "microchip,pic64hpsc-gem" for "PIC64-HPSC" and
> "microchip,pic64hx-gem" for "PIC64HX", compatible with the former.
>
> The generic compatible "cdns,gem" works but offers limited features.
> Keep it as a fallback.
>
> The GEM IPs within pic64hpsc have their MDIO controllers unconnected
> from any physical pin. Add a check to prevent adding PHYs under the GEM
> node.
>
> Signed-off-by: Charles Perry <charles.perry@microchip.com>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
>  .../devicetree/bindings/net/cdns,macb.yaml    | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)

Reviewed-by: Théo Lebrun <theo.lebrun@bootlin.com>

Thanks,

--
Théo Lebrun, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2026-03-17 15:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 14:06 [PATCH net-next v3 0/3] Initial support for PIC64-HPSC/HX Ethernet endpoint Charles Perry
2026-03-13 14:06 ` [PATCH net-next v3 1/3] dt-bindings: net: cdns,macb: add a compatible for Microchip pic64hpsc Charles Perry
2026-03-17 15:31   ` Théo Lebrun [this message]
2026-03-13 14:06 ` [PATCH net-next v3 2/3] net: macb: add safeguards for jumbo frame larger than 10240 Charles Perry
2026-03-16 17:21   ` Théo Lebrun
2026-03-16 18:26     ` Charles Perry
2026-03-17 12:29       ` Paolo Abeni
2026-03-17 15:32         ` Théo Lebrun
2026-03-13 14:06 ` [PATCH net-next v3 3/3] net: macb: add support for Microchip pic64hpsc ethernet endpoint Charles Perry
2026-03-17 15:32   ` Théo Lebrun
2026-03-16 17:28 ` [PATCH net-next v3 0/3] Initial support for PIC64-HPSC/HX Ethernet endpoint Théo Lebrun
2026-03-16 18:47   ` Charles Perry
2026-03-17 12:31   ` Paolo Abeni
2026-03-17 12:40 ` patchwork-bot+netdevbpf

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=DH55ZAW09CJW.18CMNS7Z3UWOY@bootlin.com \
    --to=theo.lebrun@bootlin.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=charles.perry@microchip.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --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