From: Bart Van Assche <bvanassche@acm.org>
To: palash.kambar@oss.qualcomm.com, mani@kernel.org,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Cc: linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, nitin.rawat@oss.qualcomm.com,
shawn.lin@rock-chips.com
Subject: Re: [PATCH v4 1/2] ufs: core: Configure only active lanes during link
Date: Fri, 17 Apr 2026 09:32:14 -0700 [thread overview]
Message-ID: <7594972e-5c01-470c-a59e-2419da730f21@acm.org> (raw)
In-Reply-To: <20260417045602.3042928-2-palash.kambar@oss.qualcomm.com>
On 4/16/26 9:56 PM, palash.kambar@oss.qualcomm.com wrote:
> The number of connected lanes detected during UFS link startup can be
> fewer than the lanes specified in the device tree. The current driver
> logic attempts to configure all lanes defined in the device tree,
> regardless of their actual availability. This mismatch may cause
> failures during power mode changes.
>
> Hence, Add a check during link startup to ensure that only the lanes
> actually discovered are considered valid. If a mismatch is detected,
> fail the initialization early, preventing the driver from entering
> an unsupported configuration that could cause power mode transition
> failures.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2026-04-17 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 4:56 [PATCH v4 0/2] Add post change sequence for link start notify palash.kambar
2026-04-17 4:56 ` [PATCH v4 1/2] ufs: core: Configure only active lanes during link palash.kambar
2026-04-17 16:32 ` Bart Van Assche [this message]
2026-04-20 0:37 ` Shawn Lin
2026-04-20 9:40 ` Manivannan Sadhasivam
2026-04-22 11:42 ` Palash Kambar
2026-04-17 4:56 ` [PATCH v4 2/2] ufs: ufs-qcom: Enable Auto Hibern8 clock request support palash.kambar
2026-04-20 9:40 ` Manivannan Sadhasivam
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=7594972e-5c01-470c-a59e-2419da730f21@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=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nitin.rawat@oss.qualcomm.com \
--cc=palash.kambar@oss.qualcomm.com \
--cc=shawn.lin@rock-chips.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