[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YZ8aygJQoxie+Ddn@matsya>
Date: Thu, 25 Nov 2021 10:40:34 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Swapnil Kashinath Jakhade <sjakhade@...ence.com>
Cc: "kishon@...com" <kishon@...com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
"linux-phy@...ts.infradead.org" <linux-phy@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Milind Parab <mparab@...ence.com>,
"a-govindraju@...com" <a-govindraju@...com>
Subject: Re: [PATCH v3 13/15] phy: cadence: Sierra: Add PCIe + QSGMII PHY
multilink configuration
On 24-11-21, 07:33, Swapnil Kashinath Jakhade wrote:
> > so this is pcie->qsgmii ->ssc/external/internal ... ok
> >
> > > + [NO_SSC] =
> > &pcie_100_no_ssc_plllc_cmn_vals,
> > > + [EXTERNAL_SSC] =
> > &pcie_100_ext_ssc_plllc_cmn_vals,
> > > + [INTERNAL_SSC] =
> > &pcie_100_int_ssc_plllc_cmn_vals,
> > > + },
> > > },
> > > [TYPE_USB] = {
> > > [TYPE_NONE] = {
> > > [EXTERNAL_SSC] =
> > &usb_100_ext_ssc_cmn_vals,
> > > },
> > > },
> > > + [TYPE_QSGMII] = {
> > > + [TYPE_PCIE] = {
> >
> > now it is reverse! qsgmii -> pcie -> ... why?
> >
> > what is meant by pcie->qsgmii and qsgmii-> pcie?
> >
>
> Multi-protocol configuration is done in 2 phases, each for one protocol.
> e.g. for PCIe + QSGMII case,
> [TYPE_PCIE][TYPE_QSGMII] will configure common and lane registers for PCIe and
> [TYPE_QSGMII][TYPE_PCIE] will configure common and lane registers for QSGMII.
Then it should be always common + protocol or protocol + common, not
both please! Pls make an order and stick to it everywhere... If that is
not possible, I would like to understand why
--
~Vinod
Powered by blists - more mailing lists