[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221013191249.GA38183-robh@kernel.org>
Date: Thu, 13 Oct 2022 14:12:49 -0500
From: Rob Herring <robh@...nel.org>
To: Dominic Rath <dominic.rath@...-augsburg.de>
Cc: krzysztof.kozlowski+dt@...aro.org, tjoseph@...ence.com,
bhelgaas@...gle.com, lpieralisi@...nel.org, nm@...com,
vigneshr@...com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
Alexander Bahle <bahle@...-augsburg.de>,
Dominic Rath <rath@...-augsburg.de>
Subject: Re: [PATCH 1/3] dt-bindings: PCI: cdns: Add PHY latency properties
On Thu, Oct 13, 2022 at 08:26:47AM +0200, Dominic Rath wrote:
> From: Alexander Bahle <bahle@...-augsburg.de>
>
> Add "cdns,tx-phy-latency-ps" and "cdns,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.:
>
> max-link-speed = <2>;
> tx-phy-latency-ps = <100000 200000>; /* Gen1: 100ns, Gen2: 200ns */
> rx-phy-latency-ps = <150000 250000>; /* Gen1: 150ns, Gen2: 250ns */
These are a property of the PHY or PCI host? Sounds like PHY to me and
that should be in the PHY node. No reason the PCI driver can't go read
PHY node properties.
If PTM is a standard PCIe thing, then I don't think these should be
Cadence specific. IOW, drop 'cdns'.
Rob
Powered by blists - more mailing lists