From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 2/4] PCI: Factor out pci_bus_wait_crs()
Date: Wed, 23 Aug 2017 00:40:45 -0400 [thread overview]
Message-ID: <b9cbd3d8-dec5-65db-efec-b84f1e96985d@codeaurora.org> (raw)
In-Reply-To: <eca38319-9e78-1a9c-b275-43944fd0a63d@codeaurora.org>
On 8/21/2017 3:37 PM, Sinan Kaya wrote:
> bool pci_bus_crs_pending(struct pci_dev *dev, u32 l)
> {
> if !pci_bus_crs_vis_supported(dev->parent)
> return false;
Apparently, I can't do this. By the time, we come to here from vendor id read
function, the topology has not been set up yet.
I'm getting an exception:
[ 6.067392] [<ffff00000846c878>] pci_bus_crs_visibility_pending+0x4/0x7c
[ 6.074085] [<ffff00000846cccc>] pci_scan_single_device+0x40/0xb4
[ 6.080170] [<ffff00000846cd90>] pci_scan_slot+0x50/0xe8
[ 6.085474] [<ffff00000846dc14>] pci_scan_child_bus+0x30/0x108
[ 6.091300] [<ffff0000084bab94>] acpi_pci_root_create+0x184/0x1f0
[ 6.097388] [<ffff000008091dc8>] pci_acpi_scan_root+0x188/0x1d4
[ 6.103298] [<ffff0000084ba7a8>] acpi_pci_root_add+0x38c/0x44c
[ 6.109125] [<ffff0000084b4d94>] acpi_bus_attach+0xe0/0x1ac
[ 6.114689] [<ffff0000084b4e08>] acpi_bus_attach+0x154/0x1ac
[ 6.120340] [<ffff0000084b4e08>] acpi_bus_attach+0x154/0x1ac
[ 6.125991] [<ffff0000084b6608>] acpi_bus_scan+0x60/0x70
[ 6.131297] [<ffff0000091c87f8>] acpi_scan_init+0xd8/0x228
[ 6.136774] [<ffff0000091c84e0>] acpi_init+0x2d4/0x328
[ 6.141905] [<ffff0000091a0c88>] do_one_initcall+0x80/0x108
[ 6.147469] [<ffff0000091a0e98>] kernel_init_freeable+0x188/0x228
[ 6.153556] [<ffff000008c9bcbc>] kernel_init+0x10/0xfc
[ 6.158687] [<ffff000008082ec0>] ret_from_fork+0x10/0x50
>
> return (l & 0xFFFF) == 0x0001;
> }
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-08-23 4:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 21:31 [PATCH v11 0/4] PCI: Use CRS Software Visibility to wait for device to become ready Bjorn Helgaas
2017-08-18 21:32 ` [PATCH v11 1/4] PCI: Don't ignore valid response before CRS timeout Bjorn Helgaas
2017-08-21 14:02 ` Sinan Kaya
2017-08-21 17:44 ` Bjorn Helgaas
2017-08-18 21:32 ` [PATCH v11 2/4] PCI: Factor out pci_bus_wait_crs() Bjorn Helgaas
2017-08-21 13:53 ` Sinan Kaya
2017-08-21 19:18 ` Bjorn Helgaas
2017-08-21 19:37 ` Sinan Kaya
2017-08-21 20:23 ` Bjorn Helgaas
2017-08-21 20:32 ` Sinan Kaya
2017-08-21 21:09 ` Bjorn Helgaas
2017-08-23 4:40 ` Sinan Kaya [this message]
2017-08-18 21:32 ` [PATCH v11 3/4] PCI: Handle CRS ("device not ready") returned by device after FLR Bjorn Helgaas
2017-08-18 21:32 ` [PATCH v11 4/4] PCI: Warn periodically while waiting for device to become ready Bjorn Helgaas
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=b9cbd3d8-dec5-65db-efec-b84f1e96985d@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).