linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abdelghani Ouchabane <abdelghani@ezono.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: PCIe can not rescan for new PCIe device ( FPGA board )
Date: Fri, 14 Oct 2011 11:40:12 +0200	[thread overview]
Message-ID: <4E98037C.4000403@ezono.com> (raw)
In-Reply-To: <4E96DE8A.6050404@jp.fujitsu.com>

On 13/10/11 14:50, Kenji Kaneshige wrote:
> Thank you for the information. Though I don't have any good news for you,
> I think as follows based on the info.
>
> - There are two hot-plug capable PCIe slots on your machine.
>
> - But, it seems you are using fakephp driver, not pciehp (is that
>   correct?). The fakephp cannot handle hot-plug event such as presence
>   change event on the slot. This is why the bus is not scanned automatically.
>
> - Unfortunately, the bus would not be scanned automatically even if you
>   use pciehp. As I told you in the previous email, current pciehp don't
>   scan the bus automatically only if the slot is hot-plug surprise
>   capable. According to the lspci output, your hotplug controller is not
>   hot-plug surprise capable.
>
> - I don't think pciehp solve invalid register read problem. According to
>   the lspci output, power controller capability isn't present on your
>   hotplug controller. On such environment, pciehp driver does almost the
>   same thing as fakephp does (just scan the bus/remove the pci device data
>   structure) except hot-plug event handling.
>
> But it's worth whole trying pciehp.
> By the way, have you tried acpiphp? It might help you.
>
> Regards,
> Kenji Kaneshige
>

Hallo Kenji,

many thanks for your great supports. The new BIOS from Congatec solves
the problem.

I using both fakephp & pciehp drivers, Can I use both drivers at the
same time?

I am using fakephp because I need "/sys/bus/pci/slots/0000\:02\:00.0/power".

Other thing: my Kernel has "CONFIG_ACPI_PROC_EVENT is not set", does
this explain why the scan is not performed automatically?

[root@localhost ~]# modprobe acpiphp
FATAL: Error inserting acpiphp
(/lib/modules/2.6.40.3-0.119.delos.i686/kernel/drivers/pci/hotplug/acpiphp.ko):
No such device

What is the advantage to use acpiphp ?


Cheers,
Ghani






  reply	other threads:[~2011-10-14  9:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07  7:16 PCIe can not rescan for new PCIe device ( FPGA board ) Abdelghani Ouchabane
2011-10-07 15:37 ` Bjorn Helgaas
2011-10-07 16:22   ` Abdelghani Ouchabane
2011-10-07 16:36     ` Bjorn Helgaas
2011-10-11  1:39       ` Kenji Kaneshige
2011-10-11  8:11         ` Abdelghani Ouchabane
2011-10-12  6:36           ` Kenji Kaneshige
2011-10-12  8:35             ` Abdelghani Ouchabane
2011-10-13 12:50               ` Kenji Kaneshige
2011-10-14  9:40                 ` Abdelghani Ouchabane [this message]
2011-10-24  5:00                   ` Kenji Kaneshige
2011-10-24  9:20                     ` Abdelghani Ouchabane
2011-10-11  8:10       ` Abdelghani Ouchabane
2011-10-11 15:22         ` Bjorn Helgaas
     [not found]           ` <4E954251.5020801@ezono.com>
2011-10-12  8:03             ` Abdelghani Ouchabane
2011-10-12 15:58               ` Bjorn Helgaas
2011-10-14  9:27                 ` Abdelghani Ouchabane

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=4E98037C.4000403@ezono.com \
    --to=abdelghani@ezono.com \
    --cc=bhelgaas@google.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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 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).