From: "정요한(JOUNG YOHAN) Mobile SE" <yohan.joung@sk.com>
To: Bean Huo <huobean@gmail.com>,
"daejun7.park@samsung.com" <daejun7.park@samsung.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"cang@codeaurora.org" <cang@codeaurora.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"최재영(CHOI JAE YOUNG) Mobile SE" <jaeyoung21.choi@sk.com>,
"곽태수(KWAK TAESU) Mobile SE" <taesu.kwak@sk.com>
Subject: RE: Please check ufshpb init flow
Date: Tue, 23 Nov 2021 05:19:59 +0000 [thread overview]
Message-ID: <4d2331ea33a246c78fcabaf1ca4e0b10@sk.com> (raw)
In-Reply-To: <b06d9a87232a6d4e90fe635384a83c48586652e9.camel@gmail.com>
> it's for "Inactivating all HPB regions" after reboot
>
> scsi_add_lun()...>ufshpb_issue_umap_all_req(hpb);
>
> if it is a cold reboot on both host side and UFS device side, it is not
> necessary to issue this write buffer.
According to you, is ufshpb_issue_umap_all_req used only for host reset?
During boottime, the problem is that the hpb is set to the last LUN, write buffer command is sent before sd_probe completes.
so, instead of performing unmap, UAC is returned.
If ufshpb_issue_umap_all_req is not needed in cold boot, it seems necessary to move it to an appropriate location or remove
>
>
> On Fri, 2021-11-19 at 02:31 +0000, 정요한(JOUNG YOHAN) Mobile SE wrote:
> > Hi daejun
> >
> > Please check ufshpb init flow.
> > sending write buffer(0x03) seems spec violation (JESD220 Commands for
> > exceptional behavior on UAC, SAM 5r05) before UAC clear (sd_probe).
> > Anyway hpb reset query(ufshpb_check_hpb_reset_query) seems sufficient.
> > Why do we need to send write buffer?
> >
> > void ufshpb_init_hpb_lu(struct ufs_hba *hba, struct scsi_device
> > *sdev)
> > {
> > out:
> > /* All LUs are initialized */
> > if (atomic_dec_and_test(&hba->ufshpb_dev.slave_conf_cnt))
> > There seems to be a problem with this logic.
> > If hpb is set on the last LUN, write buffer command is sent before
> > sd_probe completes.
> > ufshpb_hpb_lu_prepared(hba);
> > }
> >
> > static void ufshpb_hpb_lu_prepared(struct ufs_hba *hba) {
> >
> > init_success = !ufshpb_check_hpb_reset_query(hba);
> >
> > shost_for_each_device(sdev, hba->host) {
> > hpb = ufshpb_get_hpb_data(sdev);
> > if (!hpb)
> > continue;
> >
> > if (init_success) {
> > ufshpb_set_state(hpb, HPB_PRESENT);
> > if ((hpb->lu_pinned_end - hpb->lu_pinned_start) > 0)
> > queue_work(ufshpb_wq, &hpb->map_work);
> > if (!hpb->is_hcm)
> > ufshpb_issue_umap_all_req(hpb);
> > This seems unnecessary.
> >
> > } else {
> >
> > Thanks
> > yohan
next prev parent reply other threads:[~2021-11-23 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 2:31 Please check ufshpb init flow 정요한(JOUNG YOHAN) Mobile SE
2021-11-19 9:59 ` Bean Huo
2021-11-23 5:19 ` 정요한(JOUNG YOHAN) Mobile SE [this message]
2022-04-12 7:50 ` Po-Wen Kao
2022-04-12 7:51 ` Po-Wen Kao
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=4d2331ea33a246c78fcabaf1ca4e0b10@sk.com \
--to=yohan.joung@sk.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=daejun7.park@samsung.com \
--cc=huobean@gmail.com \
--cc=jaeyoung21.choi@sk.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stanley.chu@mediatek.com \
--cc=taesu.kwak@sk.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