From: Marek Vasut <marek.vasut@mailbox.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-arm-kernel@lists.infradead.org,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Aradhya Bhatia" <a-bhatia1@ti.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Heiko Stuebner" <heiko@sntech.de>,
"Junhao Xie" <bigfoot@classfun.cn>,
"Kever Yang" <kever.yang@rock-chips.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"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/4] dt-bindings: PCI: rcar-gen4-pci-host: Document optional aux clock
Date: Mon, 12 May 2025 22:42:20 +0200 [thread overview]
Message-ID: <84cc6341-a2c1-4e3c-8c9e-2bc6589c52a6@mailbox.org> (raw)
In-Reply-To: <2ny7jhcp2g5ixo75donutncxnjdawzev3mw7cytvhbk6szl3ue@vixax5lwpycw>
On 5/9/25 9:37 PM, Manivannan Sadhasivam wrote:
> On Sun, Apr 06, 2025 at 04:45:21PM +0200, Marek Vasut wrote:
>> Document 'aux' clock which are used to supply the PCIe bus. This
>> is useful in case of a hardware setup, where the PCIe controller
>> input clock and the PCIe bus clock are supplied from the same
>> clock synthesiser, but from different differential clock outputs:
>
> How different is this clock from the 'reference clock'? I'm not sure what you
> mean by 'PCIe bus clock' here. AFAIK, endpoint only takes the reference clock
> and the binding already has 'ref' clock for that purpose. So I don't understand
> how this new clock is connected to the endpoint device.
See the ASCII art below , CLK_DIF0 is 'ref' clock that feeds the
controller side, CLK_DIF1 is the bus (or 'aux') clock which feeds the
bus (or endpoint) side. Both clock come from the same clock synthesizer,
but from two separate clock outputs of the synthesizer.
>> ____________ _____________
>> | R-Car PCIe | | PCIe device |
>> | | | |
>> | PCIe RX<|==================|>PCIe TX |
>> | PCIe TX<|==================|>PCIe RX |
>> | | | |
>> | PCIe CLK<|======.. ..======|>PCIe CLK |
>> '------------' || || '-------------'
>> || ||
>> ____________ || ||
>> | 9FGV0441 | || ||
>> | | || ||
>> | CLK DIF0<|======'' ||
>> | CLK DIF1<|==========''
>> | CLK DIF2<|
>> | CLK DIF3<|
>> '------------'
next prev parent reply other threads:[~2025-05-12 20:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 14:45 [PATCH v2 0/4] arm64: dts: renesas: r8a779g3: Add Retronix R-Car V4H Sparrow Hawk board support Marek Vasut
2025-04-06 14:45 ` [PATCH v2 1/4] dt-bindings: PCI: rcar-gen4-pci-host: Document optional aux clock Marek Vasut
2025-04-10 20:48 ` Rob Herring
2025-04-13 9:28 ` Marek Vasut
2025-04-23 9:38 ` Geert Uytterhoeven
2025-05-25 13:33 ` Marek Vasut
2025-05-09 19:37 ` Manivannan Sadhasivam
2025-05-12 20:42 ` Marek Vasut [this message]
2025-05-15 11:57 ` Manivannan Sadhasivam
2025-05-19 15:04 ` Rob Herring
2025-05-19 17:30 ` Manivannan Sadhasivam
2025-05-25 16:07 ` Marek Vasut
2025-04-06 14:45 ` [PATCH v2 2/4] dt-bindings: vendor-prefixes: Add Retronix Technology Inc Marek Vasut
2025-04-06 14:45 ` [PATCH v2 3/4] dt-bindings: soc: renesas: Document Retronix R-Car V4H Sparrow Hawk board support Marek Vasut
2025-04-06 14:45 ` [PATCH v2 4/4] arm64: dts: renesas: r8a779g3: Add " Marek Vasut
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=84cc6341-a2c1-4e3c-8c9e-2bc6589c52a6@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=a-bhatia1@ti.com \
--cc=bhelgaas@google.com \
--cc=bigfoot@classfun.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.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-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=magnus.damm@gmail.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=neil.armstrong@linaro.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=rafal@milecki.pl \
--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;
as well as URLs for NNTP newsgroup(s).