From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: Support basic hotplug for PCI-E
Date: Wed, 21 Nov 2012 13:56:52 -0500 [thread overview]
Message-ID: <20121121185652.GD15800@titan.lakedaemon.net> (raw)
In-Reply-To: <20121121184754.GB12822@obsidianresearch.com>
On Wed, Nov 21, 2012 at 11:47:54AM -0700, Jason Gunthorpe wrote:
> On Wed, Nov 21, 2012 at 01:35:27PM -0500, Jason Cooper wrote:
> > On Wed, Nov 21, 2012 at 11:25:28AM -0700, Jason Gunthorpe wrote:
> > > Unconditionally register the PCI-E bus, even if the link is currently
> > > down.
> >
> > How does this affect clock gating on boards without PCI-E devices? Will
> > the SoC then power this unconditionally?
>
> Hmm, interesting question.. This will definitely hold the clock lock
> on the PCI-E ports even if they are down at boot, and they will surely
> consume more power than if they were switched off.
>
> However, if a board has no possible PCI-E devices, then it shouldn't
> be calling kirkwood_pcie_init, which will let things gate.
Ok, that's the good short-term answer.
> I guess another way to deal with this is to make the stuff in
> kirkwood/pcie.c an actual platform driver and hot attach the entire
> driver rather than using just using pci/rescan, but that is a fairly
> extensive change.. And I worry that powering down the interface in the
> interm will require re-initializing all the registers, which linux
> doesn't have the code to do at all.
The goal is to remove everything from mach-kirkwood/, mach-dove/, etc.
which means pcie will eventually become a real driver under drivers/.
We just aren't there yet.
I'll pull this in as is. Thanks for the patch!
thx,
Jason.
next prev parent reply other threads:[~2012-11-21 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 18:25 [PATCH] ARM: Kirkwood: Support basic hotplug for PCI-E Jason Gunthorpe
2012-11-21 18:35 ` Jason Cooper
2012-11-21 18:47 ` Jason Gunthorpe
2012-11-21 18:56 ` Jason Cooper [this message]
2012-11-21 19:02 ` Andrew Lunn
2012-11-21 19:19 ` Jason Gunthorpe
2013-01-07 16:11 ` Jason Cooper
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=20121121185652.GD15800@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.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.