All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Jim Quinlan <james.quinlan@broadcom.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
Cc: "Conor Dooley" <conor+dt@kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"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>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v7 0/3] PCI: brcmstb: Configure appropriate HW CLKREQ# mode
Date: Mon, 13 Nov 2023 09:36:34 -0800	[thread overview]
Message-ID: <ee43568a-f96e-4d9f-9a4d-1df1b139196b@broadcom.com> (raw)
In-Reply-To: <20231109191355.27738-1-james.quinlan@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 4208 bytes --]

On 11/9/23 11:13, Jim Quinlan wrote:
> v7 -- Manivannan Sadhasivam suggested (a) making the property look like a
>        network phy-mode and (b) keeping the code simple (not counting clkreq
>        signal appearances, un-advertising capabilites, etc).  This is
>        what I have done.  The property is now "brcm,clkreq-mode" and
>        the values may be one of "safe", "default", and "no-l1ss".  The
>        default setting is to employ the most capable power savings mode.
> 
> 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.

For the entire series:

Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>

on all of my available devices:

- SUNIX Co., Ltd. Multiport serial controller
- Broadcom BCM4331 Wi-Fi
- Broadcom BCM43224 Wi-Fi
- Broadcom BCM4322 Wi-Fi
- Qualcomm Atheros AR5008
- Broadcom BCM4366 Wi-Fi
- Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s controller
- Intel 7260 Wi-Fi
- Intel Corporation 82574L Gigabit Network Connection
- Broadcom NetXtreme BCM5751 Gigabit Ethernet
- Pepperl+Fuchs RocketPort EXPRESS 8-port w/Octa Cable
- Micron/Crucial Technology P2 NVMe PCIe SSD
- ASM1184e PCIe Switch Port
-- 
Florian


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Jim Quinlan <james.quinlan@broadcom.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
Cc: "Conor Dooley" <conor+dt@kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"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>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v7 0/3] PCI: brcmstb: Configure appropriate HW CLKREQ# mode
Date: Mon, 13 Nov 2023 09:36:34 -0800	[thread overview]
Message-ID: <ee43568a-f96e-4d9f-9a4d-1df1b139196b@broadcom.com> (raw)
In-Reply-To: <20231109191355.27738-1-james.quinlan@broadcom.com>


[-- Attachment #1.1: Type: text/plain, Size: 4208 bytes --]

On 11/9/23 11:13, Jim Quinlan wrote:
> v7 -- Manivannan Sadhasivam suggested (a) making the property look like a
>        network phy-mode and (b) keeping the code simple (not counting clkreq
>        signal appearances, un-advertising capabilites, etc).  This is
>        what I have done.  The property is now "brcm,clkreq-mode" and
>        the values may be one of "safe", "default", and "no-l1ss".  The
>        default setting is to employ the most capable power savings mode.
> 
> 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.

For the entire series:

Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>

on all of my available devices:

- SUNIX Co., Ltd. Multiport serial controller
- Broadcom BCM4331 Wi-Fi
- Broadcom BCM43224 Wi-Fi
- Broadcom BCM4322 Wi-Fi
- Qualcomm Atheros AR5008
- Broadcom BCM4366 Wi-Fi
- Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s controller
- Intel 7260 Wi-Fi
- Intel Corporation 82574L Gigabit Network Connection
- Broadcom NetXtreme BCM5751 Gigabit Ethernet
- Pepperl+Fuchs RocketPort EXPRESS 8-port w/Octa Cable
- Micron/Crucial Technology P2 NVMe PCIe SSD
- ASM1184e PCIe Switch Port
-- 
Florian


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-11-13 17:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 19:13 [PATCH v7 0/3] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Jim Quinlan
2023-11-09 19:13 ` Jim Quinlan
2023-11-09 19:13 ` [PATCH v7 1/3] dt-bindings: PCI: brcmstb: Add property "brcm,clkreq-mode" Jim Quinlan
2023-11-09 19:13   ` Jim Quinlan
2023-11-09 21:33   ` Bjorn Helgaas
2023-11-09 21:33     ` Bjorn Helgaas
2023-11-09 19:13 ` [PATCH v7 2/3] PCI: brcmstb: Configure HW CLKREQ# mode appropriate for downstream device Jim Quinlan
2023-11-09 19:13   ` Jim Quinlan
2023-11-09 21:27   ` Bjorn Helgaas
2023-11-09 21:27     ` Bjorn Helgaas
2023-11-09 22:06     ` Jim Quinlan
2023-11-09 22:06       ` Jim Quinlan
2023-11-09 22:31       ` Bjorn Helgaas
2023-11-09 22:31         ` Bjorn Helgaas
2023-11-10 13:01         ` Jim Quinlan
2023-11-10 13:01           ` Jim Quinlan
2023-11-10 14:39           ` Bjorn Helgaas
2023-11-10 14:39             ` Bjorn Helgaas
2023-11-09 19:13 ` [PATCH v7 3/3] PCI: brcmstb: Set higher value for internal bus timeout Jim Quinlan
2023-11-09 19:13   ` Jim Quinlan
2023-11-09 21:27   ` Bjorn Helgaas
2023-11-09 21:27     ` Bjorn Helgaas
2023-11-13 17:36 ` Florian Fainelli [this message]
2023-11-13 17:36   ` [PATCH v7 0/3] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Florian Fainelli

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=ee43568a-f96e-4d9f-9a4d-1df1b139196b@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=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 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.