[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74e491ce-24c6-4d7a-a1b3-708857f03887@collabora.com>
Date: Mon, 6 Nov 2023 09:36:19 +0100
From: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
Jian Yang <jian.yang@...iatek.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Krzysztof WilczyĆski <kw@...ux.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Rob Herring <robh@...nel.org>,
Jianjun Wang <jianjun.wang@...iatek.com>
Cc: linux-pci@...r.kernel.org, linux-mediatek@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Project_Global_Chrome_Upstream_Group@...iatek.com,
Chuanjia.Liu@...iatek.com, Jieyy.Yang@...iatek.com,
Qizhong.Cheng@...iatek.com, Jianguo.Zhang@...iatek.com,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Abel Vesa <abel.vesa@...aro.org>
Subject: Re: [PATCH v4 2/2] PCI: mediatek-gen3: Add power and reset control
feature for downstream component
Il 06/11/23 08:53, Krzysztof Kozlowski ha scritto:
> On 06/11/2023 07:12, Jian Yang wrote:
>> From: "jian.yang" <jian.yang@...iatek.com>
>>
>> Make MediaTek's controller driver capable of controlling power
>> supplies and reset pin of a downstream component in power-on and
>> power-off process.
>>
>> Some downstream components (e.g., a WIFI chip) may need an extra
>> reset other than PERST# and their power supplies, depending on
>> the requirements of platform, may need to controlled by their
>> parent's driver. To meet the requirements described above, I add this
>> feature to MediaTek's PCIe controller driver as an optional feature.
>
> NAK, strong NAK. This should be done in a generic way because nothing
> here is specific to Mediatek.
>
> You just implement power sequencing of devices through quirks specific
> to one controller.
>
> Work with others to provide common solution.
> https://lpc.events/event/17/contributions/1507/
>
I agree that working with everyone else by adding pwrseq is a must, but other
other PCIe controllers are doing the exact same as this patch: if the supply
and gpio names are aligned with the others, why shouldn't we let this in and
then convert this driver, along with the others, to the new pwrseq subsystem
when it's ready?
That, because I expect the pwrseq to require a bit more time before being
ready to get upstream.
P.S.: Check Tegra, Broadcom, RockChip DW, IMX6Q-pcie.
Cheers,
Angelo
Powered by blists - more mailing lists