public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Can Guo <can.guo@oss.qualcomm.com>
Cc: avri.altman@wdc.com, bvanassche@acm.org, beanhuo@micron.com,
	peter.wang@mediatek.com, martin.petersen@oracle.com,
	mani@kernel.org, linux-scsi@vger.kernel.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	linux-kernel@vger.kernel.org (open list:ARM/Mediatek SoC
	support:Keyword:mediatek),
	linux-arm-kernel@lists.infradead.org (moderated
	list:ARM/Mediatek SoC support:Keyword:mediatek),
	linux-mediatek@lists.infradead.org (moderated list:ARM/Mediatek
	SoC support:Keyword:mediatek)
Subject: Re: [PATCH v5 00/12] scsi: ufs: Add TX Equalization support for UFS 5.0
Date: Fri, 27 Mar 2026 17:25:14 -0400	[thread overview]
Message-ID: <yq1jyux7yok.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260325152154.1604082-1-can.guo@oss.qualcomm.com> (Can Guo's message of "Wed, 25 Mar 2026 08:21:42 -0700")


Can,

> The UFS v5.0 and UFSHCI v5.0 standards have published, introducing
> support for HS-G6 (46.6 Gbps per lane) through the new UniPro V3.0
> interconnect layer and M-PHY V6.0 physical layer specifications. To
> achieve reliable operation at these higher speeds, UniPro V3.0
> introduces TX Equalization and Pre-Coding mechanisms that are
> essential for signal integrity.

Applied to 7.1/scsi-staging, thanks!

-- 
Martin K. Petersen


  parent reply	other threads:[~2026-03-27 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 15:21 [PATCH v5 00/12] scsi: ufs: Add TX Equalization support for UFS 5.0 Can Guo
2026-03-25 15:21 ` [PATCH v5 01/12] scsi: ufs: core: Introduce a new ufshcd vops negotiate_pwr_mode() Can Guo
2026-03-26  1:52 ` [PATCH v5 00/12] scsi: ufs: Add TX Equalization support for UFS 5.0 Peter Wang (王信友)
2026-03-27 21:25 ` Martin K. Petersen [this message]
2026-04-03  2:05 ` Martin K. Petersen

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=yq1jyux7yok.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=can.guo@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=peter.wang@mediatek.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