From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Jim Quinlan <james.quinlan@broadcom.com>
Cc: 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,
"Conor Dooley" <conor+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Jim Quinlan" <jim2101024@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v6 0/5] PCI: brcmstb: Configure appropriate HW CLKREQ# mode
Date: Mon, 21 Aug 2023 10:34:51 +0200 [thread overview]
Message-ID: <ZOMhq8a/wnURWsFP@lpieralisi> (raw)
In-Reply-To: <20230623144100.34196-1-james.quinlan@broadcom.com>
On Fri, Jun 23, 2023 at 10:40:53AM -0400, Jim Quinlan wrote:
> v6 -- No code has been changed.
> -- Changed commit subject and comment in "#PERST" commit (Bjorn, Cyril)
> -- Changed sign-off and author email address for all commits.
> This was due to a change in Broadcom's upstreaming policy.
>
> v5 -- Remove DT property "brcm,completion-timeout-us" from
> "DT bindings" commit. Although this error may be reported
> as a completion timeout, its cause was traced to an
> internal bus timeout which may occur even when there is
> no PCIe access being processed. We set a timeout of four
> seconds only if we are operating in "L1SS CLKREQ#" mode.
> -- Correct CEM 2.0 reference provided by HW engineer,
> s/3.2.5.2.5/3.2.5.2.2/ (Bjorn)
> -- Add newline to dev_info() string (Stefan)
> -- Change variable rval to unsigned (Stefan)
> -- s/implementaion/implementation/ (Bjorn)
> -- s/superpowersave/powersupersave/ (Bjorn)
> -- Slightly modify message on "PERST#" commit.
> -- Rebase to torvalds master
>
> v4 -- New commit that asserts PERST# for 2711/RPi SOCs at PCIe RC
> driver probe() time. This is done in Raspian Linux and its
> absence may be the cause of a failing test case.
> -- New commit that removes stale comment.
>
> v3 -- Rewrote commit msgs and comments refering panics if L1SS
> is enabled/disabled; the code snippet that unadvertises L1SS
> eliminates the panic scenario. (Bjorn)
> -- Add reference for "400ns of CLKREQ# assertion" blurb (Bjorn)
> -- Put binding names in DT commit Subject (Bjorn)
> -- Add a verb to a commit's subject line (Bjorn)
> -- s/accomodat(\w+)/accommodat$1/g (Bjorn)
> -- Rewrote commit msgs and comments refering panics if L1SS
> is enabled/disabled; the code snippet that unadvertises L1SS
> eliminates the panic scenario. (Bjorn)
>
> v2 -- Changed binding property 'brcm,completion-timeout-msec' to
> 'brcm,completion-timeout-us'. (StefanW for standard suffix).
> -- Warn when clamping timeout value, and include clamped
> region in message. Also add min and max in YAML. (StefanW)
> -- Qualify description of "brcm,completion-timeout-us" so that
> it refers to PCIe transactions. (StefanW)
> -- Remvove mention of Linux specifics in binding description. (StefanW)
> -- s/clkreq#/CLKREQ#/g (Bjorn)
> -- Refactor completion-timeout-us code to compare max and min to
> value given by the property (as opposed to the computed value).
>
> v1 -- The current driver assumes the downstream devices can
> provide CLKREQ# for ASPM. These commits accomodate devices
> w/ or w/o clkreq# and also handle L1SS-capable devices.
>
> -- The Raspian Linux folks have already been using a PCIe RC
> property "brcm,enable-l1ss". These commits use the same
> property, in a backward-compatible manner, and the implementaion
> adds more detail and also automatically identifies devices w/o
> a clkreq# signal, i.e. most devices plugged into an RPi CM4
> IO board.
>
>
> Jim Quinlan (5):
> dt-bindings: PCI: brcmstb: Add brcm,enable-l1ss property
> PCI: brcmstb: Configure HW CLKREQ# mode appropriate for downstream
> device
I am not merging the first two patches since the discussion thread
is still open and I'd like to understand better what can/should be
done, sorry.
> PCI: brcmstb: Set higher value for internal bus timeout
> PCI: brcmstb: Assert PERST# on BCM2711
> PCI: brcmstb: Remove stale comment
Is it OK to apply these three on their own ? Overall it would be
great to avoid mixing patches with different end goals in a single
series.
Thanks,
Lorenzo
> .../bindings/pci/brcm,stb-pcie.yaml | 9 ++
> drivers/pci/controller/pcie-brcmstb.c | 91 ++++++++++++++++---
> 2 files changed, 89 insertions(+), 11 deletions(-)
>
>
> base-commit: 8a28a0b6f1a1dcbf5a834600a9acfbe2ba51e5eb
> --
> 2.17.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Jim Quinlan <james.quinlan@broadcom.com>
Cc: 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,
"Conor Dooley" <conor+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Jim Quinlan" <jim2101024@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v6 0/5] PCI: brcmstb: Configure appropriate HW CLKREQ# mode
Date: Mon, 21 Aug 2023 10:34:51 +0200 [thread overview]
Message-ID: <ZOMhq8a/wnURWsFP@lpieralisi> (raw)
In-Reply-To: <20230623144100.34196-1-james.quinlan@broadcom.com>
On Fri, Jun 23, 2023 at 10:40:53AM -0400, Jim Quinlan wrote:
> v6 -- No code has been changed.
> -- Changed commit subject and comment in "#PERST" commit (Bjorn, Cyril)
> -- Changed sign-off and author email address for all commits.
> This was due to a change in Broadcom's upstreaming policy.
>
> v5 -- Remove DT property "brcm,completion-timeout-us" from
> "DT bindings" commit. Although this error may be reported
> as a completion timeout, its cause was traced to an
> internal bus timeout which may occur even when there is
> no PCIe access being processed. We set a timeout of four
> seconds only if we are operating in "L1SS CLKREQ#" mode.
> -- Correct CEM 2.0 reference provided by HW engineer,
> s/3.2.5.2.5/3.2.5.2.2/ (Bjorn)
> -- Add newline to dev_info() string (Stefan)
> -- Change variable rval to unsigned (Stefan)
> -- s/implementaion/implementation/ (Bjorn)
> -- s/superpowersave/powersupersave/ (Bjorn)
> -- Slightly modify message on "PERST#" commit.
> -- Rebase to torvalds master
>
> v4 -- New commit that asserts PERST# for 2711/RPi SOCs at PCIe RC
> driver probe() time. This is done in Raspian Linux and its
> absence may be the cause of a failing test case.
> -- New commit that removes stale comment.
>
> v3 -- Rewrote commit msgs and comments refering panics if L1SS
> is enabled/disabled; the code snippet that unadvertises L1SS
> eliminates the panic scenario. (Bjorn)
> -- Add reference for "400ns of CLKREQ# assertion" blurb (Bjorn)
> -- Put binding names in DT commit Subject (Bjorn)
> -- Add a verb to a commit's subject line (Bjorn)
> -- s/accomodat(\w+)/accommodat$1/g (Bjorn)
> -- Rewrote commit msgs and comments refering panics if L1SS
> is enabled/disabled; the code snippet that unadvertises L1SS
> eliminates the panic scenario. (Bjorn)
>
> v2 -- Changed binding property 'brcm,completion-timeout-msec' to
> 'brcm,completion-timeout-us'. (StefanW for standard suffix).
> -- Warn when clamping timeout value, and include clamped
> region in message. Also add min and max in YAML. (StefanW)
> -- Qualify description of "brcm,completion-timeout-us" so that
> it refers to PCIe transactions. (StefanW)
> -- Remvove mention of Linux specifics in binding description. (StefanW)
> -- s/clkreq#/CLKREQ#/g (Bjorn)
> -- Refactor completion-timeout-us code to compare max and min to
> value given by the property (as opposed to the computed value).
>
> v1 -- The current driver assumes the downstream devices can
> provide CLKREQ# for ASPM. These commits accomodate devices
> w/ or w/o clkreq# and also handle L1SS-capable devices.
>
> -- The Raspian Linux folks have already been using a PCIe RC
> property "brcm,enable-l1ss". These commits use the same
> property, in a backward-compatible manner, and the implementaion
> adds more detail and also automatically identifies devices w/o
> a clkreq# signal, i.e. most devices plugged into an RPi CM4
> IO board.
>
>
> Jim Quinlan (5):
> dt-bindings: PCI: brcmstb: Add brcm,enable-l1ss property
> PCI: brcmstb: Configure HW CLKREQ# mode appropriate for downstream
> device
I am not merging the first two patches since the discussion thread
is still open and I'd like to understand better what can/should be
done, sorry.
> PCI: brcmstb: Set higher value for internal bus timeout
> PCI: brcmstb: Assert PERST# on BCM2711
> PCI: brcmstb: Remove stale comment
Is it OK to apply these three on their own ? Overall it would be
great to avoid mixing patches with different end goals in a single
series.
Thanks,
Lorenzo
> .../bindings/pci/brcm,stb-pcie.yaml | 9 ++
> drivers/pci/controller/pcie-brcmstb.c | 91 ++++++++++++++++---
> 2 files changed, 89 insertions(+), 11 deletions(-)
>
>
> base-commit: 8a28a0b6f1a1dcbf5a834600a9acfbe2ba51e5eb
> --
> 2.17.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-21 8:35 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 14:40 [PATCH v6 0/5] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Jim Quinlan
2023-06-23 14:40 ` Jim Quinlan
2023-06-23 14:40 ` Jim Quinlan
2023-06-23 14:40 ` [PATCH v6 1/5] dt-bindings: PCI: brcmstb: Add brcm,enable-l1ss property Jim Quinlan
2023-06-23 14:40 ` Jim Quinlan
2023-08-21 14:46 ` Lorenzo Pieralisi
2023-08-21 14:46 ` Lorenzo Pieralisi
2023-08-21 15:25 ` Jim Quinlan
2023-08-21 15:25 ` Jim Quinlan
2023-08-21 15:41 ` Lorenzo Pieralisi
2023-08-21 15:41 ` Lorenzo Pieralisi
2023-08-21 16:01 ` Jim Quinlan
2023-08-21 16:01 ` Jim Quinlan
2023-08-23 7:30 ` Lorenzo Pieralisi
2023-08-23 7:30 ` Lorenzo Pieralisi
2023-08-23 12:42 ` Bjorn Helgaas
2023-08-23 12:42 ` Bjorn Helgaas
2023-08-23 15:02 ` Jim Quinlan
2023-08-23 15:02 ` Jim Quinlan
2023-08-23 14:48 ` Rob Herring
2023-08-23 14:48 ` Rob Herring
2023-08-23 16:29 ` Lorenzo Pieralisi
2023-08-23 16:29 ` Lorenzo Pieralisi
2023-08-23 18:26 ` Manivannan Sadhasivam
2023-08-23 18:26 ` Manivannan Sadhasivam
2023-08-24 15:19 ` Jim Quinlan
2023-08-24 15:19 ` Jim Quinlan
2023-06-23 14:40 ` [PATCH v6 2/5] PCI: brcmstb: Configure HW CLKREQ# mode appropriate for downstream device Jim Quinlan
2023-06-23 14:40 ` Jim Quinlan
2023-09-05 20:24 ` Sam Edwards
2023-09-05 20:24 ` Sam Edwards
2023-06-23 14:40 ` [PATCH v6 3/5] PCI: brcmstb: Set higher value for internal bus timeout Jim Quinlan
2023-06-23 14:40 ` Jim Quinlan
2023-07-28 8:43 ` Lorenzo Pieralisi
2023-07-28 8:43 ` Lorenzo Pieralisi
[not found] ` <CA+-6iNzuNZ0TGUvSKsq3outKnCBTkqtxygKOuM4=J-CPxcBb2g@mail.gmail.com>
2023-08-14 19:30 ` Jim Quinlan
2023-08-14 19:30 ` Jim Quinlan
2023-08-14 22:06 ` Bjorn Helgaas
2023-08-14 22:06 ` Bjorn Helgaas
2023-08-15 12:34 ` Jim Quinlan
2023-08-15 12:34 ` Jim Quinlan
2023-06-23 14:40 ` [PATCH v6 4/5] PCI: brcmstb: Assert PERST# on BCM2711 Jim Quinlan
2023-06-23 14:40 ` Jim Quinlan
2023-06-23 14:40 ` [PATCH v6 5/5] PCI: brcmstb: Remove stale comment Jim Quinlan
2023-06-23 14:40 ` Jim Quinlan
2023-06-29 1:59 ` [PATCH v6 0/5] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Cyril Brulebois
2023-06-29 1:59 ` Cyril Brulebois
2023-08-21 8:34 ` Lorenzo Pieralisi [this message]
2023-08-21 8:34 ` Lorenzo Pieralisi
2023-08-21 12:15 ` Jim Quinlan
2023-08-21 12:15 ` Jim Quinlan
2023-08-21 14:42 ` Lorenzo Pieralisi
2023-08-21 14:42 ` Lorenzo Pieralisi
2023-08-24 15:36 ` (subset) " Lorenzo Pieralisi
2023-08-24 15:36 ` Lorenzo Pieralisi
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=ZOMhq8a/wnURWsFP@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=kibi@debian.org \
--cc=krzysztof.kozlowski+dt@linaro.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=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 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.