From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Alistair Popple <alistair@popple.id.au>,
Sam Bobroff <sbobroff@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>,
Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH kernel v2] powerpc/pci/of: Parse unassigned resources
Date: Mon, 8 Jul 2019 11:19:43 +1000 (AEST) [thread overview]
Message-ID: <45hng32RrMz9sP2@ozlabs.org> (raw)
In-Reply-To: <20190626023746.94250-1-aik@ozlabs.ru>
On Wed, 2019-06-26 at 02:37:46 UTC, Alexey Kardashevskiy wrote:
> The pseries platform uses the PCI_PROBE_DEVTREE method of PCI probing
> which reads "assigned-addresses" of every PCI device and initializes
> the device resources. However if the property is missing or zero sized,
> then there is no fallback of any kind and the PCI resources remain
> undiscovered, i.e. pdev->resource[] array remains empty.
>
> This adds a fallback which parses the "reg" property in pretty much same
> way except it marks resources as "unset" which later make Linux assign
> those resources proper addresses.
>
> This has an effect when:
> 1. a hypervisor failed to assign any resource for a device;
> 2. /chosen/linux,pci-probe-only=0 is in the DT so the system may try
> assigning a resource.
> Neither is likely to happen under PowerVM.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/dead1c845dbe97e0061dae2017eaf3bd8f8f06ee
cheers
prev parent reply other threads:[~2019-07-08 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 2:37 [PATCH kernel v2] powerpc/pci/of: Parse unassigned resources Alexey Kardashevskiy
2019-07-08 1:19 ` Michael Ellerman [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=45hng32RrMz9sP2@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=alistair@popple.id.au \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.com \
--cc=paulus@samba.org \
--cc=sbobroff@linux.ibm.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).