[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181017153913.GA13333@bogus>
Date: Wed, 17 Oct 2018 10:39:13 -0500
From: Rob Herring <robh@...nel.org>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: Tony Lindgren <tony@...mide.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Kishon Vijay Abraham I <kishon@...com>,
Sekhar Nori <nsekhar@...com>, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [RFC PATCH 02/11] dt-bindings: phy: add cpsw port interface mode
selection phy bindings
On Tue, Oct 09, 2018 at 03:10:34PM -0500, Grygorii Strashko wrote:
>
>
> On 10/09/2018 09:40 AM, Tony Lindgren wrote:
> > * Grygorii Strashko <grygorii.strashko@...com> [181008 23:54]:
> >> +Examples:
> >> + phy_gmii_sel: phy-gmii-sel {
> >> + compatible = "ti,am3352-phy-gmii-sel";
> >> + syscon-scm = <&scm_conf>;
> >> + #phy-cells = <2>;
> >> + };
> >
> > Now that this driver can live in it's proper place in the
>
> right
>
> > dts, you may want to consider just using standard reg
> > property for it instead of the syscon-scm. And also get
> > rid of the syscon reads and writes.
>
> Could you help clarify how to get syscon in this case?
> syscon_node_to_regmap(dev->parent->of_node)?
>
> Also, there are could be more then one gmii_sel registers in SCM in the future,
> so I hidden offsets in of_match data.
> As result, "reg" not needed at all now.
If there's a defined register range which doesn't overlap with other
things (other than the parent), then use reg whether you currently need
it or not.
Rob
Powered by blists - more mailing lists