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, shawn.lin@rock-chips.com,
nitin.rawat@oss.qualcomm.com
Subject: Re: [PATCH V2 2/2] ufs: ufs-qcom: Enable Auto Hibern8 clock request support
Date: Fri, 27 Mar 2026 14:22:06 -0700 [thread overview]
Message-ID: <97050b9c-7174-4402-a1ee-66269f8d8b6a@acm.org> (raw)
In-Reply-To: <20260327090346.656324-3-palash.kambar@oss.qualcomm.com>
On 3/27/26 2:03 AM, palash.kambar@oss.qualcomm.com wrote:
> On platforms that support Auto Hibern8 (AH8), the UFS controller can
> autonomously de-assert clk_req signals to the GCC when entering the
> Hibern8 state. This allows GCC to gate unused clocks, improving
> power efficiency.
What is the "GCC"? Please expand acronyms that are neither defined in
the UFSHCI standard nor in the UFS standard.
> +static void ufs_qcom_link_startup_post_change(struct ufs_hba *hba)
> +{
> + if (ufshcd_is_auto_hibern8_supported(hba)) {
> + ufshcd_rmwl(hba, UFS_HW_CLK_CTRL_EN, UFS_HW_CLK_CTRL_EN,
> + UFS_AH8_CFG);
> + }
> +}
From the Linux kernel coding style "Do not unnecessarily use braces
where a single statement will do." Please follow that rule.
Thanks,
Bart.
next prev parent reply other threads:[~2026-03-27 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 9:03 [PATCH V2 0/2] Add post change sequence for link start notify palash.kambar
2026-03-27 9:03 ` [PATCH V2 1/2] ufs: core: Configure only active lanes during link palash.kambar
2026-03-27 9:31 ` Shawn Lin
2026-03-27 11:58 ` Palash Kambar
2026-03-27 21:17 ` Bart Van Assche
2026-04-03 11:58 ` Palash Kambar
2026-03-27 9:03 ` [PATCH V2 2/2] ufs: ufs-qcom: Enable Auto Hibern8 clock request support palash.kambar
2026-03-27 21:22 ` Bart Van Assche [this message]
2026-04-03 11:59 ` Palash Kambar
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=97050b9c-7174-4402-a1ee-66269f8d8b6a@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