All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Phil Edworthy <phil.edworthy@renesas.com>,
	Pratyush Anand <pratyush.anand@gmail.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	Gabriele Paoloni <gabriele.paoloni@huawei.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Zhou Wang <wangzhou1@hisilicon.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Sinan Kaya <okaya@codeaurora.org>
Subject: Re: [RFC] ARM/ARM64 PCI_PROBE_ONLY platforms
Date: Thu, 28 Jan 2016 17:27:01 +0000	[thread overview]
Message-ID: <20160128172701.GA28468@red-moon> (raw)
In-Reply-To: <HK2PR0601MB1393A8E38392D17EC2DD7900F5C40@HK2PR0601MB1393.apcprd06.prod.outlook.com>

[+ Pratyush, Jingoo, Gabriele]

any comment on this for the designware driver ?

Thanks,
Lorenzo

On Fri, Jan 22, 2016 at 04:28:39PM +0000, Phil Edworthy wrote:
> Hi Lorenzo,
> 
> On 20 January 2016 18:10, Lorenzo Pieralisi wrote:
> > On Wed, Jan 20, 2016 at 11:13:04AM -0500, Sinan Kaya wrote:
> > > On 1/20/2016 11:04 AM, Lorenzo Pieralisi wrote:
> > > > Hi,
> > > >
> > > > I noticed that:
> > > >
> > > > 79953dd22c1d ("PCI: rcar: Remove dependency on ARM-specific struct
> > hw_pci")
> > > > cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > > >
> > > > added code in the respective host controller drivers to size bridges
> > > > and assign resources only if the PCI_PROBE_ONLY flag is clear, which makes
> > > > me wonder if there exists PCI_PROBE_ONLY set-ups for the respective
> > > > host controllers:
> > > >
> <snip>
>  
> > Resources claiming and assignment should be managed in arch code,
> > not in host controllers specific code, and that's the reason I
> > complained in this RFC about the scattering of PCI_PROBE_ONLY flag
> > checks in host drivers, it is becoming unmanageable (if useful
> > at all on designware and rcar, I would like to know if there are
> > PCI_PROBE_ONLY set-ups probing those host drivers).
> 
> I am pretty sure  there are no rcar set-ups that use PCI_PROBE_ONLY,
> so I am happy for that code to go.
> 
> Thanks
> Phil
> 
> > Does it make the point clearer ?
> > 
> > > > https://patchwork.ozlabs.org/patch/545671/
> > > >
> > > > so unless you really have *existing* set-ups that require it, please
> > > > remove the respective checks from the host controller drivers, this is
> > > > becoming a serious issue, because either:
> > > >
> > > > - we claim resources if and only if PCI_PROBE_ONLY is set
> > > >
> > > > Either like this (to be done for every host controllers and ARM
> > > > bios32):
> > > >
> > > > https://patchwork.ozlabs.org/patch/545670/
> > > >
> > > > or in core ARM/ARM64 code - eg pcibios_fixup_bus() - (to avoid adding a
> > > > resource claiming call in ALL PCI host controllers)
> > > >
> > > > - or we *always* carry out resource claiming regardless of PCI_PROBE_ONLY
> > > >   (but on ARM we can't really do that since PCI FW set-up on most of the
> > > >   platforms is not present)
> > > >
> > > > On PCI_PROBE_ONLY systems resources claiming is mandatory if we want
> > > > to get rid of arches workarounds:
> > >
> > > I'm hoping to see x86 like behavior on ARM64 without any gotchas as
> > > there is nothing special about CPU type when it comes to PCI.
> > 
> > As I said, we must enforce it with ACPI, for DT platforms I am all
> > ears to decide how we can implement it sanely (I think the only way
> > to do it is by claiming the PCI resources on PCI_PROBE_ONLY systems,
> > that's not ideal but it simplifies things a lot).
> > 
> > Thanks,
> > Lorenzo
> > 
> > >
> > > >
> > > > https://patchwork.ozlabs.org/patch/545671/
> > > >
> > > > Comments very appreciated.
> > > >
> > > > Thanks,
> > > > Lorenzo
> > > > --
> > > > 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
> > > >
> > >
> > >
> > > --
> > > Sinan Kaya
> > > Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
> > > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
> > Foundation Collaborative Project
> > >
> --
> 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
> 

  parent reply	other threads:[~2016-01-28 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 16:04 [RFC] ARM/ARM64 PCI_PROBE_ONLY platforms Lorenzo Pieralisi
2016-01-20 16:13 ` Sinan Kaya
2016-01-20 18:10   ` Lorenzo Pieralisi
2016-01-20 18:15     ` Sinan Kaya
2016-01-29 23:26       ` Bjorn Helgaas
2016-01-22 16:28     ` Phil Edworthy
2016-01-25 17:51       ` Lorenzo Pieralisi
2016-01-28 17:27       ` Lorenzo Pieralisi [this message]
2016-01-29 12:02         ` Gabriele Paoloni
2016-01-29  6:32       ` Pratyush Anand
2016-01-29 23:25     ` Bjorn Helgaas
2016-02-01 16:28       ` Lorenzo Pieralisi
2016-02-01 21:19         ` Bjorn Helgaas
2016-01-29 23:06   ` Bjorn Helgaas
2016-01-30  0:14     ` Sinan Kaya
2016-01-30 13:30       ` Bjorn Helgaas
2016-01-30 17:51         ` Okaya
2016-02-01 15:25         ` Lorenzo Pieralisi
2016-02-01 21:12           ` 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=20160128172701.GA28468@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=bhelgaas@google.com \
    --cc=gabriele.paoloni@huawei.com \
    --cc=jingoohan1@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@codeaurora.org \
    --cc=phil.edworthy@renesas.com \
    --cc=pratyush.anand@gmail.com \
    --cc=wangzhou1@hisilicon.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.