[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000001d894ca$45da51f0$d18ef5d0$@samsung.com>
Date: Mon, 11 Jul 2022 11:02:28 +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?
>
> Thanks,
>
> Bart.
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.
Besides, I think reading them in dump is not proper because reading them is not just 'reading'
Thanks.
Kiwoong Kim
Powered by blists - more mailing lists