mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel GUITTET <jguittet.opensource@witekio.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Bad commit backported on the v5.15.y branch ?
Date: Fri, 11 Oct 2024 08:48:39 +0000	[thread overview]
Message-ID: <AM9P192MB1316ABE1A8E1D41C4243F596D7792@AM9P192MB1316.EURP192.PROD.OUTLOOK.COM> (raw)

Hello,

I faced some issue related to scaling frequency on ZynqMP device using v5.15.167 kernel.
As an exemple setting the scaling frequency below show it's not properly set:

cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
299999 399999 599999 1199999

echo 399999 > /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed

cat /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq
399999

cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq
299999 ====> Should be 399999

After analysis of this issue with the help of Xilinx, it appears that a commit was backported on the 5.15.y branch, but probably it should not, or not as is. The commit is 9117fc44fd3a9538261e530ba5a022dfc9519620 modifying drivers/clk/zynqmp/divider.c.

Is anybody reading this message able to answer why it was backported ? The information I have until now is that it is intended recent kernel version. Dependencies for this modification is currently under clarification with Xilinx (maybe another commit to backport).

By the way, reverting this commit fix the issue shown above.

Thanks for the feedback,
Joel

             reply	other threads:[~2024-10-11  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  8:48 Joel GUITTET [this message]
2024-10-14  6:45 ` Thorsten Leemhuis
2024-10-16  9:23   ` Joel GUITTET
2024-10-16 10:53     ` Greg KH
2024-10-16 13:13       ` Joel GUITTET
2024-10-16 14:58         ` Greg KH

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=AM9P192MB1316ABE1A8E1D41C4243F596D7792@AM9P192MB1316.EURP192.PROD.OUTLOOK.COM \
    --to=jguittet.opensource@witekio.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®