[PATCH v2 0/4] devfreq: check the get_cur_freq() return value and use it in ufshcd · Bean Huo <hidden> · 2026-09-07
[PATCH v2 4/4] scsi: ufs: core: Report the current clock frequency to devfreq · Bean Huo <hidden> · 2026-09-07
[PATCH v2 1/4] PM / devfreq: Fall back to previous_freq when get_cur_freq() fails · Bean Huo <hidden> · 2026-09-07
[PATCH v2 2/4] PM / devfreq: Add more details to the get_cur_freq() comment · Bean Huo <hidden> · 2026-09-07
[PATCH v2 3/4] scsi: ufs: core: Record the frequency the controller starts at · Bean Huo <hidden> · 2026-09-07
Re: [PATCH v2 0/4] devfreq: check the get_cur_freq() return value and use it in ufshcd · Stanley Jhu <hidden> · 2026-09-08
Re: [PATCH v2 0/4] devfreq: check the get_cur_freq() return value and use it in ufshcd · "Martin K. Petersen (Oracle)" <mkp@kernel.org> · 2026-09-10

Re: [PATCH v2 0/4] devfreq: check the get_cur_freq() return value and use it in ufshcd

From: Stanley Jhu <hidden>
Date: 2026-09-08 01:34:52
Also in: linux-scsi, lkml

On Mon, 7 Sep 2026 21:21:36 +0200, Bean Huo wrote:

Changes since v1:
- New patch 3, so that target_freq and devfreq's previous_freq are not 0
  at boot (suggested by Stanley Jhu).
- Patch 4: drop the !cur_freq check, it cannot happen any more.

Thanks for addressing the initial frequency desync in v2.

For the series:
Reviewed-by: Stanley Jhu <redacted>

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help