mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Mon, 11 Jul 2022 14:04:51 -0700	[thread overview]
Message-ID: <58eec756-0932-cc43-8702-1c6e23d89ea4@acm.org> (raw)
In-Reply-To: <002e01d894da$e2021bc0$a6065340$@samsung.com>

On 7/10/22 21:01, Kiwoong Kim wrote:
> 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 ?

Hi Kiwoong,

I had overlooked the "ROC" text in the "Type" column in the UFSHCI 
specification. Thank you for having taken the time to answer my questions.

Bart.

  reply	other threads:[~2022-07-11 21:04 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
2022-07-11  4:01         ` Kiwoong Kim
2022-07-11 21:04           ` Bart Van Assche [this message]
     [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=58eec756-0932-cc43-8702-1c6e23d89ea4@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®