linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jake Magee <jakemagee@gmail.com>
Cc: Dan Wilson <dwilson@fulcrummicro.com>, Linuxppc-dev@lists.ozlabs.org
Subject: Re: Resetting PCI-E devices after linux boot
Date: Thu, 15 Apr 2010 08:25:23 +1000	[thread overview]
Message-ID: <1271283923.13059.150.camel@pasglop> (raw)
In-Reply-To: <t2wa8142e731004140655p230f7094idc29e489ea09e848@mail.gmail.com>

On Wed, 2010-04-14 at 08:55 -0500, Jake Magee wrote:
> On Thu, Mar 25, 2010 at 8:26 PM, Dan Wilson <dwilson@fulcrummicro.com>
> wrote:
>         We are building a PCI-E device for use in an embedded system
>         with an 85xx processor.  One of our customers is adamant that
>         linux PCI-E hot-swap support will not allow us to either bring
>         the device up after linux boot (i.e., the PCI-E device must be
>         present when linux scans for PCI-E devices at startup) or to
>         reset the device once linux is up.  It was our impression that
>         the PCI-E hot-swap support should allow for devices to appear
>         after linux boot, be properly initialized, and then later be
>         able to shut them down and bring them back up again.
>         
>         Has anyone successfully used the PCI-E hot-swap capabilities
>         in the linux kernel in a PPC 85xx environment?  Any known
>         gotchas we need to be aware of?
>         
>         Thanks in advance for your responses,

It should be possible to get that working, but I suspect not without
some code changes. I know the current PCIe hotswap driver has ACPI hooks
that would need to be replaced by appropriate hooks into the powerpc
code to perform the right resource manipulation etc...

We do PCIe hotswap on IBM pSeries, but this is using specific FW
interfaces for which we have a dedicated PCI hotplug driver.

Can the slot power be SW controlled on the Canyonlands PCIe slot ? In
that case I should be able to toy with that myself at some stage (but
not for a couple of weeks).

Cheers,
Ben.

  reply	other threads:[~2010-04-14 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26  1:26 Resetting PCI-E devices after linux boot Dan Wilson
2010-04-14 13:55 ` Jake Magee
2010-04-14 22:25   ` Benjamin Herrenschmidt [this message]
2010-04-15 10:59     ` Stefan Roese

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=1271283923.13059.150.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Linuxppc-dev@lists.ozlabs.org \
    --cc=dwilson@fulcrummicro.com \
    --cc=jakemagee@gmail.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;
as well as URLs for NNTP newsgroup(s).