linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH v3][UPDATE] ARM/PCI: claim bus resources on PCI_PROBE_ONLY set-ups
Date: Thu, 23 Jun 2016 11:30:43 -0500	[thread overview]
Message-ID: <20160623163043.GB17987@localhost> (raw)
In-Reply-To: <1466678182-27672-1-git-send-email-lorenzo.pieralisi@arm.com>

On Thu, Jun 23, 2016 at 11:36:22AM +0100, Lorenzo Pieralisi wrote:
> The PCI bios API does not reassign bus resources on systems
> that require the BARs set-up to be immutable (ie PCI_PROBE_ONLY) since
> that would trigger system failures. Nonetheless, PCI bus resources
> allocated to PCI bridge and devices must be claimed in order to be
> validated and inserted in the kernel resource tree, but the current
> code omits the resources claiming and relies on arch specific kludges
> to prevent probing failure (ie preventing resources enablement on
> PCI_PROBE_ONLY systems).
> 
> Add code to the ARM PCI bios kernel layer that correctly claims bus
> resources upon probe on systems that are required to prevent
> reassignment after bus enumeration, so that the allocated resources
> can be enabled successfully upon PCI device drivers probing, without
> resorting to arch back-ends workarounds.
> 
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Russell King <linux@armlinux.org.uk>
> ---
> Hi Bjorn,
> 
> I put together this patch as requested, I could not test this
> specific path but I do not really see how this patch would
> affect any existing set-up.
> 
> It completes (and should be inserted as patch 2 or 3 for
> bisection reasons) this series:
> 
> https://patchwork.ozlabs.org/patch/632161/
> 
> Please let me know if that's ok.

Yes, this is exactly what I had in mind.  Then all the places that use
PCI_PROBE_ONLY will make sense when we look at them later.  I'll add
this to the series on pci/resource.

Thanks!

>  arch/arm/kernel/bios32.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/kernel/bios32.c b/arch/arm/kernel/bios32.c
> index 488545f..1e05d04 100644
> --- a/arch/arm/kernel/bios32.c
> +++ b/arch/arm/kernel/bios32.c
> @@ -515,7 +515,9 @@ void pci_common_init_dev(struct device *parent, struct hw_pci *hw)
>  	list_for_each_entry(sys, &head, node) {
>  		struct pci_bus *bus = sys->bus;
>  
> -		if (!pci_has_flag(PCI_PROBE_ONLY)) {
> +		if (pci_has_flag(PCI_PROBE_ONLY)) {
> +			pci_bus_claim_resources(bus);
> +		} else {
>  			struct pci_bus *child;
>  
>  			/*
> -- 
> 2.6.4
> 
> --
> 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

      reply	other threads:[~2016-06-23 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 10:36 [PATCH v3][UPDATE] ARM/PCI: claim bus resources on PCI_PROBE_ONLY set-ups Lorenzo Pieralisi
2016-06-23 16:30 ` Bjorn Helgaas [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=20160623163043.GB17987@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lorenzo.pieralisi@arm.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 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).