All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Can Guo <quic_cang@quicinc.com>,
	mani@kernel.org, quic_nguyenb@quicinc.com,
	quic_nitirawa@quicinc.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"open list:UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER..." 
	<linux-arm-msm@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] scsi: ufs: ufs-qcom: Add support for UFS device version detection
Date: Mon, 11 Sep 2023 11:46:20 +0200	[thread overview]
Message-ID: <31823dc4-6f50-435b-9a20-66471209ec31@linaro.org> (raw)
In-Reply-To: <6225a132-4b7f-bbb4-e863-4e62b99dd79d@quicinc.com>

On 11.09.2023 11:42, Can Guo wrote:
> Hi Konrad,
> 
> On 9/11/2023 5:17 PM, Konrad Dybcio wrote:
>> On 11.09.2023 07:59, Can Guo wrote:
>>> From: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>
>>>
>>> Retrieve UFS device version from UFS host controller's spare register
>>> which is populated by bootloader, and use the UFS device version together
>>> with host controller's HW version to decide the proper power modes which
>>> should be used to configure the UFS PHY.
>> That sounds a bit fishy.. is there no bootloader-independent
>> solution to that? Can't we bring in the code that the bootloader
>> uses to determine these values?
>>
>> Konrad
> 
> 
> Agree, it is.
> 
> 
> All these complexities come from one request from PHY design team - power saving.
> 
> And to achieve power saving, Qualcomm UFS developers are requested to use the
> 
> lowest hanging PHY settings which can sustain the Max agreed HS Gear (btw host
> 
> and UFS device) during UFS's lifecycle in High Level OS,  whereas the power saving
> 
> request does not apply to bootloader, which works for only a few seconds during
> 
> bootup. Hence, there is no such version detect code in bootloader -  it just uses the
> 
> highest PHY settings to configure PHY, boot up UFS and put UFS device version in this
> 
> register.
First of all, your email client seems to be inserting 2 newlines
instead of 1. If you're using thunderbird, you may want to edit:

mail.identity.(default or your mail identity idx).default.compose_html

to `false`

and add that to your internal wiki page, as I see many @quic folks having
this issue.


Going back to the main topic, I don't think we understood each other.
The commit message states:


"Retrieve UFS device version from UFS host controller's spare register
which is populated by bootloader"


Which means the bootloader is able to somehow determine the value
that's in the spare register and write it there.

I'm asking whether we can take the logic behind this value and
move it to Linux so that we don't depend on the bootloader to
guarantee it (e.g. Chrome or some other devices with more exotic
fw may not work this way).


Konrad

  reply	other threads:[~2023-09-11 21:21 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11  5:59 [PATCH 0/6] Enable HS-G5 support on SM8550 Can Guo
2023-09-11  5:59 ` [PATCH 1/6] scsi: ufs: ufs-qcom: Setup host power mode during init Can Guo
2023-09-14 12:40   ` Nitin Rawat
2023-09-19 10:36   ` Manivannan Sadhasivam
2023-10-31 13:09     ` Can Guo
2023-09-11  5:59 ` [PATCH 2/6] scsi: ufs: ufs-qcom: Add support for UFS device version detection Can Guo
2023-09-11  9:17   ` Konrad Dybcio
2023-09-11  9:42     ` Can Guo
2023-09-11  9:46       ` Konrad Dybcio [this message]
2023-09-11 10:02         ` Can Guo
2023-09-15  2:31           ` Dmitry Baryshkov
2023-09-19 12:08             ` Manivannan Sadhasivam
2023-09-19 22:27               ` Dmitry Baryshkov
2023-09-20 10:23                 ` Manivannan Sadhasivam
2023-09-20 11:13                   ` Dmitry Baryshkov
2023-09-20 11:51                     ` Manivannan Sadhasivam
2023-10-18 12:47                   ` Manivannan Sadhasivam
2023-10-26 19:31                     ` Konrad Dybcio
2023-10-27 12:22                       ` Manivannan Sadhasivam
2023-09-15 12:48           ` Konrad Dybcio
2023-10-18 14:02   ` Neil Armstrong
     [not found]     ` <059cc112-7fb6-4da4-bc25-4eede0252f0e@linaro.org>
2023-10-31  5:06       ` Can Guo
2023-10-31  9:30         ` neil.armstrong
2023-09-11  5:59 ` [PATCH 3/6] phy: qualcomm: phy-qcom-qmp-ufs: Add High Speed Gear 5 support for SM8550 Can Guo
2023-09-11  5:59   ` Can Guo
2023-09-14 12:26   ` Nitin Rawat
2023-09-14 12:26     ` Nitin Rawat
2023-09-15  2:07     ` Can Guo
2023-09-15  2:07       ` Can Guo
2023-09-19 12:10   ` Manivannan Sadhasivam
2023-09-19 12:10     ` Manivannan Sadhasivam
2023-09-11  5:59 ` [PATCH 4/6] phy: qualcomm: phy-qcom-qmp-ufs: Move data structs and setting tables to header Can Guo
2023-09-11  5:59   ` Can Guo
2023-09-14 11:44   ` Nitin Rawat
2023-09-14 11:44     ` Nitin Rawat
2023-09-14 12:28   ` Dmitry Baryshkov
2023-09-14 12:28     ` Dmitry Baryshkov
2023-09-19 12:15     ` Manivannan Sadhasivam
2023-09-19 12:15       ` Manivannan Sadhasivam
2023-09-19 22:30       ` Dmitry Baryshkov
2023-09-19 22:30         ` Dmitry Baryshkov
2023-09-20 10:19         ` Manivannan Sadhasivam
2023-09-20 10:19           ` Manivannan Sadhasivam
2023-09-21 14:02           ` Bjorn Andersson
2023-09-21 14:02             ` Bjorn Andersson
2023-09-22 18:23             ` Manivannan Sadhasivam
2023-09-22 18:23               ` Manivannan Sadhasivam
2023-09-21 13:58       ` Bjorn Andersson
2023-09-21 13:58         ` Bjorn Andersson
2023-09-11  5:59 ` [PATCH 5/6] scsi: ufs: ufs-sysfs: Expose UFS power info Can Guo
2023-09-14 11:33   ` Nitin Rawat
2023-09-15  1:59     ` Can Guo
2023-09-19 12:16   ` Manivannan Sadhasivam
2023-10-31  8:08     ` Can Guo
2023-10-26 19:53   ` Bart Van Assche
2023-10-31  4:46     ` Can Guo
2023-09-11  5:59 ` [PATCH 6/6] scsi: ufs: ufs-sysfs: Introduce UFS power info sysfs nodes Can Guo
2023-09-14 11:35   ` Nitin Rawat
2023-09-15  2:00     ` Can Guo
2023-09-18 15:36   ` Bart Van Assche
2023-10-31  4:53     ` Can Guo

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=31823dc4-6f50-435b-9a20-66471209ec31@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=quic_cang@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 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.