From: Bean Huo <huobean@gmail.com>
To: Huan Tang <tanghuan@vivo.com>, beanhuo@micron.com
Cc: bvanassche@acm.org, cang@qti.qualcomm.com,
linux-scsi@vger.kernel.org, opensource.kernel@vivo.com,
richardp@quicinc.com, luhongfei@vivo.com
Subject: Re: [EXT] Re: [PATCH v2] ufs: core: Add WB buffer resize support
Date: Wed, 30 Oct 2024 16:13:38 +0100 [thread overview]
Message-ID: <580c23960612b82ae0278ad51d13df2b6c0a9fea.camel@gmail.com> (raw)
In-Reply-To: <20241030093743.659-1-tanghuan@vivo.com>
On Wed, 2024-10-30 at 17:37 +0800, Huan Tang wrote:
> > Hi Bart,
> >
> > Thank you for your feedback. That's good point. But I didn't
> > observe the ufs-bsg path bypassing core logic such as clock scaling
> > and clock gating. However, I might be mistaken.
> >
> > From my understanding, changing certain attributes can indeed
> > bypass the UFS driver tracking. But in this particular patch, there
> > is no parameter or flag associated that is tracked by the UFS
> > driver.
> >
> > Best regards,
> > Bean
>
> Hi Bean,
>
> Thank you for your reply!
>
> Actually, there are some parameters related to UFS driver; for
> example: b_presrv_uspc_en, host_sem, etc.
>
> Thanks
> Huan
I meant there isn’t a UFS driver parameter tied to adjusting the WB size.
If you think there is issue on changing WB size over ufs-bsg, please
make sure
to emphasize the issue of this and the reason why you add this new
interface in
your patch.
Kind regards,
Bean
prev parent reply other threads:[~2024-10-30 15:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 0:44 [PATCH v2] ufs: core: Add WB buffer resize support Huan Tang
2024-10-26 17:03 ` kernel test robot
2024-10-26 17:44 ` kernel test robot
2024-10-26 19:40 ` Bean Huo
2024-10-28 18:37 ` Bart Van Assche
2024-10-28 20:04 ` [EXT] " Bean Huo
2024-10-28 20:10 ` Bart Van Assche
2024-10-28 20:17 ` Bean Huo
2024-10-29 2:53 ` Huan Tang
2024-10-29 3:11 ` Huan Tang
2024-10-29 10:17 ` Bean Huo
2024-10-29 12:03 ` Huan Tang
2024-10-29 13:18 ` Bean Huo
2024-10-29 16:56 ` Bart Van Assche
2024-10-29 18:44 ` Bean Huo
2024-10-30 9:37 ` Huan Tang
2024-10-30 15:13 ` Bean Huo [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=580c23960612b82ae0278ad51d13df2b6c0a9fea.camel@gmail.com \
--to=huobean@gmail.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@qti.qualcomm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luhongfei@vivo.com \
--cc=opensource.kernel@vivo.com \
--cc=richardp@quicinc.com \
--cc=tanghuan@vivo.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