From: Marek Vasut <marex@denx.de>
To: linux-arm-kernel@lists.infradead.org,
linux-stable <stable@vger.kernel.org>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
Patrice Chotard <patrice.chotard@st.com>,
Patrick Delaunay <patrick.delaunay@st.com>,
linux-stm32@st-md-mailman.stormreply.com,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] ARM: dts: stm32: Rework LAN8710Ai PHY reset on DHCOM SoM
Date: Mon, 28 Jun 2021 12:44:37 +0200 [thread overview]
Message-ID: <47597d13-e6ec-ccd2-c34b-eb65896cdd70@denx.de> (raw)
In-Reply-To: <20210408230001.310215-1-marex@denx.de>
On 4/9/21 1:00 AM, Marek Vasut wrote:
> The Microchip LAN8710Ai PHY requires XTAL1/CLKIN external clock to be
> enabled when the nRST is toggled according to datasheet Microchip
> LAN8710A/LAN8710Ai DS00002164B page 35 section 3.8.5.1 Hardware Reset:
[...]
> Fixes: 34e0c7847dcf ("ARM: dts: stm32: Add DH Electronics DHCOM STM32MP1 SoM and PDK2 board")
Adding stable to CC.
Patch is now part of Linux 5.13 as commit
1cebcf9932ab ("ARM: dts: stm32: Rework LAN8710Ai PHY reset on DHCOM SoM")
It would be nice to pick it into stable, since it fixes ethernet
stability issues on the device.
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: linux-arm-kernel@lists.infradead.org,
linux-stable <stable@vger.kernel.org>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
Patrice Chotard <patrice.chotard@st.com>,
Patrick Delaunay <patrick.delaunay@st.com>,
linux-stm32@st-md-mailman.stormreply.com,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] ARM: dts: stm32: Rework LAN8710Ai PHY reset on DHCOM SoM
Date: Mon, 28 Jun 2021 12:44:37 +0200 [thread overview]
Message-ID: <47597d13-e6ec-ccd2-c34b-eb65896cdd70@denx.de> (raw)
In-Reply-To: <20210408230001.310215-1-marex@denx.de>
On 4/9/21 1:00 AM, Marek Vasut wrote:
> The Microchip LAN8710Ai PHY requires XTAL1/CLKIN external clock to be
> enabled when the nRST is toggled according to datasheet Microchip
> LAN8710A/LAN8710Ai DS00002164B page 35 section 3.8.5.1 Hardware Reset:
[...]
> Fixes: 34e0c7847dcf ("ARM: dts: stm32: Add DH Electronics DHCOM STM32MP1 SoM and PDK2 board")
Adding stable to CC.
Patch is now part of Linux 5.13 as commit
1cebcf9932ab ("ARM: dts: stm32: Rework LAN8710Ai PHY reset on DHCOM SoM")
It would be nice to pick it into stable, since it fixes ethernet
stability issues on the device.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-28 10:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 23:00 [PATCH] ARM: dts: stm32: Rework LAN8710Ai PHY reset on DHCOM SoM Marek Vasut
2021-06-01 6:50 ` Alexandre TORGUE
2021-06-28 10:44 ` Marek Vasut [this message]
2021-06-28 10:44 ` Marek Vasut
2021-06-28 12:29 ` Greg KH
2021-06-28 12:29 ` Greg KH
2021-06-28 12:32 ` Marek Vasut
2021-06-28 12:32 ` Marek Vasut
2021-06-28 13:02 ` Greg KH
2021-06-28 13:02 ` Greg KH
2021-06-28 13:10 ` Marek Vasut
2021-06-28 13:10 ` Marek Vasut
2021-06-28 13:38 ` Greg KH
2021-06-28 13:38 ` Greg KH
2021-06-28 13:58 ` Marek Vasut
2021-06-28 13:58 ` Marek Vasut
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=47597d13-e6ec-ccd2-c34b-eb65896cdd70@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=patrice.chotard@st.com \
--cc=patrick.delaunay@st.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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 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.