All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Joseph Telaak <joseph@telaak.dev>
Cc: hauke@hauke-m.de, andrew@lunn.ch, olteanv@gmail.com,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, daniel@makrotopia.org,
	p.zabel@pengutronix.de, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/2] net: dsa: mxl-gsw1xx: reset the switch through reset-gpios
Date: Thu, 19 Nov 2026 10:30:05 +0000	[thread overview]
Message-ID: <179508420578.3002552.9484670027487082797.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261115-mxl-gsw1xx-reset-v4-0-4ecd18c922e2@telaak.dev>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sun, 15 Nov 2026 17:33:44 -0500 you wrote:
> The GSW1xx driver never resets the switch, and the MDIO core does not
> handle reset-gpios for non-PHY devices, so the driver works with whatever
> the bootloader configured. On the GL.iNet GL-SFT1200 (Siflower SF19A2890 +
> GSW150), nothing answers at internal MDIO address 0 after the bootloader,
> and each port's address answers with the neighboring port's PHY, so the
> WAN port has no PHY. Describing the PHYs at the addresses they answer at
> is not enough: with them at 1 to 3 and no reset, neither LAN port passes
> traffic. A hardware reset puts the switch back in its power-on state, as
> GL.iNet's own firmware does from Linux.
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/2] dt-bindings: net: dsa: lantiq,gswip: add reset-gpios
    https://git.kernel.org/netdev/net-next/c/98b599217570
  - [net-next,v4,2/2] net: dsa: mxl-gsw1xx: reset the switch through reset-gpios
    https://git.kernel.org/netdev/net-next/c/839a787e9ba9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-19 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15 22:33 [PATCH net-next v4 0/2] net: dsa: mxl-gsw1xx: reset the switch through reset-gpios Joseph Telaak via B4 Relay
2026-11-15 22:33 ` Joseph Telaak
2026-11-15 22:33 ` [PATCH net-next v4 1/2] dt-bindings: net: dsa: lantiq,gswip: add reset-gpios Joseph Telaak via B4 Relay
2026-11-15 22:33   ` Joseph Telaak
2026-11-16 22:34   ` sashiko-bot
2026-11-15 22:33 ` [PATCH net-next v4 2/2] net: dsa: mxl-gsw1xx: reset the switch through reset-gpios Joseph Telaak via B4 Relay
2026-11-15 22:33   ` Joseph Telaak
2026-11-18 12:33   ` netdev-bot+sashiko
2026-11-18 20:16     ` Joseph Telaak
2026-11-18 13:07   ` Daniel Golle
2026-11-19 10:30 ` patchwork-bot+netdevbpf [this message]

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=179508420578.3002552.9484670027487082797.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=joseph@telaak.dev \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=p.zabel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.