From: Andrew Lunn <andrew@lunn.ch>
To: Parthiban.Veerasooran@microchip.com
Cc: hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ramon.nordin.rodriguez@ferroamp.se, Horatiu.Vultur@microchip.com,
Woojung.Huh@microchip.com, Nicolas.Ferre@microchip.com,
Thorsten.Kummermehr@microchip.com
Subject: Re: [PATCH net-next v2 4/6] net: phy: microchip_t1s: fix reset complete status handling
Date: Wed, 24 May 2023 14:03:42 +0200 [thread overview]
Message-ID: <e0ea8a35-3ea6-43a5-bb5b-a914f86cd492@lunn.ch> (raw)
In-Reply-To: <2523bd58-2b2c-723f-6261-aa44ca92e00a@microchip.com>
> As per the datasheet DS-LAN8670-1-2-60001573C.pdf, during the Power ON
> Reset(POR)/Hard Reset/Soft Reset, the Reset Complete status bit in the
> STS2 register to be checked before proceeding for the initial
register _has_ to be checked before proceeding _to_ the initial
> configuration. Reading STS2 register will also clear the Reset Complete
> interrupt which is non-maskable.
Otherwise, this is O.K.
Andrew
next prev parent reply other threads:[~2023-05-24 12:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 11:33 [PATCH net-next v2 0/6] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Parthiban Veerasooran
2023-05-22 11:33 ` [PATCH net-next v2 1/6] net: phy: microchip_t1s: modify driver description to be more generic Parthiban Veerasooran
2023-05-22 12:27 ` Andrew Lunn
2023-05-22 11:33 ` [PATCH net-next v2 2/6] net: phy: microchip_t1s: replace read-modify-write code with phy_modify_mmd Parthiban Veerasooran
2023-05-22 12:31 ` Andrew Lunn
2023-05-23 6:15 ` Parthiban.Veerasooran
2023-05-22 11:33 ` [PATCH net-next v2 3/6] net: phy: microchip_t1s: update LAN867x PHY supported revision number Parthiban Veerasooran
2023-05-22 12:38 ` Andrew Lunn
2023-05-23 6:25 ` Parthiban.Veerasooran
2023-05-22 11:33 ` [PATCH net-next v2 4/6] net: phy: microchip_t1s: fix reset complete status handling Parthiban Veerasooran
2023-05-22 12:43 ` Andrew Lunn
2023-05-23 5:30 ` Parthiban.Veerasooran
2023-05-23 12:23 ` Andrew Lunn
2023-05-24 7:24 ` Parthiban.Veerasooran
2023-05-24 7:31 ` Parthiban.Veerasooran
2023-05-24 12:03 ` Andrew Lunn [this message]
2023-05-24 13:21 ` Parthiban.Veerasooran
2023-05-22 11:33 ` [PATCH net-next v2 5/6] net: phy: microchip_t1s: remove unnecessary interrupts disabling code Parthiban Veerasooran
2023-05-22 12:45 ` Andrew Lunn
2023-05-22 11:33 ` [PATCH net-next v2 6/6] net: phy: microchip_t1s: add support for Microchip LAN865x Rev.B0 PHYs Parthiban Veerasooran
2023-05-22 12:56 ` Andrew Lunn
2023-05-23 6:13 ` Parthiban.Veerasooran
2023-05-23 12:29 ` Andrew Lunn
2023-05-24 7:25 ` Parthiban.Veerasooran
2023-05-22 15:02 ` Simon Horman
2023-05-23 5:33 ` Parthiban.Veerasooran
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=e0ea8a35-3ea6-43a5-bb5b-a914f86cd492@lunn.ch \
--to=andrew@lunn.ch \
--cc=Horatiu.Vultur@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=Thorsten.Kummermehr@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ramon.nordin.rodriguez@ferroamp.se \
/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;
as well as URLs for NNTP newsgroup(s).