From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "mary@mary.zone" <mary@mary.zone>,
"manisadhasivam.linux@gmail.com" <manisadhasivam.linux@gmail.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chu.stanley@gmail.com" <chu.stanley@gmail.com>,
"James.Bottomley@hansenpartnership.com"
<James.Bottomley@hansenpartnership.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH 1/1] scsi: ufs-mediatek: Add UFSHCD_QUIRK_BROKEN_LSDBS_CAP
Date: Tue, 20 Aug 2024 05:56:54 +0000 [thread overview]
Message-ID: <59503540293f6d640809e24b43ea5102b3119853.camel@mediatek.com> (raw)
In-Reply-To: <ZsOJKMg8xlpdgoi5@kuroko.kudu-justice.ts.net>
On Mon, 2024-08-19 at 20:17 +0200, Mary Guillemard wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> On Mon, Aug 19, 2024 at 05:38:52PM +0530, Manivannan Sadhasivam
> wrote:
> > On Mon, Aug 19, 2024 at 12:24:42AM +0200, Mary Guillemard wrote:
> > > MT8183 supports UFSHCI 2.1 spec, but report a bogus value of 1 in
> the
> > > reserved part for the Legacy Single Doorbell Support (LSDBS)
> capability.
> > >
> >
> > Wow... I never thought that this quirk will be used outside of Qcom
> SoCs...
> >
>
> Yeah I found that by trial and error some weeks ago and noticed your
> serie while looking to upstream this change, quite funny to see other
> vendors having the same quirk here.
>
> > > This set UFSHCD_QUIRK_BROKEN_LSDBS_CAP when MCQ support is
> explicitly
> > > disabled, allowing the device to be properly registered.
> > >
> > > Signed-off-by: Mary Guillemard <mary@mary.zone>
> > > ---
> > > drivers/ufs/host/ufs-mediatek.c | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/drivers/ufs/host/ufs-mediatek.c
> b/drivers/ufs/host/ufs-mediatek.c
> > > index 02c9064284e1..9a5919434c4e 100644
> > > --- a/drivers/ufs/host/ufs-mediatek.c
> > > +++ b/drivers/ufs/host/ufs-mediatek.c
> > > @@ -1026,6 +1026,9 @@ static int ufs_mtk_init(struct ufs_hba
> *hba)
> > > if (host->caps & UFS_MTK_CAP_DISABLE_AH8)
> > > hba->caps |= UFSHCD_CAP_HIBERN8_WITH_CLK_GATING;
> > >
> > > +if (host->caps & UFS_MTK_CAP_DISABLE_MCQ)
> >
> > How can this be the deciding factor? You said above that the issue
> is with
> > MT8183 SoC. So why not just use the quirk only for that platform?
> >
> > - Mani
> >
>
> So my current assumption is that it also affect other Mediatek SoCs
> that are also based on UFS 2.1 spec but I cannot check this.
>
> Instead, we know that if MCQ isn't supported, we must fallback to
> LSDB
> as there is no other ways to drive the device.
>
> UFS_MTK_CAP_DISABLE_MCQ (mediatek,ufs-disable-mcq) being unused
> upstream,
> I think that's an acceptable fix.
>
> Another way to handle this would be to add a new dt property and add
> it
> to ufs_mtk_host_caps but I feel that my approach should be enough.
>
Hi Mary,
Yes, the MT8395 indeed requires the LSDBS flag,
but not every MediaTek legacy chip does.
So setting the LSDBS flag here is appropriate.
Thanks.
Peter
> > > +hba->quirks |= UFSHCD_QUIRK_BROKEN_LSDBS_CAP;
> > > +
> > > ufs_mtk_init_clocks(hba);
> > >
> > > /*
> > > --
> > > 2.46.0
> > >
> > >
> >
> > --
> > மணிவண்ணன் சதாசிவம்
>
> - Mary
>
next prev parent reply other threads:[~2024-08-20 5:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 22:24 [PATCH 0/1] ufs: mediatek: Fix probe failure on MT8395 SoC Mary Guillemard
2024-08-18 22:24 ` [PATCH 1/1] scsi: ufs-mediatek: Add UFSHCD_QUIRK_BROKEN_LSDBS_CAP Mary Guillemard
2024-08-19 12:08 ` Manivannan Sadhasivam
2024-08-19 18:17 ` Mary Guillemard
2024-08-20 5:56 ` Peter Wang (王信友) [this message]
2024-08-20 6:09 ` Manivannan Sadhasivam
2024-08-20 21:50 ` Bart Van Assche
2024-08-21 21:32 ` Mary Guillemard
2024-08-22 6:34 ` Manivannan Sadhasivam
2024-08-20 5:58 ` Peter Wang (王信友)
2024-08-29 2:50 ` Martin K. Petersen
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=59503540293f6d640809e24b43ea5102b3119853.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chu.stanley@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manisadhasivam.linux@gmail.com \
--cc=martin.petersen@oracle.com \
--cc=mary@mary.zone \
--cc=matthias.bgg@gmail.com \
/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
all inboxes | Powered by JetHome®