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 V7 2/2] ufs: ufs-qcom: Enable Auto Hibern8 clock request support
Date: Mon, 27 Apr 2026 08:57:54 -0700 [thread overview]
Message-ID: <20f52429-10e2-4407-b2ab-63bb92b85d6e@acm.org> (raw)
In-Reply-To: <20260423102023.3779489-3-palash.kambar@oss.qualcomm.com>
On 4/23/26 3:20 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 Global Clock Controller
> when entering the Hibern8 state. This allows Global Clock Controller
> (GCC) to gate unused clocks, improving power efficiency.
>
> Enable the Clock Request feature by setting the UFS_HW_CLK_CTRL_EN
> bit in the UFS_AH8_CFG register, as recommended in the Hardware
> Programming Guidelines.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2026-04-27 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 10:20 [PATCH V7 0/2] Add post change sequence for link start notify palash.kambar
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 [this message]
2026-05-15 2:20 ` [PATCH V7 0/2] Add post change sequence for link start notify 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=20f52429-10e2-4407-b2ab-63bb92b85d6e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.