From: Amelie DELAUNAY <amelie.delaunay@foss.st.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 1/1] phy: stm32: fix st,slow-hs-slew-rate with st,decrease-hs-slew-rate
Date: Mon, 15 Nov 2021 11:25:40 +0100 [thread overview]
Message-ID: <d4e76549-4f27-6043-64c1-411261b8a5aa@foss.st.com> (raw)
In-Reply-To: <20211026154817.198937-1-amelie.delaunay@foss.st.com>
Hi,
Kind reminder.
Regards,
Amelie
On 10/26/21 5:48 PM, Amelie Delaunay wrote:
> st,decrease-hs-slew-rate is described in phy-stm32-usbphyc.yaml. Then
> fix the property name in driver.
>
> Fixes: 2f5e9f815a2f ("phy: stm32: add phy tuning support")
> Signed-off-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
> ---
> drivers/phy/st/phy-stm32-usbphyc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/phy/st/phy-stm32-usbphyc.c b/drivers/phy/st/phy-stm32-usbphyc.c
> index 7df6a63ad37b..e4f4a9be5132 100644
> --- a/drivers/phy/st/phy-stm32-usbphyc.c
> +++ b/drivers/phy/st/phy-stm32-usbphyc.c
> @@ -478,7 +478,7 @@ static void stm32_usbphyc_phy_tuning(struct stm32_usbphyc *usbphyc,
> if (!of_property_read_bool(np, "st,no-lsfs-fb-cap"))
> usbphyc_phy->tune |= LFSCAPEN;
>
> - if (of_property_read_bool(np, "st,slow-hs-slew-rate"))
> + if (of_property_read_bool(np, "st,decrease-hs-slew-rate"))
> usbphyc_phy->tune |= HSDRVSLEW;
>
> ret = of_property_read_u32(np, "st,tune-hs-dc-level", &val);
>
next prev parent reply other threads:[~2021-11-15 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 15:48 [PATCH 1/1] phy: stm32: fix st,slow-hs-slew-rate with st,decrease-hs-slew-rate Amelie Delaunay
2021-11-15 10:25 ` Amelie DELAUNAY [this message]
2021-11-16 9:58 ` Vinod Koul
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=d4e76549-4f27-6043-64c1-411261b8a5aa@foss.st.com \
--to=amelie.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@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 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).