All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daejun Park <daejun7.park@samsung.com>
To: Avri Altman <Avri.Altman@wdc.com>,
	Daejun Park <daejun7.park@samsung.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
	"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>,
	"cang@codeaurora.org" <cang@codeaurora.org>,
	"bvanassche@acm.org" <bvanassche@acm.org>,
	"huobean@gmail.com" <huobean@gmail.com>,
	ALIM AKHTAR <alim.akhtar@samsung.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	JinHwan Park <jh.i.park@samsung.com>,
	Javier Gonzalez <javier.gonz@samsung.com>,
	SEUNGUK SHIN <seunguk.shin@samsung.com>,
	Sung-Jun Park <sungjun07.park@samsung.com>,
	yongmyung lee <ymhungry.lee@samsung.com>,
	Jinyoung CHOI <j-young.choi@samsung.com>,
	BoRam Shin <boram.shin@samsung.com>
Subject: RE: RE: [PATCH v24 4/4] scsi: ufs: Add HPB 2.0 support
Date: Thu, 25 Feb 2021 12:26:15 +0900	[thread overview]
Message-ID: <20210225032615epcms2p6679f3571205dc7a9c222f07398a9726c@epcms2p6> (raw)
In-Reply-To: <DM6PR04MB6575BBF6F89002222EA5FC1DFC9F9@DM6PR04MB6575.namprd04.prod.outlook.com>

> >         if (dev_info->wspecversion >= UFS_DEV_HPB_SUPPORT_VERSION &&
> >             (b_ufs_feature_sup & UFS_DEV_HPB_SUPPORT)) {
> > -               dev_info->hpb_enabled = true;
> > +               bool hpb_en = false;
> > +
> >                 ufshpb_get_dev_info(hba, desc_buf);
> > +
> > +               err = ufshcd_query_flag_retry(hba,
> > UPIU_QUERY_OPCODE_READ_FLAG,
> > +                                             QUERY_FLAG_IDN_HPB_EN, 0, &hpb_en);
> > +               if (ufshpb_is_legacy(hba) || (!err && hpb_en))
> If is_legacy you shouldn't send fHPBen in the first place, not ignoring its failure.
OK,

> Also, using a Boolean is limiting you to HPB2.0 vs. HPB1.0.
> What would you do in new flags/attributes/descriptors that HPB3.0 will introduce?
It can be managed as enum. but it is enough now, I think.

> > +                       dev_info->hpb_enabled = true;
> >         }

Thanks,
Daejun

      parent reply	other threads:[~2021-02-25  3:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210224045323epcms2p66cc6a4b73086621e050da37f12f432f0@epcms2p6>
2021-02-24  4:53 ` [PATCH v24 0/4] scsi: ufs: Add Host Performance Booster Support Daejun Park
     [not found]   ` <CGME20210224045323epcms2p66cc6a4b73086621e050da37f12f432f0@epcms2p7>
2021-02-24  4:54     ` [PATCH v24 2/4] scsi: ufs: L2P map management for HPB read Daejun Park
2021-02-25 14:59       ` Bean Huo
     [not found]       ` <CGME20210224045323epcms2p66cc6a4b73086621e050da37f12f432f0@epcms2p4>
2021-02-26  4:53         ` Daejun Park
2021-02-24  4:55     ` [PATCH v24 3/4] scsi: ufs: Prepare HPB read for cached sub-region Daejun Park
     [not found]   ` <CGME20210224045323epcms2p66cc6a4b73086621e050da37f12f432f0@epcms2p2>
2021-02-24  4:54     ` [PATCH v24 1/4] scsi: ufs: Introduce HPB feature Daejun Park
2021-02-25 14:38       ` Bean Huo
     [not found]       ` <CGME20210224045323epcms2p66cc6a4b73086621e050da37f12f432f0@epcms2p1>
2021-02-26  4:49         ` Daejun Park
2021-02-24  4:55     ` [PATCH v24 4/4] scsi: ufs: Add HPB 2.0 support Daejun Park
2021-02-24  9:52       ` Avri Altman
2021-02-24 10:24       ` Avri Altman
2021-02-24 11:52         ` Avri Altman
     [not found]         ` <CGME20210224045323epcms2p66cc6a4b73086621e050da37f12f432f0@epcms2p5>
2021-02-25  3:25           ` Daejun Park
2021-02-25  3:26 ` Daejun Park [this message]

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=20210225032615epcms2p6679f3571205dc7a9c222f07398a9726c@epcms2p6 \
    --to=daejun7.park@samsung.com \
    --cc=Avri.Altman@wdc.com \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=boram.shin@samsung.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=huobean@gmail.com \
    --cc=j-young.choi@samsung.com \
    --cc=javier.gonz@samsung.com \
    --cc=jejb@linux.ibm.com \
    --cc=jh.i.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=seunguk.shin@samsung.com \
    --cc=stanley.chu@mediatek.com \
    --cc=sungjun07.park@samsung.com \
    --cc=ymhungry.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 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.