From: Jimmie Mayfield <mayfield@sackheads.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Trying to reset a PCIe device and scratching my head...
Date: Tue, 28 Sep 2010 15:13:08 -0400 [thread overview]
Message-ID: <20100928191307.GA54440@sackheads.org> (raw)
In-Reply-To: <20100928090655.158d1675@jbarnes-desktop>
On Tue, Sep 28, 2010 at 09:06:55AM -0700, Jesse Barnes wrote:
> Right, if your system supports this, it may be the easiest way to go.
I was under the impression that PCIe requires support for at least
fundamental reset and maybe hot reset (secondary bus reset) though I'd
have to go back to the spec to verify the latter. Are you saying that
not all PCIe chipsets support this? Sorry if this seems like a dumb
question...I'm by no means a PCIe guru.
> But devices often have proprietary ways of resetting themselves too;
> maybe you could change your device to reset if a specific bit in config
> or MMIO space was flipped. You'd likely need some sort of delay before
> accessing the device again, but it should be bounded and fairly fixed,
> so probably not a big deal for the driver to handle.
Indeed, the device does support a proprietary reset via MMIO but
that reset only affects those components that lie behind the card's PCIe
interface. So it's nearly a full device reset but not quite. The FPGA
containing the PCIe interface does not get reloaded. Unfortunately, that
behavior is likely set in stone.
Jimmie
prev parent reply other threads:[~2010-09-28 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 2:05 Trying to reset a PCIe device and scratching my head Jimmie Mayfield
2010-09-28 7:28 ` Clemens Ladisch
2010-09-28 16:06 ` Jesse Barnes
2010-09-28 19:13 ` Jimmie Mayfield [this message]
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=20100928191307.GA54440@sackheads.org \
--to=mayfield@sackheads.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.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.