From: Yijing Wang <wangyijing@huawei.com>
To: Frank Rizzo <thefrankrizzo@hotmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Rescan PCIE bus to find recently powered on device.
Date: Fri, 19 Apr 2013 11:27:57 +0800 [thread overview]
Message-ID: <5170B9BD.6040408@huawei.com> (raw)
In-Reply-To: <SNT136-W425B9A4DBEA719E570080DB2C80@phx.gbl>
On 2013/4/19 10:59, Frank Rizzo wrote:
> Hey list.
>
> I'm working on a driver for a device that's external from the PC. It's connected to the PC via a weird cable that connects to a PCIE card inside the case that appears to be nothing other than glue logic to allow the signals from the cable to be tossed onto the bus.
>
> When the external device is powered off during boot, nothing is found. hwinfo doesn't find it, lspci doesn't find it, etc. If you power on the device BEFORE booting, everything is found, and it works fine. And lastly, if you power it on AFTER Linux has booted, you still can't find it. I've tried echoing "1" to rescan, and everything else that I could find via Google search.
>
> So, what are my options here? I'm not allergic to adding code to the driver to scan for the device periodically, if I knew HOW to find it. And, once found, how do I get it registered?
>
When your device power off during boot, system maybe will not reserve resource like bus res for your device. So when you power on your device after system boot,
system cannot scan your device by rescan interface, I guess.
>
> Thanks! --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2013-04-19 3:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 2:59 Rescan PCIE bus to find recently powered on device Frank Rizzo
2013-04-19 3:27 ` Yijing Wang [this message]
2013-04-19 15:49 ` Bjorn Helgaas
[not found] ` <BLU0-SMTP305A7D1308063E03F4C5CE9B2C90@phx.gbl>
[not found] ` <5171F610.80001@huawei.com>
2013-04-20 2:22 ` Frank Rizzo
2013-04-20 2:59 ` Yijing Wang
2013-04-20 3:26 ` Frank Rizzo
2013-04-20 5:47 ` Yijing Wang
2013-04-20 16:10 ` Jiang Liu
2013-04-20 16:17 ` Jiang Liu
2013-04-20 20:52 ` Frank Rizzo
2013-04-21 2:21 ` Jiang Liu
2013-04-22 17:21 ` Bjorn Helgaas
2013-05-12 22:13 ` Frank Rizzo
2013-05-13 5:35 ` Frank Rizzo
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=5170B9BD.6040408@huawei.com \
--to=wangyijing@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=thefrankrizzo@hotmail.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 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.