public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: MANISH PANDEY <quic_mapa@quicinc.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, quic_nitirawa@quicinc.com,
	quic_bhaskarv@quicinc.com, quic_rampraka@quicinc.com,
	quic_cang@quicinc.com, quic_nguyenb@quicinc.com
Subject: Re: [PATCH] ufs: qcom: Add quirks for Samsung UFS devices
Date: Wed, 26 Mar 2025 06:39:39 -0400	[thread overview]
Message-ID: <e5c5ea82-2103-4616-8bcf-e21be5952f4c@acm.org> (raw)
In-Reply-To: <33c03e94-5e8b-44cf-be32-fb571ca73a17@quicinc.com>

On 3/26/25 5:53 AM, MANISH PANDEY wrote:
> The QUIRK_PA_HIBER8TIME may also be necessary for other SoC vendors host 
> controllers. For instance, the ufs-exynos.c file implements a similar 
> approach in the fsd_ufs_post_link() function:
> 
> ufshcd_dme_set(hba, UIC_ARG_MIB(0x15A7), max_rx_hibern8_time_cap + 1);
> 
> https://lore.kernel.org/lkml/001101d874c1$3d850eb0$b88f2c10$@samsung.com/
> 
> Should we consider moving the QUIRK_PA_HIBER8TIME quirk to the ufshcd 
> driver? Please advise.

That would be appreciated.

Thanks,

Bart.

      reply	other threads:[~2025-03-26 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25  8:38 [PATCH] ufs: qcom: Add quirks for Samsung UFS devices Manish Pandey
2025-03-25 11:42 ` Bart Van Assche
2025-03-26  9:53   ` MANISH PANDEY
2025-03-26 10:39     ` Bart Van Assche [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=e5c5ea82-2103-4616-8bcf-e21be5952f4c@acm.org \
    --to=bvanassche@acm.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=quic_bhaskarv@quicinc.com \
    --cc=quic_cang@quicinc.com \
    --cc=quic_mapa@quicinc.com \
    --cc=quic_nguyenb@quicinc.com \
    --cc=quic_nitirawa@quicinc.com \
    --cc=quic_rampraka@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