Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: r3p/gD8jDs0V9OQjJbiEaAgfVUonEWenthRCyR5Ha5mmECaVwqWrfUhSdRRvlPYfDzTIuH8MgP
 CzuoDAV82yG4t4OM1jj8YFD6KRbbFvppx2kCwsDK/hq+ur1dOVm8xvZYSluyBuZfmkz/KutKtL
 lnPtTXHF6SMcf2sA/fAT56ScaW9uZvK/d3xi0FoWRIztFdm2TOTFpYEF38Z7ck9Q5zVx/gEPlS
 kT+BBdmwOK/YY2PJB1DKb4jMmkZe8C0QVW3zKfbq8XBkXLgLMTDlRwscuDQ+BamMDiJfqXVSs6
 0gz/Y22xDo749DcDdP2uhLAk
Date:   Thu, 14 Oct 2021 17:20:16 +0200
From:   Horatiu Vultur <horatiu.vultur@microchip.com>
To:     Philipp Zabel <p.zabel@pengutronix.de>
CC:     <robh+dt@kernel.org>, <andrew@lunn.ch>,
        <lars.povlsen@microchip.com>, <Steen.Hegelund@microchip.com>,
        <UNGLinuxDriver@microchip.com>, <devicetree@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: reset: Add lan966x support
Message-ID: <20211014152016.wuwaesswc5iiil42@soft-dev3-1.localhost>
References: <20211013073807.2282230-1-horatiu.vultur@microchip.com>
 <20211013073807.2282230-2-horatiu.vultur@microchip.com>
 <838af7b574968fc55d517a3becede5fa106ed896.camel@pengutronix.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <838af7b574968fc55d517a3becede5fa106ed896.camel@pengutronix.de>
Precedence: bulk

Hi Philipp,

The 10/14/2021 13:55, Philipp Zabel wrote:
> 
> On Wed, 2021-10-13 at 09:38 +0200, Horatiu Vultur wrote:
> > This adds support for lan966x.
> >
> > Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> > ---
> >  .../devicetree/bindings/reset/microchip,rst.yaml   | 14 +++++++++++++-
> >  1 file changed, 13 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/reset/microchip,rst.yaml b/Documentation/devicetree/bindings/reset/microchip,rst.yaml
> > index 370579aeeca1..fb170ed2c57a 100644
> > --- a/Documentation/devicetree/bindings/reset/microchip,rst.yaml
> > +++ b/Documentation/devicetree/bindings/reset/microchip,rst.yaml
> > @@ -20,7 +20,11 @@ properties:
> >      pattern: "^reset-controller@[0-9a-f]+$"
> >
> >    compatible:
> > -    const: microchip,sparx5-switch-reset
> > +    oneOf:
> > +      - items:
> > +          - const: microchip,sparx5-switch-reset
> > +      - items:
> > +          - const: microchip,lan966x-switch-reset
> >
> >    reg:
> >      items:
> > @@ -37,6 +41,14 @@ properties:
> >      $ref: "/schemas/types.yaml#/definitions/phandle"
> >      description: syscon used to access CPU reset
> >
> > +  cuphy-syscon:
> > +    $ref: "/schemas/types.yaml#/definitions/phandle"
> > +    description: syscon used to access CuPHY
> 
> Can this be used on sparx5?

No, because the sparx5 doesn't have any internal PHYs that need to
be released of the reset.

> Is it optional on lan966x?

No, it is required on lan966x. I will update the binding to show this.

> 
> > +  phy-reset-gpios:
> > +    description: used for release of reset of the external PHY
> > +    maxItems: 1
> > +
> >  required:
> >    - compatible
> >    - reg
> 
> I'd like somebody to reassure me that putting the CuPHY reset and
> external PHY GPIO reset in the reset controller is the right thing to
> do.
> 
> It looks fine to me, but I'm not sure if these should rather be in
> separate phy nodes that are referenced from the switch.
> 
> regards
> Philipp

-- 
/Horatiu