From: Bart Van Assche <bvanassche@acm.org>
To: Kiwoong Kim <kwmad.kim@samsung.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
alim.akhtar@samsung.com, avri.altman@wdc.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, beanhuo@micron.com,
adrian.hunter@intel.com, sc.suh@samsung.com,
hy50.seo@samsung.com, sh425.lee@samsung.com,
bhoon95.kim@samsung.com
Subject: Re: [RESEND PATCH v3] scsi: ufs: exclude UECxx from SFR dump list
Date: Sun, 10 Jul 2022 20:41:08 -0700 [thread overview]
Message-ID: <213634d7-a796-8509-9612-56fe7c61ef01@acm.org> (raw)
In-Reply-To: <000001d894ca$45da51f0$d18ef5d0$@samsung.com>
On 7/10/22 19:02, Kiwoong Kim wrote:
>> 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.
next prev parent reply other threads:[~2022-07-11 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220315095716epcas2p2ec52c66863b71180a6c2c45856058683@epcas2p2.samsung.com>
2022-03-15 9:56 ` Kiwoong Kim
2022-07-08 21:28 ` Bart Van Assche
2022-07-11 1:59 ` Kiwoong Kim
2022-07-11 2:02 ` Kiwoong Kim
2022-07-11 3:41 ` Bart Van Assche [this message]
2022-07-11 4:01 ` Kiwoong Kim
2022-07-11 21:04 ` Bart Van Assche
[not found] <CGME20220331012539epcas2p180d804d9562b6e0fb968ffd181d64605@epcas2p1.samsung.com>
2022-03-31 1:24 ` Kiwoong Kim
2022-04-26 12:32 ` Martin K. Petersen
2022-05-03 0:51 ` 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=213634d7-a796-8509-9612-56fe7c61ef01@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bhoon95.kim@samsung.com \
--cc=hy50.seo@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sc.suh@samsung.com \
--cc=sh425.lee@samsung.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®