[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <002e01d894da$e2021bc0$a6065340$@samsung.com>
Date: Mon, 11 Jul 2022 13:01:22 +0900
From: "Kiwoong Kim" <kwmad.kim@...sung.com>
To: "'Bart Van Assche'" <bvanassche@....org>,
<linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<alim.akhtar@...sung.com>, <avri.altman@....com>,
<jejb@...ux.ibm.com>, <martin.petersen@...cle.com>,
<beanhuo@...ron.com>, <adrian.hunter@...el.com>,
<sc.suh@...sung.com>, <hy50.seo@...sung.com>,
<sh425.lee@...sung.com>, <bhoon95.kim@...sung.com>
Subject: RE: [RESEND PATCH v3] scsi: ufs: exclude UECxx from SFR dump list
> >> Is this behavior specific to the Exynos controller or is this
> >> behavior required by the UFSHCI specification? In the latter case,
> >> can you tell me where to find this requirement in the UFSHCI
> >> specification? I haven't found that requirement yet. Maybe this means
> that I overlooked something?
> >
> > This is needed because those SFRs are ROC (Read to Clear) type.
> > That means reading causes clearing contexts.
> > The SFRs are mainly read in interrupt context but the reading is also
> done in dump.
> The above repeats what I can find in the patch description but doesn't
> answer my question :-(
>
> Bart.
It's definitely not Exynos specific
because the fact that those SFRs are ROC type is written in UFSHCI.
I don't know more things to explain why this patch is needed.
You just want to know whether any additional descriptions about ROC is written ?
Thanks.
Kiwoong Kim
Powered by blists - more mailing lists