RE: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs

[Hongxing Zhu]

> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx>
> Sent: 2023年8月29日 15:50
> To: Hongxing Zhu <hongxing.zhu@xxxxxxx>; vkoul@xxxxxxxxxx;
> kishon@xxxxxxxxxx; robh+dt@xxxxxxxxxx; krzysztof.kozlowski+dt@xxxxxxxxxx;
> conor+dt@xxxxxxxxxx; shawnguo@xxxxxxxxxx; s.hauer@xxxxxxxxxxxxxx;
> festevam@xxxxxxxxx; l.stach@xxxxxxxxxxxxxx; a.fatoum@xxxxxxxxxxxxxx;
> u.kleine-koenig@xxxxxxxxxxxxxx
> Cc: linux-phy@xxxxxxxxxxxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx;
> linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> kernel@xxxxxxxxxxxxxx; dl-linux-imx <linux-imx@xxxxxxx>
> Subject: Re: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for
> different usecases of i.MX8QM PCIe PHYs
> 
> On 29/08/2023 08:45, Richard Zhu wrote:
> > Add binding for different usecases of i.MX8QM PCIe PHYs.
> >
> > Signed-off-by: Richard Zhu <hongxing.zhu@xxxxxxx>
> 
> This patch does not make sense on its own. Otherwise your previous patch has
> invalid path.
> 
> > ---
> >  include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
> >  1 file changed, 7 insertions(+)
> >
> > diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h
> > b/include/dt-bindings/phy/phy-imx8-pcie.h
> > index 8bbe2d6538d8..c8425c172118 100644
> > --- a/include/dt-bindings/phy/phy-imx8-pcie.h
> > +++ b/include/dt-bindings/phy/phy-imx8-pcie.h
> > @@ -11,4 +11,11 @@
> >  #define IMX8_PCIE_REFCLK_PAD_INPUT	1
> >  #define IMX8_PCIE_REFCLK_PAD_OUTPUT	2
> >
> > +/*
> > + * Different usecases of i.MX8QM HSIO(High Speed IO) module.
> > + */
> > +#define	PCIEAX2SATA		1
> > +#define	PCIEAX1PCIEBX1SATA	2
> > +#define	PCIEAX2PCIEBX1		3
> 
> Drop indentation. Look at the define few lines above and compare.
> 
> Anyway, this is neither explained nor looking like hardware property.
> Nothing in the commit msg or in doc here justifies these constants. Drop and use
> existing properties.
This property is used to specify the work mode of HSIO subsystem.
The HSIO and the PHYs contained in it would be initialized together refer to
 the different work modes. See the detailed discussion in #1 patch.

Best Regards
Richard Zhu
> 
> 
> Best regards,
> Krzysztof