From: nicolas saenz julienne <nsaenz@kernel.org>
To: Jeremy Linton <jeremy.linton@arm.com>, linux-pci@vger.kernel.org
Cc: lorenzo.pieralisi@arm.com, bhelgaas@google.com,
rjw@rjwysocki.net, lenb@kernel.org, robh@kernel.org,
kw@linux.com, f.fainelli@gmail.com,
bcm-kernel-feedback-list@broadcom.com,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] PCI: brcmstb: Add ACPI config space quirk
Date: Mon, 30 Aug 2021 10:36:43 +0200 [thread overview]
Message-ID: <44ad79081412af289c68e74cdecb6a2baa2e873c.camel@kernel.org> (raw)
In-Reply-To: <20210826071557.29239-3-jeremy.linton@arm.com>
Hi Jeremy,
sorry for the late reply, I've been on vacation.
On Thu, 2021-08-26 at 02:15 -0500, Jeremy Linton wrote:
[...]
> +static void __iomem *brcm_pcie_map_conf2(struct pci_bus *bus,
> + unsigned int devfn, int where)
> +{
> + struct pci_config_window *cfg = bus->sysdata;
> + void __iomem *base = cfg->win;
> + int idx;
> + u32 up;
> +
> + /* Accesses to the RC go right to the RC registers if slot==0 */
> + if (pci_is_root_bus(bus))
> + return PCI_SLOT(devfn) ? NULL : base + where;
> +
> + /*
> + * Assure the link is up before sending requests downstream. This is done
> + * to avoid sending transactions to EPs that don't exist. Link flap
> + * conditions/etc make this race more probable. The resulting unrecoverable
> + * SERRORs will result in the machine crashing.
> + */
> + up = readl(base + PCIE_MISC_PCIE_STATUS);
> + if (!(up & PCIE_MISC_PCIE_STATUS_PCIE_DL_ACTIVE_MASK))
> + return NULL;
> +
> + if (!(up & PCIE_MISC_PCIE_STATUS_PCIE_PHYLINKUP_MASK))
> + return NULL;
Couldn't this be integrated in the original brcm_pcie_map_conf()? IIUC there is
nothing ACPI specific about it. It'd also make for less code duplication.
Regards,
Nicolas
next prev parent reply other threads:[~2021-08-30 8:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 7:15 [PATCH v3 0/4] CM4 ACPI PCIe quirk Jeremy Linton
2021-08-26 7:15 ` [PATCH v3 1/4] PCI: brcmstb: Break register definitions into separate header Jeremy Linton
2021-08-30 8:37 ` nicolas saenz julienne
2021-08-26 7:15 ` [PATCH v3 2/4] PCI: brcmstb: Add ACPI config space quirk Jeremy Linton
2021-08-30 8:36 ` nicolas saenz julienne [this message]
2021-08-30 16:23 ` Jeremy Linton
2021-08-30 16:27 ` Florian Fainelli
2021-08-30 17:17 ` nicolas saenz julienne
2021-10-05 15:32 ` Bjorn Helgaas
2021-10-05 15:57 ` Jeremy Linton
2021-10-05 19:43 ` Pali Rohár
2021-10-05 22:25 ` Jeremy Linton
2021-10-06 2:07 ` Florian Fainelli
2021-10-22 17:04 ` Florian Fainelli
2021-10-22 17:17 ` Pali Rohár
2021-10-22 17:29 ` Florian Fainelli
2021-10-22 17:57 ` Pali Rohár
2021-08-26 7:15 ` [PATCH v3 3/4] PCI/ACPI: Add Broadcom bcm2711 MCFG quirk Jeremy Linton
2021-08-30 8:37 ` nicolas saenz julienne
2021-09-13 16:12 ` Rafael J. Wysocki
2021-10-05 15:10 ` Bjorn Helgaas
2021-10-05 15:43 ` Jeremy Linton
2021-10-05 22:31 ` Bjorn Helgaas
2021-10-05 23:32 ` Jeremy Linton
2021-10-05 20:02 ` Pali Rohár
2021-10-05 22:44 ` Jeremy Linton
2021-08-26 7:15 ` [PATCH v3 4/4] MAINTAINERS: Widen brcmstb PCIe file scope Jeremy Linton
2021-08-30 8:38 ` nicolas saenz julienne
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=44ad79081412af289c68e74cdecb6a2baa2e873c.camel@kernel.org \
--to=nsaenz@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=f.fainelli@gmail.com \
--cc=jeremy.linton@arm.com \
--cc=kw@linux.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.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).