[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<BN9PR18MB4251FD4F9BD9915477823316DB4D2@BN9PR18MB4251.namprd18.prod.outlook.com>
Date: Thu, 15 Feb 2024 17:01:41 +0000
From: Elad Nachman <enachman@...vell.com>
To: Ulf Hansson <ulf.hansson@...aro.org>
CC: "huziji@...vell.com" <huziji@...vell.com>,
"adrian.hunter@...el.com"
<adrian.hunter@...el.com>,
"linux-mmc@...r.kernel.org"
<linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: RE: [EXT] Re: [PATCH v2 0/2] Fix PHY init timeout issues
> -----Original Message-----
> From: Ulf Hansson <ulf.hansson@...aro.org>
> Sent: Thursday, February 15, 2024 6:51 PM
> To: Elad Nachman <enachman@...vell.com>
> Cc: huziji@...vell.com; adrian.hunter@...el.com; linux-
> mmc@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: [EXT] Re: [PATCH v2 0/2] Fix PHY init timeout issues
>
> External Email
>
> ----------------------------------------------------------------------
> On Thu, 15 Feb 2024 at 17:16, Elad Nachman <enachman@...vell.com>
> wrote:
> >
> > From: Elad Nachman <enachman@...vell.com>
> >
> > Fix PHY init timeout issues:
> >
> > 1. Clock Stability issue causing PHY timeout
> >
> > 2. Timeout taking longer than needed on AC5X.
> > Solve by constantly testing the PHY init bit
> > until it toggles, but up to 100X timeout factor.
> >
> > v2:
> > 1) convert polling loop to read_poll_timeout()
> > for both patches.
> >
> > Elad Nachman (2):
> > mmc: xenon: fix PHY init clock stability
> > mmc: xenon: add timeout for PHY init complete
> >
> > drivers/mmc/host/sdhci-xenon-phy.c | 48
> > ++++++++++++++++++++++++------
> > 1 file changed, 39 insertions(+), 9 deletions(-)
> >
>
> The series looks good to me. Although, I assume we should tag this for stable
> kernels too and possibly add a fixes tag?
No problem.
>
> Moreover, it would be nice to get an ack from Hu Ziji.
He does not longer work with Marvell, so this email is invalid, I tried also to send an e-mail manually as well and got:
huziji@...vell.com
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
Could not locate him via google search either.
>
> Kind regards
> Uffe
Powered by blists - more mailing lists