From: Jakub Kicinski <kuba@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v3 0/3] Add reset deassertion for Aspeed MDIO
Date: Mon, 28 Mar 2022 21:45:22 -0700 [thread overview]
Message-ID: <20220328214522.7cfdff1e@kernel.org> (raw)
In-Reply-To: <20220325041451.894-1-dylan_hung@aspeedtech.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Dylan Hung <dylan_hung@aspeedtech.com>
Cc: <robh+dt@kernel.org>, <joel@jms.id.au>, <andrew@aj.id.au>,
<andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <pabeni@redhat.com>,
<p.zabel@pengutronix.de>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <BMC-SW@aspeedtech.com>
Subject: Re: [PATCH v3 0/3] Add reset deassertion for Aspeed MDIO
Date: Mon, 28 Mar 2022 21:45:22 -0700 [thread overview]
Message-ID: <20220328214522.7cfdff1e@kernel.org> (raw)
In-Reply-To: <20220325041451.894-1-dylan_hung@aspeedtech.com>
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.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Dylan Hung <dylan_hung@aspeedtech.com>
Cc: <robh+dt@kernel.org>, <joel@jms.id.au>, <andrew@aj.id.au>,
<andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <pabeni@redhat.com>,
<p.zabel@pengutronix.de>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <BMC-SW@aspeedtech.com>
Subject: Re: [PATCH v3 0/3] Add reset deassertion for Aspeed MDIO
Date: Mon, 28 Mar 2022 21:45:22 -0700 [thread overview]
Message-ID: <20220328214522.7cfdff1e@kernel.org> (raw)
In-Reply-To: <20220325041451.894-1-dylan_hung@aspeedtech.com>
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.
next prev parent reply other threads:[~2022-03-29 4:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 4:14 [PATCH v3 0/3] Add reset deassertion for Aspeed MDIO Dylan Hung
2022-03-25 4:14 ` Dylan Hung
2022-03-25 4:14 ` Dylan Hung
2022-03-25 4:14 ` [PATCH v3 1/3] dt-bindings: net: add reset property for aspeed, ast2600-mdio binding Dylan Hung
2022-03-25 4:14 ` Dylan Hung
2022-03-25 4:14 ` Dylan Hung
2022-03-25 12:19 ` Krzysztof Kozlowski
2022-03-25 12:19 ` Krzysztof Kozlowski
2022-03-25 12:19 ` Krzysztof Kozlowski
2022-03-25 4:14 ` [PATCH v3 2/3] net: mdio: add reset control for Aspeed MDIO Dylan Hung
2022-03-25 4:14 ` Dylan Hung
2022-03-25 4:14 ` Dylan Hung
2022-03-31 7:12 ` Russell King
2022-03-31 7:12 ` Russell King (Oracle)
2022-03-31 7:12 ` Russell King (Oracle)
2022-04-07 6:29 ` Dylan Hung
2022-04-07 6:29 ` Dylan Hung
2022-04-07 6:29 ` Dylan Hung
2022-03-25 4:14 ` [PATCH v3 3/3] ARM: dts: aspeed: add reset properties into MDIO nodes Dylan Hung
2022-03-25 4:14 ` Dylan Hung
2022-03-25 4:14 ` Dylan Hung
2022-03-29 4:45 ` Jakub Kicinski [this message]
2022-03-29 4:45 ` [PATCH v3 0/3] Add reset deassertion for Aspeed MDIO Jakub Kicinski
2022-03-29 4:45 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2022-04-07 7:57 Dylan Hung
2022-04-07 7:57 ` Dylan Hung
2022-04-07 7:57 ` Dylan Hung
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=20220328214522.7cfdff1e@kernel.org \
--to=kuba@kernel.org \
--cc=linux-aspeed@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.