[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d2329736-9697-4d73-b2d2-2b83c129221d@ti.com>
Date: Mon, 5 Aug 2024 15:29:28 +0530
From: Siddharth Vadapalli <s-vadapalli@...com>
To: Vinod Koul <vkoul@...nel.org>
CC: Siddharth Vadapalli <s-vadapalli@...com>, <kishon@...nel.org>,
<p.zabel@...gutronix.de>, <sjakhade@...ence.com>, <rogerq@...nel.org>,
<thomas.richard@...tlin.com>, <theo.lebrun@...tlin.com>,
<robh@...nel.org>, <linux-phy@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<srk@...com>
Subject: Re: [PATCH v3] phy: cadence-torrent: add support for three or more
links using 2 protocols
On Sun, Aug 04, 2024 at 10:39:59PM +0530, Vinod Koul wrote:
> On 16-07-24, 15:54, Siddharth Vadapalli wrote:
> > The Torrent SERDES can support at most two different protocols (PHY types).
> > This only mandates that the device-tree sub-nodes used to represent the
> > configuration should describe links with at-most two different protocols.
> >
> > The existing implementation however imposes an artificial constraint that
> > allows only two links (device-tree sub-nodes). As long as at-most two
> > protocols are chosen, using more than two links to describe them in an
> > alternating configuration is still a valid configuration of the Torrent
> > SERDES.
> >
> > A 3-Link 2-Protocol configuration of the 4-Lane SERDES can be:
> > Lane 0 => Protocol 1 => Link 1
> > Lane 1 => Protocol 1 => Link 1
> > Lane 2 => Protocol 2 => Link 2
> > Lane 3 => Protocol 1 => Link 3
> >
> > A 4-Link 2-Protocol configuration of the 4-Lane SERDES can be:
> > Lane 0 => Protocol 1 => Link 1
> > Lane 1 => Protocol 2 => Link 2
> > Lane 2 => Protocol 1 => Link 3
> > Lane 3 => Protocol 2 => Link 4
> >
> > Signed-off-by: Siddharth Vadapalli <s-vadapalli@...com>
> > ---
> >
> > Hello,
> >
> > This patch is based on linux-next tagged next-20240715.
>
> Sorry this does not apply for me on phy/next, can you rebase..?
Thank you for pointing it out. I have rebased this patch on linux-next
tagged next-20240805 and have posted the v4 patch at:
https://lore.kernel.org/r/20240805092607.143869-1-s-vadapalli@ti.com/
Regards,
Siddharth.
Powered by blists - more mailing lists