public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Naresh Maramaina <quic_mnaresh@quicinc.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Peter Wang <peter.wang@mediatek.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	chu.stanley@gmail.com
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, quic_cang@quicinc.com,
	quic_nguyenb@quicinc.com, Nitin Rawat <quic_nitirawa@quicinc.com>
Subject: Re: [PATCH V2 1/3] ufs: core: Add CPU latency QoS support for ufs driver
Date: Tue, 5 Dec 2023 07:11:56 -1000	[thread overview]
Message-ID: <5e7c5c75-cb5f-4afe-9d57-b0cab01a6f26@acm.org> (raw)
In-Reply-To: <692cd503-5b14-4be6-831d-d8e9c282a95e@quicinc.com>

On 12/4/23 21:58, Naresh Maramaina wrote:
> On 12/5/2023 12:30 AM, Bart Van Assche wrote:
>> On 12/4/23 06:30, Maramaina Naresh wrote:
>>> +    /* This capability allows the host controller driver to use the 
>>> PM QoS
>>> +     * feature.
>>> +     */
>>> +    UFSHCD_CAP_PM_QOS                = 1 << 13,
>>>   };
>>
>> Why does it depend on the host driver whether or not PM QoS is
>> enabled? Why isn't it enabled unconditionally?
> 
> For some platform vendors power KPI might be more important than random 
> io KPI. Hence this flag is disabled by default and can be enabled based 
> on platform requirement.

How about leaving this flag out unless if a host vendor asks explicitly
for this flag?
>>
>>> + * @pm_qos_req: PM QoS request handle
>>> + * @pm_qos_init: flag to check if pm qos init completed
>>>    */
>>
>> Documentation for pm_qos_init is missing.
>>
> Sorry, i didn't get your comment, i have already added documentation for 
> @pm_qos_init, @pm_qos_req variable as above. Do you want me to add this 
> information some where else as well?

Oops, I meant 'qos_vote'.

Thanks,

Bart.


  reply	other threads:[~2023-12-05 17:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 14:30 [PATCH V2 0/3] Add CPU latency QoS support for ufs driver Maramaina Naresh
2023-12-04 14:30 ` [PATCH V2 1/3] ufs: core: " Maramaina Naresh
2023-12-04 19:00   ` Bart Van Assche
2023-12-05  5:58     ` Naresh Maramaina
2023-12-05 17:11       ` Bart Van Assche [this message]
2023-12-06 14:02         ` Naresh Maramaina
2023-12-06 15:32           ` Manivannan Sadhasivam
2023-12-07  1:02             ` Bart Van Assche
2023-12-07  9:43               ` Manivannan Sadhasivam
2023-12-07 10:26                 ` Nitin Rawat
2023-12-07 11:21                   ` Manivannan Sadhasivam
2023-12-11 10:00                     ` Pavan Kondeti
2023-12-06 15:26   ` Manivannan Sadhasivam
2023-12-07 11:26     ` Naresh Maramaina
2023-12-11  9:56     ` Naresh Maramaina
2023-12-04 14:31 ` [PATCH V2 2/3] ufs: ufs-mediatek: Enable CPU latency PM QoS support for MEDIATEK SoC Maramaina Naresh
2023-12-04 14:31 ` [PATCH V2 3/3] ufs: ufs-qcom: Enable CPU latency QoS support for QCOM SoC Maramaina Naresh

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=5e7c5c75-cb5f-4afe-9d57-b0cab01a6f26@acm.org \
    --to=bvanassche@acm.org \
    --cc=agross@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=andersson@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=avri.altman@wdc.com \
    --cc=chu.stanley@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=matthias.bgg@gmail.com \
    --cc=peter.wang@mediatek.com \
    --cc=quic_cang@quicinc.com \
    --cc=quic_mnaresh@quicinc.com \
    --cc=quic_nguyenb@quicinc.com \
    --cc=quic_nitirawa@quicinc.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