linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Jim Quinlan <jim2101024@gmail.com>
Cc: linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
	"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
	"Mark Brown" <broonie@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	james.quinlan@broadcom.com,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.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>,
	"Saenz Julienne" <nsaenzjulienne@suse.de>
Subject: Re: [PATCH v10 0/7] PCI: brcmstb: root port turns on sub-device power
Date: Fri, 10 Dec 2021 12:44:03 -0600	[thread overview]
Message-ID: <YbOf836C58fUSmCO@robh.at.kernel.org> (raw)
In-Reply-To: <20211209211407.8102-1-jim2101024@gmail.com>

On Thu, Dec 09, 2021 at 04:13:58PM -0500, Jim Quinlan wrote:
> v10 -- Bindings commit example: in comment, refer to bridge under
>        controller node as a root port. (Pali)
>     -- Bindings commit example: remove three properties that are not
>        appropriate for a PCIe endpoint node. (Rob)
> 
> v9  -- Simplify where this mechanism works: instead of looking for
>        regulators below every bridge, just look for them at the
>        bridge under the root bus (root port).  Now there is no
>        modification of portdrv_{pci,core}.c in this submission.
>     -- Although Pali is working on support for probing native
>        PCIe controller drivers, this work may take some time to
>        implement and it still might not be able to accomodate
>        our driver's requirements (e.g. vreg suspend/resume control).
>     -- Move regulator suspend/resume control to Brcm RC driver.  It
>        must reside there because (a) in order to know when to
>        initiate linkup during resume and (b) to turn on the
>        regulators before any config-space accesses occur.

You now have a mixture of 'generic' add/remove_bus hooks and the host 
controller suspend/resume managing the regulators. I think long term, 
the portdrv is going to be the right place for all of this with some 
interface defined for link control. So I think this solution moves 
sideways rather than towards anything common.

Unfortunately, the only leverage maintainers have to get folks to care 
about any refactoring is to reject features. We're lucky to find anyone 
to test refactoring when posted if done independently. There's a long 
list of commits of PCI hosts that I've broken to prove that. So it's 
up to Lorenzo and Bjorn on what they want to do here.

Rob

  parent reply	other threads:[~2021-12-10 18:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 21:13 [PATCH v10 0/7] PCI: brcmstb: root port turns on sub-device power Jim Quinlan
2021-12-09 21:13 ` [PATCH v10 1/7] PCI: brcmstb: Fix function return value handling Jim Quinlan
2021-12-09 21:34   ` Florian Fainelli
2021-12-09 21:14 ` [PATCH v10 2/7] dt-bindings: PCI: Correct brcmstb interrupts, interrupt-map Jim Quinlan
2021-12-09 21:14 ` [PATCH v10 3/7] dt-bindings: PCI: Add bindings for Brcmstb EP voltage regulators Jim Quinlan
2021-12-10 18:23   ` Rob Herring
2021-12-09 21:14 ` [PATCH v10 4/7] PCI: Add mechanism to turn on subdev regulators Jim Quinlan
2021-12-09 21:14 ` [PATCH v10 5/7] PCI: brcmstb: Split brcm_pcie_setup() into two funcs Jim Quinlan
2021-12-09 21:14 ` [PATCH v10 6/7] PCI: brcmstb: Add control of subdevice voltage regulators Jim Quinlan
2021-12-09 21:14 ` [PATCH v10 7/7] PCI: brcmstb: Do not turn off WOL regulators on suspend Jim Quinlan
2021-12-10 18:44 ` Rob Herring [this message]
2021-12-10 20:31   ` [PATCH v10 0/7] PCI: brcmstb: root port turns on sub-device power Florian Fainelli
2022-01-04 14:17     ` Lorenzo Pieralisi
2022-01-04 23:01       ` Jim Quinlan

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=YbOf836C58fUSmCO@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=james.quinlan@broadcom.com \
    --cc=jim2101024@gmail.com \
    --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=nsaenz@kernel.org \
    --cc=nsaenzjulienne@suse.de \
    /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).