mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
	"Russell King (Oracle)" <linux@armlinux.org.uk>,
	Joakim Zhang <qiangqing.zhang@nxp.com>,
	Philippe Schenker <philippe.schenker@toradex.com>,
	netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] net: fec: reset phy on resume after power-up
Date: Wed, 15 Dec 2021 20:48:55 +0100	[thread overview]
Message-ID: <20211215194855.GA114534@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <YbpDKH6CaHzm119W@lunn.ch>

On Wed, Dec 15, 2021 at 08:34:00PM +0100, Andrew Lunn wrote:
> > The reason is that the power consumption in reset is higher in reset
> > compared to the normal PHY software power down.
> 
> Does the datasheet have numbers for in lower power mode and held in
> reset? We only have an issue if held in reset when in low power mode
> consumes more power than simply in low power mode.

The numbers for KSZ9131, Table 6-3: Power Consumption from datasheet [0]

61.2mW in reset, 24.4mW in software power down (3.3VDD)
40.9mW in reset, 12.5mW in software power down (2.5VDD)

Francesco

[0] https://ww1.microchip.com/downloads/en/DeviceDoc/00002841B.pdf


  reply	other threads:[~2021-12-15 19:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 12:16 [PATCH net-next 0/3] Add Possiblity to Reset PHY After Power-up Philippe Schenker
2021-12-14 12:16 ` [PATCH net-next 1/3] net: phy: add phy_reset_after_power_on() function Philippe Schenker
2021-12-14 12:16 ` [PATCH net-next 2/3] net: phy: micrel: add reset-after-power-on flag to ksz9x31 phys Philippe Schenker
2021-12-14 12:16 ` [PATCH net-next 3/3] net: fec: reset phy on resume after power-up Philippe Schenker
2021-12-14 18:54   ` Andrew Lunn
2021-12-14 19:09     ` Russell King (Oracle)
2021-12-14 22:35     ` Francesco Dolcini
2021-12-15  9:36       ` Andrew Lunn
2021-12-15 10:29         ` Russell King (Oracle)
2021-12-15 11:01         ` Francesco Dolcini
2021-12-15 11:10           ` Francesco Dolcini
2021-12-15 19:34           ` Andrew Lunn
2021-12-15 19:48             ` Francesco Dolcini [this message]
2021-12-16  4:52           ` Joakim Zhang
2021-12-16  7:52             ` Francesco Dolcini
2021-12-16 10:24               ` Andrew Lunn
2021-12-16 11:24                 ` Francesco Dolcini
2021-12-16 11:28                   ` Andrew Lunn
2021-12-16 11:31                     ` Francesco Dolcini
2021-12-16 11:32                       ` Andrew Lunn
2021-12-15 10:25       ` Joakim Zhang
2021-12-14 12:23 ` [PATCH net-next 0/3] Add Possiblity to Reset PHY After Power-up Francesco Dolcini

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=20211215194855.GA114534@francesco-nb.int.toradex.com \
    --to=francesco.dolcini@toradex.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=festevam@gmail.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=philippe.schenker@toradex.com \
    --cc=qiangqing.zhang@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®