From: Bjorn Helgaas <helgaas@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Christian Gmeiner <christian.gmeiner@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Dominic Rath <rath@ibv-augsburg.de>,
krzysztof.kozlowski+dt@linaro.org, tjoseph@cadence.com,
bhelgaas@google.com, lpieralisi@kernel.org, nm@ti.com,
vigneshr@ti.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
bahle@ibv-augsburg.de
Subject: Re: [PATCH v2 1/3] dt-bindings: phy: cadence-torrent: Add latency properties
Date: Wed, 10 May 2023 16:12:08 -0500 [thread overview]
Message-ID: <ZFwIqBRj8in1CaGB@bhelgaas> (raw)
In-Reply-To: <6a36a4ad-6d46-4e4e-1724-ed27513a72ef@linaro.org>
On Wed, May 10, 2023 at 09:08:39AM +0200, Krzysztof Kozlowski wrote:
> On 09/05/2023 23:57, Bjorn Helgaas wrote:
> > On Tue, May 09, 2023 at 05:31:19PM +0200, Christian Gmeiner wrote:
> >>> On Thu, Apr 27, 2023 at 07:50:30AM +0200, Dominic Rath wrote:
> >>>> From: Alexander Bahle <bahle@ibv-augsburg.de>
> >>>>
> >>>> Add "tx-phy-latency-ps" and "rx-phy-latency-ps" DT bindings for
> >>>> setting the PCIe PHY latencies.
> >>>> The properties expect a list of uint32 PHY latencies in picoseconds for
> >>>> every supported speed starting at PCIe Gen1, e.g.:
> >>>>
> >>>> tx-phy-latency-ps = <100000 200000>; /* Gen1: 100ns, Gen2: 200ns */
> >>>> rx-phy-latency-ps = <150000 250000>; /* Gen1: 150ns, Gen2: 250ns */
> >>>
> >>> Are these things that could/should be described in a more generic
> >>> place? They don't look necessarily Cadence-specific.
> >>
> >> As there is currently no generic binding, would you like to see a new
> >> yaml binding
> >> added (Documentation/devicetree/bindings/phy/phy.yaml) that contains just the
> >> two phy properties?
> >
> > The whole thing is more a question for Rob.
>
> For which you might wait a bit currently.
>
> If the question is only about location of the properties - device schema
> or something generic - then for now you can keep it here. Moving to
> generic schema is always easy later.
>
> Better to have proper names for properties.
Good point. The current names seem fine to me since the names
themselves aren't Cadence-specific.
Bjorn
next prev parent reply other threads:[~2023-05-10 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230427055032.85015-1-rath@ibv-augsburg.de>
2023-04-27 5:50 ` [PATCH v2 2/3] PCI: cadence: Use DT bindings to set PHY latencies Dominic Rath
2023-05-04 11:33 ` Verma, Achal
2023-05-30 8:20 ` Christian Gmeiner
2023-04-27 5:50 ` [PATCH v2 3/3] arm64: dts: ti: k3-am64: Add PCIe PHY latency DT binding Dominic Rath
2023-05-09 15:27 ` Christian Gmeiner
[not found] ` <20230427055032.85015-2-rath@ibv-augsburg.de>
2023-04-27 18:30 ` [PATCH v2 1/3] dt-bindings: phy: cadence-torrent: Add latency properties Bjorn Helgaas
2023-05-09 15:31 ` Christian Gmeiner
2023-05-09 21:57 ` Bjorn Helgaas
2023-05-10 7:08 ` Krzysztof Kozlowski
2023-05-10 21:12 ` Bjorn Helgaas [this message]
2023-05-30 8:19 ` Christian Gmeiner
2023-05-30 8:21 ` [PATCH v2 0/3] Cadence PCIe PHY latency for PTM Christian Gmeiner
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=ZFwIqBRj8in1CaGB@bhelgaas \
--to=helgaas@kernel.org \
--cc=bahle@ibv-augsburg.de \
--cc=bhelgaas@google.com \
--cc=christian.gmeiner@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=nm@ti.com \
--cc=rath@ibv-augsburg.de \
--cc=robh+dt@kernel.org \
--cc=tjoseph@cadence.com \
--cc=vigneshr@ti.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