From: Bean Huo <beanhuo@iokpp.de>
To: Avri Altman <Avri.Altman@wdc.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"tomas.winkler@intel.com" <tomas.winkler@intel.com>,
"daejun7.park@samsung.com" <daejun7.park@samsung.com>,
"quic_cang@quicinc.com" <quic_cang@quicinc.com>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"quic_xiaosenh@quicinc.com" <quic_xiaosenh@quicinc.com>,
"quic_richardp@quicinc.com" <quic_richardp@quicinc.com>,
"quic_asutoshd@quicinc.com" <quic_asutoshd@quicinc.com>,
"hare@suse.de" <hare@suse.de>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v1 1/2] ufs: core: Advanced RPMB detection
Date: Tue, 08 Nov 2022 17:50:06 +0100 [thread overview]
Message-ID: <1eda1c55fdf8292c2912c6d0adb741d8dd7f0a20.camel@iokpp.de> (raw)
In-Reply-To: <DM6PR04MB6575145B168BB80F3D2910A7FC3F9@DM6PR04MB6575.namprd04.prod.outlook.com>
Avri,
thanks for your review.
On Tue, 2022-11-08 at 13:40 +0000, Avri Altman wrote:
> > From: Bean Huo <beanhuo@micron.com>
> >
> > Check UFS Advanced RPMB LU enablement during ufshcd_lu_init().
> >
> > Signed-off-by: Bean Huo <beanhuo@micron.com>
> > ---
> > drivers/ufs/core/ufshcd.c | 4 ++++
> > include/ufs/ufs.h | 3 +++
> > 2 files changed, 7 insertions(+)
> >
> > diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> > index
> > ee73d7036133..d49e7a0b82ca 100644
> > --- a/drivers/ufs/core/ufshcd.c
> > +++ b/drivers/ufs/core/ufshcd.c
> > @@ -4940,6 +4940,10 @@ static void ufshcd_lu_init(struct ufs_hba
> > *hba,
> > struct scsi_device *sdev)
> > desc_buf[UNIT_DESC_PARAM_LU_WR_PROTECT] ==
> > UFS_LU_POWER_ON_WP)
> > hba->dev_info.is_lu_power_on_wp = true;
> >
> > + if (desc_buf[UNIT_DESC_PARAM_UNIT_INDEX] == UFS_RPMB_UNIT
> > &&
> Please remind me why do we need both UFS_RPMB_UNIT and
> UFS_UPIU_RPMB_WLUN ?
I see. they are the same value, we should remove one, will change it in
next version.
>
> > + desc_buf[UNIT_DESC_PARAM_RPMB_REGION_EN] & 1 << 4)
> (1 << 4) or BIT(4) ?
>
> > + hba->dev_info.b_advanced_rpmb_en = true;
> > +
> > kfree(desc_buf);
> > set_qdepth:
> > /*
> > diff --git a/include/ufs/ufs.h b/include/ufs/ufs.h index
> > 1bba3fead2ce..2e617ab87750 100644
> > --- a/include/ufs/ufs.h
> > +++ b/include/ufs/ufs.h
> > @@ -199,6 +199,7 @@ enum unit_desc_param {
> > UNIT_DESC_PARAM_PSA_SENSITIVE = 0x7,
> > UNIT_DESC_PARAM_MEM_TYPE = 0x8,
> > UNIT_DESC_PARAM_DATA_RELIABILITY = 0x9,
> > + UNIT_DESC_PARAM_RPMB_REGION_EN = 0x9,
> This is awkward. Better to define it, or -
> Maybe it's time for rpmb to have its own unit descriptor - it surely
> deserve it.
>
no problem, let me think about it, will add in the next version.
Kind regards,
Bean
next prev parent reply other threads:[~2022-11-08 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 13:10 [RFC PATCH v1 0/2] UFS Advanced RPMB Bean Huo
2022-11-07 13:10 ` [RFC PATCH v1 1/2] ufs: core: Advanced RPMB detection Bean Huo
2022-11-08 13:40 ` Avri Altman
2022-11-08 16:50 ` Bean Huo [this message]
2022-11-08 21:41 ` Avri Altman
2022-11-07 13:10 ` [RFC PATCH v1 2/2] ufs: core: Add advanced RPMB support in ufs_bsg Bean Huo
2022-11-08 19:09 ` Avri Altman
2022-11-08 19:28 ` Bean Huo
2022-11-08 21:00 ` Avri Altman
2022-11-08 21:17 ` Avri Altman
2022-11-09 8:07 ` Avri Altman
2022-11-08 12:37 ` [RFC PATCH v1 0/2] UFS Advanced RPMB Avri Altman
2022-11-08 12:53 ` Bean Huo
2022-11-09 8:18 ` Avri Altman
2022-11-10 13:50 ` Bean Huo
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=1eda1c55fdf8292c2912c6d0adb741d8dd7f0a20.camel@iokpp.de \
--to=beanhuo@iokpp.de \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=daejun7.park@samsung.com \
--cc=hare@suse.de \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_asutoshd@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_richardp@quicinc.com \
--cc=quic_xiaosenh@quicinc.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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®