From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: "Török Edvin" <edwintorok@gmail.com>,
zambrano@broadcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, power@bughost.org
Subject: Re: [PATCH] b44: power down PHY when interface down
Date: Sun, 1 Jul 2007 00:03:01 +0200 [thread overview]
Message-ID: <20070630220301.GD2553@xi.wantstofly.org> (raw)
In-Reply-To: <200706302353.25426.mb@bu3sch.de>
On Sat, Jun 30, 2007 at 11:53:25PM +0200, Michael Buesch wrote:
> > When the interface is down (or driver removed), the BroadCom 44xx card remains
> > powered on, and both its MAC and PHY is using up power.
> > This patch makes the driver issue a MAC_CTRL_PHY_PDOWN when the interface
> > is halted, and does a partial chip reset turns off the activity LEDs too.
> >
> > Applies to 2.6.22-rc6, or current git head.
> >
> > Tested on a Broadcom BCM4401-B0 card, it saves ~0.5W (measured using powertop).
>
> Hm, I was going to measure the real power advantage with a
> PCI-extender card. But my B44B0 card doesn't seem to work in
> that extender card. It works perfectly fine sticked directly into
> the motherboard, though, and other cards like a BCM4318 work in
> the extender, too.
> Not sure what this is.
> The extender has an application note about nonworking cards in the
> extender and a too big resistor on the board IDSEL pin being the
> cause of this.
Does the card show up in lspci at all? IDSEL drive strength
issues should only affect config space accesses.
Does the extender board have a PCI-PCI bridge on it? (If not,
there's not really any reason to resistively couple the IDSEL
line to the host, since the host should take care of that.)
> Maybe I can try with another machine tomorrow.
That would only make a difference if there is no PCI-PCI bridge on
the extender board.
If the extender resistively couples the host's IDSEL line, you might
see different results on a different host bridge, since different
host bridges can use different numbers of IDSEL stepping cycles.
next prev parent reply other threads:[~2007-06-30 22:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 11:47 Török Edvin
2007-06-30 12:05 ` Matthew Garrett
2007-06-30 14:44 ` Arjan van de Ven
2007-06-30 15:19 ` Matthew Garrett
2007-06-30 15:25 ` Lennert Buytenhek
2007-07-01 13:02 ` Török Edvin
2007-06-30 16:42 ` PM policy, hotplug, power saving (was Re: [PATCH] b44: power down PHY when interface down) Jeff Garzik
2007-06-30 18:10 ` Stephen Hemminger
2007-06-30 18:31 ` PM policy, hotplug, power saving and WoL Henrique de Moraes Holschuh
2007-07-01 4:51 ` PM policy, hotplug, power saving (was Re: [PATCH] b44: power down PHY when interface down) Kyle Moffett
2007-06-30 21:53 ` [PATCH] b44: power down PHY when interface down Michael Buesch
2007-06-30 22:03 ` Lennert Buytenhek [this message]
2007-06-30 22:24 ` Michael Buesch
2007-06-30 23:17 ` Lennert Buytenhek
2007-07-01 10:23 ` Michael Buesch
2007-07-01 15:00 ` Lennert Buytenhek
2007-07-01 15:29 ` Michael Buesch
2007-07-01 20:20 ` Michael Buesch
[not found] ` <20070630081302.66b1d984@oldman>
2007-07-01 12:49 ` Török Edvin
2007-07-01 12:55 ` Michael Buesch
2007-07-01 13:25 Török Edvin
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=20070630220301.GD2553@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=edwintorok@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=power@bughost.org \
--cc=zambrano@broadcom.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®