From: Markus Mayer <markus.mayer@broadcom.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Markus Mayer <markus.mayer@broadcom.com>,
Linux Power Management List <linux-pm@vger.kernel.org>
Subject: [PATCH 0/3] brcmstb-avs-cpufreq updates
Date: Thu, 28 May 2020 11:19:18 -0700 [thread overview]
Message-ID: <20200528181921.19846-1-mmayer@broadcom.com> (raw)
Hi all,
Here is a collection of little, independent improvements to the
brcmstb-avs-cpufreq driver.
- more flexible interface for __issue_avs_command()
This change makes the function more versatile as it can handle input
and output parameters at the same time.
- Support polling AVS firmware
This change allows the driver to use polling if interrupt driven mode
doesn't work for some reason.
- send S2_ENTER / S2_EXIT commands to AVS
Let the AVS firmware know when we are about to enter, or have just
exited, S2 mode.
Regards,
-Markus
Florian Fainelli (1):
cpufreq: brcmstb-avs-cpufreq: Support polling AVS firmware
Markus Mayer (2):
cpufreq: brcmstb-avs-cpufreq: more flexible interface for
__issue_avs_command()
cpufreq: brcmstb-avs-cpufreq: send S2_ENTER / S2_EXIT commands to AVS
drivers/cpufreq/brcmstb-avs-cpufreq.c | 89 ++++++++++++++++++---------
1 file changed, 59 insertions(+), 30 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-05-28 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200528181921.19846-1-mmayer@broadcom.com \
--to=markus.mayer@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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