lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 30 Nov 2023 15:11:04 +0100
From: Andrew Lunn <>
To: Andrew Halaney <>
Cc: Heiner Kallweit <>,
	Russell King <>,
	"David S. Miller" <>,
	Eric Dumazet <>,
	Jakub Kicinski <>, Paolo Abeni <>,,,
	Sagar Cheluvegowda <>
Subject: Re: [PATCH net-next v2] net: phy: mdio_device: Reset device only
 when necessary

On Mon, Nov 27, 2023 at 03:41:10PM -0600, Andrew Halaney wrote:
> Currently the phy reset sequence is as shown below for a
> devicetree described mdio phy on boot:
> 1. Assert the phy_device's reset as part of registering
> 2. Deassert the phy_device's reset as part of registering
> 3. Deassert the phy_device's reset as part of phy_probe
> 4. Deassert the phy_device's reset as part of phy_hw_init
> The extra two deasserts include waiting the deassert delay afterwards,
> which is adding unnecessary delay.
> This applies to both possible types of resets (reset controller
> reference and a reset gpio) that can be used.
> Here's some snipped tracing output using the following command line
> params "trace_event=gpio:* trace_options=stacktrace" illustrating
> the reset handling and where its coming from:

> Reported-by: Sagar Cheluvegowda <>
> Signed-off-by: Andrew Halaney <>

Reviewed-by: Andrew Lunn <>


Powered by blists - more mailing lists