linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	Eric Chanudet <echanude@redhat.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] scsi: ufs: qcom: avoid re-init quirk when gears match
Date: Mon, 29 Jan 2024 21:27:02 -0500	[thread overview]
Message-ID: <170657812687.784857.2745114891755367401.b4-ty@oracle.com> (raw)
In-Reply-To: <20240123192854.1724905-4-echanude@redhat.com>

On Tue, 23 Jan 2024 14:28:57 -0500, Eric Chanudet wrote:

> On sa8775p-ride, probing the hba will go through the
> UFSHCD_QUIRK_REINIT_AFTER_MAX_GEAR_SWITCH path although the power info
> are same during the second init.
> 
> The REINIT quirk only applies starting with controller v4. For these,
> ufs_qcom_get_hs_gear() reads the highest supported gear when setting the
> host_params. After the negotiation, if the host and device are on the
> same gear, it is the highest gear supported between the two. Skip REINIT
> to save some time.
> 
> [...]

Applied to 6.9/scsi-queue, thanks!

[1/1] scsi: ufs: qcom: avoid re-init quirk when gears match
      https://git.kernel.org/mkp/scsi/c/10a39667a117

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2024-01-30  2:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 19:28 [PATCH v2] scsi: ufs: qcom: avoid re-init quirk when gears match Eric Chanudet
2024-01-24  8:48 ` Manivannan Sadhasivam
2024-01-24 13:55 ` Andrew Halaney
2024-01-25  2:36 ` Martin K. Petersen
2024-01-30  2:27 ` Martin K. Petersen [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=170657812687.784857.2745114891755367401.b4-ty@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=andersson@kernel.org \
    --cc=echanude@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).