[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191031.142606.2018368283376596287.davem@davemloft.net>
Date: Thu, 31 Oct 2019 14:26:06 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ioana.ciornei@....com
Cc: netdev@...r.kernel.org, laurentiu.tudor@....com, andrew@...n.ch,
f.fainelli@...il.com, linux@...linux.org.uk
Subject: Re: [PATCH net-next v4 0/5] dpaa2-eth: add MAC/PHY support through
phylink
From: Ioana Ciornei <ioana.ciornei@....com>
Date: Thu, 31 Oct 2019 01:18:27 +0200
> The dpaa2-eth driver now has support for connecting to its associated PHY
> device found through standard OF bindings. The PHY interraction is handled
> by PHYLINK and even though, at the moment, only RGMII_* phy modes are
> supported by the driver, this is just the first step into adding the
> necessary changes to support the entire spectrum of capabilities.
>
> This comes after feedback on the initial DPAA2 MAC RFC submitted here:
> https://lwn.net/Articles/791182/
>
> The notable change is that now, the DPMAC is not a separate driver, and
> communication between the DPMAC and DPNI no longer happens through
> firmware. Rather, the DPMAC is now a set of API functions that other
> net_device drivers (DPNI, DPSW, etc) can use for PHY management.
>
> The change is incremental, because the DPAA2 architecture has many modes of
> connecting net devices in hardware loopback (for example DPNI to DPNI).
> Those operating modes do not have a DPMAC and phylink instance.
>
> The documentation patch provides a more complete view of the software
> architecture and the current implementation.
...
Series applied.
Powered by blists - more mailing lists