From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: "Pali Rohár" <pali@kernel.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Guowen Shan" <gshan@redhat.com>,
"Tyrel Datwyler" <tyreld@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] powerpc/pci: Add config option for using OF 'reg' for PCI domain
Date: Fri, 15 Jul 2022 11:55:04 -0300 [thread overview]
Message-ID: <17fb8d12-60f9-09d5-91fa-09d5a5a9a4fd@igalia.com> (raw)
In-Reply-To: <20220706102148.5060-1-pali@kernel.org>
On 06/07/2022 07:21, Pali Rohár wrote:
> [...]
> Fix this issue and introduce a new option CONFIG_PPC_PCI_DOMAIN_FROM_OF_REG.
> When this option is disabled then powerpc kernel would assign PCI domains
> in the similar way like it is doing kernel for other architectures,
> starting from zero and also how it was done prior that commit.
I found this sentence a bit weird, "in the similar way like it is doing
kernel for other architectures", but other than that:
Reviewed-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
Thanks for the improvement!
Cheers,
Guilherme
>
> This option is by default enabled for powernv and pseries platform for which
> was that commit originally intended.
>
> With this change upgrading kernels from LTS 4.4 version does not change PCI
> domain on smaller embedded platforms with fixed number of PCIe controllers.
> And also ensure that PCI domain zero is present as before that commit.
>
> Fixes: 63a72284b159 ("powerpc/pci: Assign fixed PHB number based on device-tree properties")
> Signed-off-by: Pali Rohár <pali@kernel.org>
> ---
> Changes in v2:
> * Enable CONFIG_PPC_PCI_DOMAIN_FROM_OF_REG by default on powernv and pseries
> ---
> arch/powerpc/Kconfig | 11 +++++++++++
> arch/powerpc/kernel/pci-common.c | 4 ++--
> 2 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index f66084bc1dfe..053a88e84049 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -386,6 +386,17 @@ config PPC_OF_PLATFORM_PCI
> depends on PCI
> depends on PPC64 # not supported on 32 bits yet
>
> +config PPC_PCI_DOMAIN_FROM_OF_REG
> + bool "Use OF reg property for PCI domain"
> + depends on PCI
> + default y if PPC_PSERIES || PPC_POWERNV
> + help
> + By default PCI domain for host bridge during its registration is
> + chosen as the lowest unused PCI domain number.
> +
> + When this option is enabled then PCI domain can be determined
> + also from lower bits of the OF / Device Tree 'reg' property.
> +
> config ARCH_SUPPORTS_UPROBES
> def_bool y
>
> diff --git a/arch/powerpc/kernel/pci-common.c b/arch/powerpc/kernel/pci-common.c
> index 068410cd54a3..7f959df34833 100644
> --- a/arch/powerpc/kernel/pci-common.c
> +++ b/arch/powerpc/kernel/pci-common.c
> @@ -74,7 +74,6 @@ void __init set_pci_dma_ops(const struct dma_map_ops *dma_ops)
> static int get_phb_number(struct device_node *dn)
> {
> int ret, phb_id = -1;
> - u32 prop_32;
> u64 prop;
>
> /*
> @@ -83,7 +82,8 @@ static int get_phb_number(struct device_node *dn)
> * reading "ibm,opal-phbid", only present in OPAL environment.
> */
> ret = of_property_read_u64(dn, "ibm,opal-phbid", &prop);
> - if (ret) {
> + if (ret && IS_ENABLED(CONFIG_PPC_PCI_DOMAIN_FROM_OF_REG)) {
> + u32 prop_32;
> ret = of_property_read_u32_index(dn, "reg", 1, &prop_32);
> prop = prop_32;
> }
next prev parent reply other threads:[~2022-07-15 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 10:21 Pali Rohár
2022-07-06 10:21 ` [PATCH v2 2/2] powerpc/pci: Prefer PCI domain assignment via DT 'linux,pci-domain' and alias Pali Rohár
2022-08-13 13:57 ` Guenter Roeck
2022-08-15 5:46 ` Michael Ellerman
2022-09-23 3:21 ` Benjamin Herrenschmidt
2022-07-15 14:55 ` Guilherme G. Piccoli [this message]
2022-07-15 17:11 ` [PATCH v2 1/2] powerpc/pci: Add config option for using OF 'reg' for PCI domain Pali Rohár
2022-07-15 18:32 ` Guilherme G. Piccoli
2022-07-16 11:35 ` Pali Rohár
2022-07-27 12:33 ` Michael Ellerman
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=17fb8d12-60f9-09d5-91fa-09d5a5a9a4fd@igalia.com \
--to=gpiccoli@igalia.com \
--cc=benh@kernel.crashing.org \
--cc=gshan@redhat.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=pali@kernel.org \
--cc=paulus@samba.org \
--cc=tyreld@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
all inboxes | Powered by JetHome®