From: palash.kambar@oss.qualcomm.com
To: 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, bvanassche@acm.org,
shawn.lin@rock-chips.com, nitin.rawat@oss.qualcomm.com,
Palash Kambar <palash.kambar@oss.qualcomm.com>
Subject: [PATCH V7 0/2] Add post change sequence for link start notify
Date: Thu, 23 Apr 2026 15:50:21 +0530 [thread overview]
Message-ID: <20260423102023.3779489-1-palash.kambar@oss.qualcomm.com> (raw)
From: Palash Kambar <palash.kambar@oss.qualcomm.com>
changes from V1
1) Addressed Shawn Lin's comments to fix comment to connected lanes.
2) Addressed Bart's comments to remove warning and trigger failure
incase of lane mismatch.
changes from V2:
1) Addressed Shawn's comments to fix commit text.
2) Addressed Bart's comments to remove variable initializations and
indentation fix.
changes from V3:
1) Addressed Manivannan's comments to remove extra comment and return
logic.
changes from V4:
1) Addressed Manivannan's comments to fix indentation and return
handling.
changes from V5:
1) Addressed Manivannan's comment and added back the missed tags from
V3.
changes from V6:
1) Addressed Manivannan's comment to fix return handling logic.
Palash Kambar (2):
ufs: core: Configure only active lanes during link
ufs: ufs-qcom: Enable Auto Hibern8 clock request support
drivers/ufs/core/ufshcd.c | 33 +++++++++++++++++++++++++++++++++
drivers/ufs/host/ufs-qcom.c | 10 ++++++++++
drivers/ufs/host/ufs-qcom.h | 11 +++++++++++
3 files changed, 54 insertions(+)
--
2.34.1
next reply other threads:[~2026-04-23 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 10:20 palash.kambar [this message]
2026-04-23 10:20 ` [PATCH V7 1/2] ufs: core: Configure only active lanes during link palash.kambar
2026-04-23 10:20 ` [PATCH V7 2/2] ufs: ufs-qcom: Enable Auto Hibern8 clock request support palash.kambar
2026-04-27 15:57 ` Bart Van Assche
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=20260423102023.3779489-1-palash.kambar@oss.qualcomm.com \
--to=palash.kambar@oss.qualcomm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--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=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