From: Bean Huo <huobean@gmail.com>
To: "Asutosh Das (asd)" <quic_asutoshd@quicinc.com>,
quic_nguyenb@quicinc.com, quic_xiaosenh@quicinc.com,
stanley.chu@mediatek.com, adrian.hunter@intel.com,
bvanassche@acm.org, avri.altman@wdc.com, mani@kernel.org,
quic_cang@quicinc.com, beanhuo@micron.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org,
Alim Akhtar <alim.akhtar@samsung.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v3 1/4] ufs: core: prepare ufs for multi circular queue support
Date: Thu, 08 Sep 2022 10:23:20 +0200 [thread overview]
Message-ID: <6b56ad5fd5b5ab128afd399adb54a7566c4a144f.camel@gmail.com> (raw)
In-Reply-To: <df32bbd5-4109-903b-c7ba-7777a298f5aa@quicinc.com>
On Wed, 2022-09-07 at 20:00 -0700, Asutosh Das (asd) wrote:
> > > ufshcd_lrb *lrbp, u8 upiu_flags)
> > > /* command descriptor fields */
> > > ucd_req_ptr->header.dword_0 = UPIU_HEADER_DWORD(
> > > UPIU_TRANSACTION_COMMAND,
> > > upiu_flags,
> > > - lrbp->lun, lrbp->task_tag);
> > > + lrbp->lun, lrbp->task_tag &
> > > 0xff);
> > > ucd_req_ptr->header.dword_1 = UPIU_HEADER_DWORD(
> > > - UPIU_COMMAND_SET_TYPE_SCSI, 0, 0,
> > > 0);
> > > + UPIU_COMMAND_SET_TYPE_SCSI, 0, 0,
> > > + (lrbp->task_tag & 0xf00) << 4);
> > >
> >
> > Are you sure here "(lrbp->task_tag & 0xf00) << 4" is correct?
> >
> EXT_IID is the higher nibble in DWORD1. So this looks correct to me.
>
> COMMAND UPIU
> 0 1 2 3
> xx000001b Flags LUN Task Tag
> 4 5 6 7
> IID Command Set Type Reserved Reserved EXT_IID | Reserved
Hi Asutosh,
yes, [7:4] of byte 7 in UPIU header for host to device UPIUs EXT_IID,
this is correct.
but I think byte7 should be (lrbp->task_tag & 0xf00) >> 4); rather
than "<< 4"
or what I missundersood.
Kind regards,
Bean
next prev parent reply other threads:[~2022-09-08 8:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1662157846.git.quic_asutoshd@quicinc.com>
2022-09-02 22:41 ` Asutosh Das
2022-09-05 12:26 ` Bean Huo
2022-09-08 3:00 ` Asutosh Das (asd)
2022-09-08 8:23 ` Bean Huo [this message]
2022-09-08 21:58 ` Bart Van Assche
2022-09-09 22:48 ` Asutosh Das (asd)
2022-09-09 23:38 ` Bart Van Assche
2022-09-12 18:18 ` Asutosh Das (asd)
2022-09-02 22:41 ` [RFC PATCH v3 2/4] ufs: core: mcq: Adds Multi-Circular Queue support Asutosh Das
2022-09-05 13:48 ` Bean Huo
2022-09-08 3:01 ` Asutosh Das (asd)
2022-09-05 14:19 ` Bean Huo
2022-09-05 16:27 ` Bean Huo
2022-09-08 3:01 ` Asutosh Das (asd)
2022-09-08 22:02 ` Bart Van Assche
2022-09-08 23:21 ` Bart Van Assche
2022-09-02 22:41 ` [RFC PATCH v3 3/4] ufs: core: Add Event Specific Interrupt configuration vendor specific ops Asutosh Das
2022-09-02 22:41 ` [RFC PATCH v3 4/4] ufs: host: qcom: Add MCQ support Asutosh Das
2022-09-08 22:30 ` Bart Van Assche
2022-09-09 22:43 ` Asutosh Das (asd)
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=6b56ad5fd5b5ab128afd399adb54a7566c4a144f.camel@gmail.com \
--to=huobean@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_asutoshd@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_xiaosenh@quicinc.com \
--cc=stanley.chu@mediatek.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®