From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "beanhuo@micron.com" <beanhuo@micron.com>,
"mani@kernel.org" <mani@kernel.org>,
"can.guo@oss.qualcomm.com" <can.guo@oss.qualcomm.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"krzk@kernel.org" <krzk@kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"quic_nitirawa@quicinc.com" <quic_nitirawa@quicinc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"quic_rdwivedi@quicinc.com" <quic_rdwivedi@quicinc.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v9 2/2] scsi: ufs: core: Add support for static TX Equalization settings
Date: Tue, 16 Jun 2026 08:04:41 +0000 [thread overview]
Message-ID: <e4590bb7dcda6bd8b20af2e22a18111b998b9efb.camel@mediatek.com> (raw)
In-Reply-To: <20260615132834.2985346-3-can.guo@oss.qualcomm.com>
On Mon, 2026-06-15 at 06:28 -0700, Can Guo wrote:
> Parse board-specific static TX Equalization settings from Device Tree
> for
> each HS gear and store them in hba->tx_eq_params.
>
> Parse txeq-preshoot-g[1-6] and txeq-deemphasis-g[1-6] as per-lane
> tuples:
> <Host_Lane0 Device_Lane0>, [<Host_Lane1 Device_Lane1>].
>
> For HS-G6, parse optional tx-precode-enable-g6 using the same per-
> lane
> Host/Device tuple format. If provided, it must contain values for all
> active lanes, and each value must be 0 or 1.
>
> Introduce from_dt in struct ufshcd_tx_eq_params to track whether TX
> EQ
> values came from static Device Tree data.
>
> When TX Equalization Training is used, static settings are not final:
> - If valid settings are retrieved from
> qTxEQGnSettings/wTxEQGnSettingsExt,
> those retrieved settings override static Device Tree settings.
> - If retrieval is not available/valid, TX EQTR runs and trained
> settings
> override static Device Tree settings.
>
> No behavior changes for platforms that do not provide these
> properties.
>
> Signed-off-by: Can Guo <can.guo@oss.qualcomm.com>
> ---
Hi Can,
I agree with Bart's comment.
Regarding sashiko-bot's comment, will you have another patch to
fix this pre-existing issue?
I think force_tx_eqtr could potentially trigger this deadlock.
Thanks.
Peter
next prev parent reply other threads:[~2026-06-16 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260615132834.2985346-1-can.guo@oss.qualcomm.com>
2026-06-15 13:28 ` [PATCH v9 1/2] dt-bindings: ufs: Document static TX Equalization settings properties Can Guo
2026-06-16 3:54 ` Krzysztof Kozlowski
2026-06-16 10:36 ` Peter Wang (王信友)
2026-06-15 13:28 ` [PATCH v9 2/2] scsi: ufs: core: Add support for static TX Equalization settings Can Guo
2026-06-15 13:38 ` Bart Van Assche
2026-06-16 8:05 ` Can Guo
2026-06-16 8:04 ` Peter Wang (王信友) [this message]
2026-06-16 9:09 ` Can Guo
2026-06-16 10:35 ` Peter Wang (王信友)
2026-06-16 10:36 ` 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=e4590bb7dcda6bd8b20af2e22a18111b998b9efb.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=can.guo@oss.qualcomm.com \
--cc=krzk@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_nitirawa@quicinc.com \
--cc=quic_rdwivedi@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
all inboxes | Powered by JetHome®