[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181126193546.GP53235@atomide.com>
Date: Mon, 26 Nov 2018 11:35:46 -0800
From: Tony Lindgren <tony@...mide.com>
To: Roger Quadros <rogerq@...com>
Cc: robh+dt@...nel.org, bcousson@...libre.com, ssantosh@...nel.org,
ohad@...ery.com, bjorn.andersson@...aro.org, s-anna@...com,
nsekhar@...com, t-kristo@...com, nsaulnier@...com, jreeder@...com,
m-karicheri2@...com, woods.technical@...il.com,
linux-omap@...r.kernel.org, linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Grygorii Strashko <grygorii.strashko@...com>
Subject: Re: [PATCH 01/17] dt-bindings: remoteproc: Add TI PRUSS bindings
* Roger Quadros <rogerq@...com> [181126 07:48]:
> Not the PHY driver but the Ethernet driver. The PHY driver will be
> a davinci-MDIO device node (not yet in this series). I should probably
> add merge that with this series.
>
> The Ethernet device tree node will reference to these syscon nodes.
> e.g.
> pruss2_eth {
> compatible = "ti,am57-prueth";
> prus = <&pru2_0>, <&pru2_1>;
> firmware-name = "ti-pruss/am57xx-pru0-prueth-fw.elf",
> "ti-pruss/am57xx-pru1-prueth-fw.elf";
> sram = <&ocmcram1>;
> interrupt-parent = <&pruss2_intc>;
> --> mii-rt = <&pruss2_mii_rt>;
> --> iep = <&pruss2_iep>;
> }
>
> Do you see any issues with that?
Well maybe take a look at Grygorii's series adding proper
PHY driver for CPSW and see if it affects this too.
Regards,
Tony
Powered by blists - more mailing lists