All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux@armlinux.org.uk, alexander.stein@ew.tq-group.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: phy: dp83867: restore LED configuration after a soft reset
Date: Tue, 15 Sep 2026 00:40:04 +0000	[thread overview]
Message-ID: <178943280413.1286519.754745669721308122.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260908235740.120112-1-donggeunyoo.kernel@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  9 Sep 2026 08:57:40 +0900 you wrote:
> The LED configuration lives in LEDCR1 (the per-LED function nibble) and
> LEDCR2 (per-LED driver enable/value and polarity). The driver programs it
> through the LED class callbacks -- dp83867_led_brightness_set(),
> dp83867_led_hw_control_set() and dp83867_led_polarity_set() -- either once
> from device tree at probe, or at runtime from sysfs and the netdev trigger.
> 
> dp83867_phy_reset(), the .soft_reset callback, issues a global software
> reset (CTRL SW_RESET), which the datasheet defines as resetting all
> registers, including the extended registers, to their defaults.
> phy_init_hw() runs .soft_reset before .config_init on every attach and
> resume -- phy_attach_direct(), mdio_bus_phy_resume() and MAC drivers -- so
> the LED configuration is wiped from the first attach onward and never
> restored. A device-tree polarity is lost, a manually driven LED goes dark,
> and an LED offloaded to the netdev trigger whose link stays down after a
> resume keeps the reset-default function until the next link event.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: phy: dp83867: restore LED configuration after a soft reset
    https://git.kernel.org/netdev/net-next/c/043777e94880

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



      reply	other threads:[~2026-09-15  0:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 23:57 [PATCH net v2] net: phy: dp83867: restore LED configuration after a soft reset Donggeun Yoo
2026-09-15  0:40 ` 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=178943280413.1286519.754745669721308122.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donggeunyoo.kernel@gmail.com \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.