From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-arm-kernel@lists.infradead.org,
Anand Moon <linux.amoon@gmail.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 1/3] PCI/pwrctrl: Add optional slot clock to pwrctrl driver for PCI slots
Date: Sat, 7 Jun 2025 21:48:03 +0200 [thread overview]
Message-ID: <e4d82284-d6e3-49d0-856e-e347d9d0de55@mailbox.org> (raw)
In-Reply-To: <CAMuHMdUFHKHKfymqa6jwfNnxZTAuH3kbj5WL+-zN=TR6XGd0eA@mail.gmail.com>
On 6/4/25 10:40 AM, Geert Uytterhoeven wrote:
> Hi Marek,
Hi,
> Thanks for your patch!
>
> On Sat, 31 May 2025 at 00:55, Marek Vasut
> <marek.vasut+renesas@mailbox.org> wrote:
>> Add the ability to enable optional slot clock into the pwrctrl driver.
>> This is used to enable slot clock in split-clock topologies, where the
>> PCIe host/controller supply and PCIe slot supply are not provided by
>> the same clock. The PCIe host/controller clock should be described in
>> the controller node as the controller clock, while the slot clock should
>> be described in controller bridge/slot subnode.
>>
>> Example DT snippet:
>> &pcicontroller {
>> clocks = <&clk_dif 0>; /* PCIe controller clock */
>>
>> pci@0,0 {
>> #address-cells = <3>;
>> #size-cells = <2>;
>> reg = <0x0 0x0 0x0 0x0 0x0>;
>> compatible = "pciclass,0604";
>> device_type = "pci";
>> clocks = <&clk_dif 1>; /* PCIe slot clock */
>
> I assume this should be documented in
> dtschema/schemas/pci/pci-bus-common.yaml, too?
Patch posted:
https://lore.kernel.org/all/20250607194353.79124-1-marek.vasut+renesas@mailbox.org/
The rest is fixed in V3, thanks.
prev parent reply other threads:[~2025-06-07 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 22:53 Marek Vasut
2025-05-30 22:53 ` [PATCH v2 2/3] arm64: dts: renesas: r8a779g0: Describe root port on R-Car V4H Marek Vasut
2025-06-04 9:13 ` Geert Uytterhoeven
2025-06-04 17:26 ` Manivannan Sadhasivam
2025-05-30 22:53 ` [PATCH v2 3/3] arm64: dts: renesas: r8a779g3: Describe split PCIe clock on V4H Sparrow Hawk Marek Vasut
2025-06-04 9:24 ` Geert Uytterhoeven
2025-06-04 17:31 ` Manivannan Sadhasivam
2025-06-05 7:33 ` Geert Uytterhoeven
2025-06-04 17:27 ` Manivannan Sadhasivam
2025-06-02 10:17 ` [PATCH v2 1/3] PCI/pwrctrl: Add optional slot clock to pwrctrl driver for PCI slots Bartosz Golaszewski
2025-06-04 8:40 ` Geert Uytterhoeven
2025-06-04 17:22 ` Manivannan Sadhasivam
2025-06-07 19:48 ` Marek Vasut [this message]
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=e4d82284-d6e3-49d0-856e-e347d9d0de55@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=magnus.damm@gmail.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=robh@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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
all inboxes | Powered by JetHome®