From: Brian Masney <bmasney@redhat.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: en7523: reset PCIE HB on init for AN7581
Date: Wed, 8 Jul 2026 12:52:49 -0400 [thread overview]
Message-ID: <ak6AYe5ZZrzyf1UB@redhat.com> (raw)
In-Reply-To: <20260708084045.8380-1-ansuelsmth@gmail.com>
Hi Christian,
Thanks for the patch.
On Wed, Jul 08, 2026 at 10:40:44AM +0200, Christian Marangi wrote:
> It was reported that PCIE HB should be reset for AN7581 or some instability
> or link training issue will be present on warm boot scenario.
>
> Reset PCIE HB on clk HW init to handle warm boot problem with PCIe.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> drivers/clk/clk-en7523.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/clk/clk-en7523.c b/drivers/clk/clk-en7523.c
> index 1ab0e2eca5d3..c450d89bfa96 100644
> --- a/drivers/clk/clk-en7523.c
> +++ b/drivers/clk/clk-en7523.c
> @@ -57,6 +57,7 @@
>
> #define REG_RST_CTRL2 0x830
> #define REG_RST_CTRL1 0x834
> +#define REG_PCIE_HB_RST BIT(29)
> #define EN751221_REG_RST_DMT 0x84
> #define EN751221_REG_RST_USB 0xec
>
> @@ -853,6 +854,12 @@ static int en7581_clk_hw_init(struct platform_device *pdev,
> val = readl(base + REG_NP_SCU_PCIC);
> writel(val | 3, base + REG_NP_SCU_PCIC);
>
> + val = readl(base + REG_RST_CTRL1);
> + val |= REG_PCIE_HB_RST;
> + writel(val, base + REG_RST_CTRL1);
> + val &= ~REG_PCIE_HB_RST;
> + writel(val, base + REG_RST_CTRL1);
> +
Sashiko has a question about whether or not a delay or a flush is needed
between the writel() calls?
https://sashiko.dev/#/patchset/20260708084045.8380-1-ansuelsmth%40gmail.com
Brian
next prev parent reply other threads:[~2026-07-08 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 8:40 [PATCH] clk: en7523: reset PCIE HB on init for AN7581 Christian Marangi
2026-07-08 16:52 ` Brian Masney [this message]
2026-07-09 13:48 ` Christian Marangi
2026-07-09 14:24 ` Brian Masney
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=ak6AYe5ZZrzyf1UB@redhat.com \
--to=bmasney@redhat.com \
--cc=ansuelsmth@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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