From: Stefan Wahren <stefan.wahren@i2se.com>
To: Jim Quinlan <jim2101024@gmail.com>,
linux-pci@vger.kernel.org,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Cyril Brulebois <kibi@debian.org>,
Phil Elwell <phil@raspberrypi.com>,
bcm-kernel-feedback-list@broadcom.com,
james.quinlan@broadcom.com
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 3/5] PCI: brcmstb: Set PCIe transaction completion timeout
Date: Wed, 3 May 2023 08:06:33 +0200 [thread overview]
Message-ID: <db172ecd-879b-b35b-2f02-e63dd9c956e2@i2se.com> (raw)
In-Reply-To: <20230428223500.23337-4-jim2101024@gmail.com>
Hi Jim,
Am 29.04.23 um 00:34 schrieb Jim Quinlan:
> Since the STB PCIe HW will cause a CPU abort on a PCIe transaction
> completion timeout abort, we might as well extend the default timeout
> limit. Further, different devices and systems may requires a larger or
> smaller amount commensurate with their L1SS exit time, so the property
> "brcm,completion-timeout-us" may be used to set a custom timeout value.
>
> Tested-by: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
> ---
> drivers/pci/controller/pcie-brcmstb.c | 30 +++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/drivers/pci/controller/pcie-brcmstb.c b/drivers/pci/controller/pcie-brcmstb.c
> index c4b076ea5180..c2cb683447ac 100644
> --- a/drivers/pci/controller/pcie-brcmstb.c
> +++ b/drivers/pci/controller/pcie-brcmstb.c
> @@ -1080,6 +1080,35 @@ static void brcm_config_clkreq(struct brcm_pcie *pcie)
> writel(clkreq_set, pcie->base + PCIE_MISC_HARD_PCIE_HARD_DEBUG);
> }
>
> +static void brcm_config_completion_timeout(struct brcm_pcie *pcie)
> +{
> + /* TIMEOUT register is two registers before RGR1_SW_INIT_1 */
> + const char *fmt = "brcm,completion-timeout-us clamped to region [%u..%u]\n";
> + const unsigned int REG_OFFSET = PCIE_RGR1_SW_INIT_1(pcie) - 8;
> + const u32 timeout_us_min = 16;
> + const u32 timeout_us_max = 19884107;
> + u32 timeout_us = 1000000; /* Our default, 1 second */
> + int rval, ret;
> +
> + ret = of_property_read_u32(pcie->np, "brcm,completion-timeout-us",
> + &timeout_us);
> + if (ret && ret != -EINVAL)
> + dev_err(pcie->dev, "malformed/invalid 'brcm,completion-timeout-us'\n");
> +
> + /* If needed, clamp the requested timeout value and issue a warning */
> + if (timeout_us < timeout_us_min) {
> + timeout_us = timeout_us_min;
> + dev_warn(pcie->dev, fmt, timeout_us_min, timeout_us_max);
> + } else if (timeout_us > timeout_us_max) {
> + timeout_us = timeout_us_max;
> + dev_warn(pcie->dev, fmt, timeout_us_min, timeout_us_max);
> + }
> +
> + /* Each unit in timeout register is 1/216,000,000 seconds */
> + rval = 216 * timeout_us;
> + writel(rval, pcie->base + REG_OFFSET);
i don't think "int" is the proper type for rval here
> +}
> +
> static int brcm_pcie_start_link(struct brcm_pcie *pcie)
> {
> struct device *dev = pcie->dev;
> @@ -1110,6 +1139,7 @@ static int brcm_pcie_start_link(struct brcm_pcie *pcie)
> return -ENODEV;
> }
>
> + brcm_config_completion_timeout(pcie);
> brcm_config_clkreq(pcie);
>
> if (pcie->gen)
next prev parent reply other threads:[~2023-05-03 6:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 22:34 [PATCH v4 0/5] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Jim Quinlan
2023-04-28 22:34 ` [PATCH v4 1/5] dt-bindings: PCI: brcmstb: brcm,{enable-l1ss,completion-timeout-us} props Jim Quinlan
2023-04-30 19:10 ` Bjorn Helgaas
2023-05-03 14:38 ` Jim Quinlan
2023-05-03 18:07 ` Bjorn Helgaas
2023-05-03 21:38 ` Jim Quinlan
2023-05-03 22:18 ` Bjorn Helgaas
2023-05-05 12:39 ` Jim Quinlan
2023-05-05 13:34 ` Bjorn Helgaas
2023-05-05 14:40 ` Jim Quinlan
2023-05-05 14:54 ` Bjorn Helgaas
2023-04-28 22:34 ` [PATCH v4 2/5] PCI: brcmstb: Configure HW CLKREQ# mode appropriate for downstream device Jim Quinlan
2023-05-03 6:09 ` Stefan Wahren
2023-04-28 22:34 ` [PATCH v4 3/5] PCI: brcmstb: Set PCIe transaction completion timeout Jim Quinlan
2023-04-30 19:13 ` Bjorn Helgaas
2023-04-30 21:24 ` Jim Quinlan
2023-04-30 22:38 ` Bjorn Helgaas
2023-05-01 20:55 ` Lukas Wunner
2023-05-03 14:06 ` Jim Quinlan
2023-05-03 6:06 ` Stefan Wahren [this message]
2023-04-28 22:34 ` [PATCH v4 4/5] PCI: brcmstb: Don't assume 2711 bootloader leaves PERST# asserted Jim Quinlan
2023-04-28 22:34 ` [PATCH v4 5/5] PCI: brcmstb: Remove stale comment Jim Quinlan
2023-05-02 23:15 ` [PATCH v4 0/5] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Cyril Brulebois
2023-05-03 18:10 ` Jim Quinlan
2023-05-03 19:10 ` Cyril Brulebois
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=db172ecd-879b-b35b-2f02-e63dd9c956e2@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=kibi@debian.org \
--cc=kw@linux.com \
--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=lpieralisi@kernel.org \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--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).