Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Yureka Lilian <yureka@cyberchaos.dev>
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Sven Peter" <sven@kernel.org>, "Janne Grunau" <j@jannau.net>,
	"Neal Gompa" <neal@gompa.dev>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] PCI: apple: Integrate pwrctrl API
Date: Wed, 15 Jul 2026 12:56:07 +0100	[thread overview]
Message-ID: <86bjc8o4a0.wl-maz@kernel.org> (raw)
In-Reply-To: <76243051-e391-45d2-b47a-d4a904f0a36f@cyberchaos.dev>

On Tue, 14 Jul 2026 17:57:11 +0100,
Yureka Lilian <yureka@cyberchaos.dev> wrote:
> 
> 
> On 7/9/26 14:29, Manivannan Sadhasivam wrote:
> > On Tue, Jul 07, 2026 at 02:58:39PM +0100, Marc Zyngier wrote:
> >> Works fine is one thing. Being consistent with the way the rest of the
> >> driver works is another. pci_pwrctrl_create_device() and
> >> pci_pwrctrl_power_on_device() appear to do exactly what would be
> >> required for a single port. They just needs to be exported made
> >> global/exported.
> >> 
> > I'm fine with exporting pci_pwrctrl_create_device() and
> > pci_pwrctrl_power_on_device() and calling them with per-port np.
> > 
> > - Mani
> 
> In theory I do agree this would work to power on the slots, and I can
> send a v2 of the patch doing it that way, but I don't quite understand
> yet how this fits better with the existing driver code: If this is the
> case, what is the difference between pcie-apple and pcie-qcom and why
> should pcie-qcom use the recursive function but pcie-apple not?

Consistency is important to maintaining any piece of code, and I do
not want to deal with two management models simultaneously.

Furthermore, the qcom stuff is bolted on the side the DWC train wreck,
has to deal with the existing way the DWC driver works, and I see no
reason to be dragged down to that level of horror.

Yes, this is an arbitrary decision.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2026-07-15 11:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 22:38 [PATCH 0/2] PCI: apple: Integrate pwrctrl API Yureka Lilian
2026-07-06 22:38 ` [PATCH 1/2] " Yureka Lilian
2026-07-06 22:59   ` sashiko-bot
2026-07-07  9:25   ` Marc Zyngier
2026-07-07 12:04     ` Yureka Lilian
2026-07-07 13:58       ` Marc Zyngier
2026-07-09 12:29         ` Manivannan Sadhasivam
2026-07-14 16:57           ` Yureka Lilian
2026-07-15 11:56             ` Marc Zyngier [this message]
2026-07-06 22:38 ` [PATCH 2/2] arm64: dts: apple: t600x: Add PCIe pwren gpios Yureka Lilian
2026-07-06 22:58   ` sashiko-bot

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=86bjc8o4a0.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=asahi@lists.linux.dev \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j@jannau.net \
    --cc=krzk+dt@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=neal@gompa.dev \
    --cc=robh@kernel.org \
    --cc=sven@kernel.org \
    --cc=yureka@cyberchaos.dev \
    /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