[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190730.094436.855806617449032791.davem@davemloft.net>
Date: Tue, 30 Jul 2019 09:44:36 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: claudiu.manoil@....com
Cc: andrew@...n.ch, robh+dt@...nel.org, leoyang.li@....com,
alexandru.marginean@....com, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v4 0/4] enetc: Add mdio bus driver for the
PCIe MDIO endpoint
From: Claudiu Manoil <claudiu.manoil@....com>
Date: Tue, 30 Jul 2019 12:45:15 +0300
> First patch fixes a sparse issue and cleans up accessors to avoid
> casting to __iomem.
> Second patch just registers the PCIe endpoint device containing
> the MDIO registers as a standalone MDIO bus driver, to allow
> an alternative way to control the MDIO bus. The same code used
> by the ENETC ports (eth controllers) to manage MDIO via local
> registers applies and is reused.
>
> Bindings are provided for the new MDIO node, similarly to ENETC
> port nodes bindings.
>
> Last patch enables the ENETC port 1 and its RGMII PHY on the
> LS1028A QDS board, where the MDIO muxing configuration relies
> on the MDIO support provided in the first patch.
...
Series applied, thank you.
Powered by blists - more mailing lists