From: "Kiwoong Kim" <kwmad.kim@samsung.com>
To: <adrian.hunter@intel.com>
Cc: <alim.akhtar@samsung.com>, <asutoshd@codeaurora.org>,
<avri.altman@wdc.com>, <bvanassche@acm.org>,
<cang@codeaurora.org>, <huobean@gmail.com>, <jejb@linux.ibm.com>,
<linux-scsi@vger.kernel.org>, <liwei213@huawei.com>,
<manivannan.sadhasivam@linaro.org>, <martin.petersen@oracle.com>
Subject: Re: [PATCH V5 1/3] scsi: ufs: Fix error handler clear ua deadlock
Date: Tue, 28 Sep 2021 15:47:56 +0900 [thread overview]
Message-ID: <002201d7b434$c4bdef80$4e39ce80$@samsung.com> (raw)
In-Reply-To: CGME20210928064756epcas2p3975b89e0cecd0ca1807b354bafadccd3@epcas2p3.samsung.com
+ prd_table[0].size = cpu_to_le32(UFS_SENSE_SIZE - 1);
UFSHCI specifies Data Byte Count (DBC) like this:
A ‘0’ based value that indicates the length, in bytes, of the data
block. A maximum of length of 256KB may exist for any entry. Bits 1:0 of this field shall be
11b to indicate Dword granularity. A value of ‘3’ indicates 4 bytes, ‘7’ indicates 8 bytes, etc.
That means the size value should be aligned with 4. And as I know it's 18.
Thanks.
Kiwoong Kim
next parent reply other threads:[~2021-09-28 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210928064756epcas2p3975b89e0cecd0ca1807b354bafadccd3@epcas2p3.samsung.com>
2021-09-28 6:47 ` Kiwoong Kim [this message]
2021-09-22 9:38 [PATCH V5 0/3] scsi: ufs: Let devices remain runtime suspended during system suspend Adrian Hunter
2021-09-22 9:38 ` [PATCH V5 1/3] scsi: ufs: Fix error handler clear ua deadlock Adrian Hunter
2021-09-28 6:55 ` Kiwoong Kim
2021-09-30 12:44 ` Adrian Hunter
2021-09-29 5:01 ` Kiwoong Kim
2021-09-30 12:43 ` Adrian Hunter
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='002201d7b434$c4bdef80$4e39ce80$@samsung.com' \
--to=kwmad.kim@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=liwei213@huawei.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.