From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: "davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "kishon@ti.com" <kishon@ti.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Leo Li <leoyang.li@nxp.com>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH net-next 0/8] dpaa2-mac: add support for changing the protocol at runtime
Date: Wed, 9 Mar 2022 16:38:10 +0000 [thread overview]
Message-ID: <20220309163809.5hzapz7s2b44iw2l@skbuf> (raw)
In-Reply-To: <20220309143751.3362678-1-ioana.ciornei@nxp.com>
On Wed, Mar 09, 2022 at 04:37:43PM +0200, Ioana Ciornei wrote:
> This patch set adds support for changing the Ethernet protocol at
> runtime on Layerscape SoCs which have the Lynx 28G SerDes block.
>
> The first two patches add a new generic PHY driver for the Lynx 28G and
> the bindings file associated. The driver reads the PLL configuration at
> probe time (the frequency provided to the lanes) and determines what
> protocols can be supported.
> Based on this the driver can deny or approve a request from the
> dpaa2-mac to setup a new protocol.
>
> The next 2 patches add some MC APIs for inquiring what is the running
> version of firmware and setting up a new protocol on the MAC.
>
> Moving along, we extract the code for setting up the supported
> interfaces on a MAC on a different function since in the next patches
> will update the logic.
>
> In the next patch, the dpaa2-mac is updated so that it retrieves the
> SerDes PHY based on the OF node and in case of a major reconfig, call
> the PHY driver to set up the new protocol on the associated lane and the
> MC firmware to reconfigure the MAC side of things.
>
> Finally, the LX2160A dtsi is annotated with the SerDes PHY nodes for the
> 1st SerDes block. Beside this, the LX2160A Clearfog dtsi is annotated
> with the 'phys' property for the exposed SFP cages.
>
> Ioana Ciornei (8):
> phy: add support for the Layerscape SerDes 28G
> dt-bindings: phy: add the "fsl,lynx-28g" compatible
> dpaa2-mac: add the MC API for retrieving the version
> dpaa2-mac: add the MC API for reconfiguring the protocol
> dpaa2-mac: retrieve API version and detect features
> dpaa2-mac: move setting up supported_interfaces into a function
> dpaa2-mac: configure the SerDes phy on a protocol change
> arch: arm64: dts: lx2160a: describe the SerDes block #1
I forgot the MODULE_LICENSE for the generic PHY driver.
I'll send a v2 so that we can actually see if the build step is clean.
Ioana
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2022-03-09 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 14:37 [PATCH net-next 0/8] dpaa2-mac: add support for changing the protocol at runtime Ioana Ciornei
2022-03-09 14:37 ` [PATCH net-next 1/8] phy: add support for the Layerscape SerDes 28G Ioana Ciornei
2022-03-09 14:37 ` [PATCH net-next 2/8] dt-bindings: phy: add the "fsl, lynx-28g" compatible Ioana Ciornei
2022-03-09 14:37 ` [PATCH net-next 3/8] dpaa2-mac: add the MC API for retrieving the version Ioana Ciornei
2022-03-09 14:37 ` [PATCH net-next 4/8] dpaa2-mac: add the MC API for reconfiguring the protocol Ioana Ciornei
2022-03-09 14:37 ` [PATCH net-next 5/8] dpaa2-mac: retrieve API version and detect features Ioana Ciornei
2022-03-09 14:37 ` [PATCH net-next 6/8] dpaa2-mac: move setting up supported_interfaces into a function Ioana Ciornei
2022-03-09 14:37 ` [PATCH net-next 7/8] dpaa2-mac: configure the SerDes phy on a protocol change Ioana Ciornei
2022-03-09 14:37 ` [PATCH net-next 8/8] arch: arm64: dts: lx2160a: describe the SerDes block #1 Ioana Ciornei
2022-03-09 16:38 ` Ioana Ciornei [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220309163809.5hzapz7s2b44iw2l@skbuf \
--to=ioana.ciornei@nxp.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=kuba@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-phy@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox