[PATCH v3 0/3] Add reset deassertion for Aspeed MDIO

Dylan Hung posted 3 patches 4 years, 2 months ago
There is a newer version of this series
.../bindings/net/aspeed,ast2600-mdio.yaml         |  5 +++++
arch/arm/boot/dts/aspeed-g6.dtsi                  |  4 ++++
drivers/net/mdio/mdio-aspeed.c                    | 15 ++++++++++++++-
3 files changed, 23 insertions(+), 1 deletion(-)
[PATCH v3 0/3] Add reset deassertion for Aspeed MDIO
Posted by Dylan Hung 4 years, 2 months ago
Add missing reset deassertion for Aspeed MDIO bus controller. The reset
is asserted by the hardware when power-on so the driver only needs to
deassert it. To be able to work with the old DT blobs, the reset is
optional since it may be deasserted by the bootloader or the previous
kernel.

V3:
- remove reset property from the required list of the device tree
  bindings
- remove "Cc: stable@vger.kernel.org" from the commit messages
- add more description in the commit message of the dt-binding

V2:
- add reset property in the device tree bindings
- add reset assertion in the error path and driver remove

Dylan Hung (3):
  dt-bindings: net: add reset property for aspeed, ast2600-mdio binding
  net: mdio: add reset control for Aspeed MDIO
  ARM: dts: aspeed: add reset properties into MDIO nodes

 .../bindings/net/aspeed,ast2600-mdio.yaml         |  5 +++++
 arch/arm/boot/dts/aspeed-g6.dtsi                  |  4 ++++
 drivers/net/mdio/mdio-aspeed.c                    | 15 ++++++++++++++-
 3 files changed, 23 insertions(+), 1 deletion(-)

-- 
2.25.1
Re: [PATCH v3 0/3] Add reset deassertion for Aspeed MDIO
Posted by Jakub Kicinski 4 years, 2 months ago
On Fri, 25 Mar 2022 12:14:48 +0800 Dylan Hung wrote:
> Add missing reset deassertion for Aspeed MDIO bus controller. The reset
> is asserted by the hardware when power-on so the driver only needs to
> deassert it. To be able to work with the old DT blobs, the reset is
> optional since it may be deasserted by the bootloader or the previous
> kernel.

# Form letter - net-next is closed

We have already sent the networking pull request for 5.18
and therefore net-next is closed for new drivers, features,
code refactoring and optimizations. We are currently accepting
bug fixes only.

Please repost when net-next reopens after 5.18-rc1 is cut, in ~1 week.

RFC patches sent for review only are obviously welcome at any time.