public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Add option to passively listen for PCIE hotplug events
Date: Tue, 04 Nov 2008 15:44:23 +0000	[thread overview]
Message-ID: <49106DD7.9010307@tuffmail.co.uk> (raw)
In-Reply-To: <20081104151128.GA22544@srcf.ucam.org>

Matthew Garrett wrote:
> On Tue, Nov 04, 2008 at 03:01:07PM +0000, Alan Jenkins wrote:
>
>   
>> Hey... you're making this conditional on whether a power led is reported
>> present, right?  Are you sure the EeePC doesn't report itself as having
>> a power led?
>>     
>
> Doesn't seem to on the one I was testing, but it's possible. Any chance 
> you could instrument it? There's only a few calls to msleep in 
> pcihp_ctrl.c.
>   

And pciehp_hpc.c!

I instrumented all the delays I could find. hpc_check_lnk_status() was
the only one that came up.  1000ms delay per call, and I get 6 such delays.

The code is saying my hardware lacks "Data Layer Link Active Reporting".



    static int hpc_check_lnk_status(struct controller *ctrl)
    {
        u16 lnk_status;
        int retval = 0;

            /*
             * Data Link Layer Link Active Reporting must be capable for
             * hot-plug capable downstream port. But old controller might
             * not implement it. In this case, we wait for 1000 ms.
             */
            if (ctrl->link_active_reporting){
                    /* Wait for Data Link Layer Link Active bit to be set */
                    pcie_wait_link_active(ctrl);
                    /*
                     * We must wait for 100 ms after the Data Link Layer
                     * Link Active bit reads 1b before initiating a
                     * configuration access to the hot added device.
                     */
                    msleep(100);
            } else {
                    msleep(1000);


  reply	other threads:[~2008-11-04 15:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bspwK-420-11@gated-at.bofh.it>
     [not found] ` <bujnh-2fr-5@gated-at.bofh.it>
     [not found]   ` <bujwT-2Ew-5@gated-at.bofh.it>
     [not found]     ` <buml1-6du-3@gated-at.bofh.it>
2008-11-04 11:29       ` Add option to passively listen for PCIE hotplug events Alan Jenkins
2008-11-04 12:47         ` Matthew Garrett
2008-11-04 13:32           ` Matthew Garrett
2008-11-04 14:26             ` Alan Jenkins
2008-11-04 14:33               ` Matthew Garrett
2008-11-04 15:01                 ` Alan Jenkins
2008-11-04 15:11                   ` Matthew Garrett
2008-11-04 15:44                     ` Alan Jenkins [this message]
2008-11-04 15:57                       ` Matthew Garrett
2008-11-04 16:22                         ` Alan Jenkins
2008-11-09 16:08                           ` Alan Jenkins
2008-11-12 23:34                             ` Matthew Garrett
2008-11-14 16:16                             ` Matthew Garrett
2008-11-14 17:07                               ` Alan Jenkins
2008-11-14 17:12                                 ` Matthew Garrett
2008-11-14 17:27                                   ` Alan Jenkins
2008-11-14 17:35                                     ` Matthew Garrett

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=49106DD7.9010307@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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