From: Florian Fainelli <f.fainelli@gmail•com>
To: Markus Mayer <markus.mayer@broadcom•com>,
"Rafael J. Wysocki" <rjw@rjwysocki•net>,
Viresh Kumar <viresh.kumar@linaro•org>,
Florian Fainelli <f.fainelli@gmail•com>
Cc: Broadcom Kernel List <bcm-kernel-feedback-list@broadcom•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
ARM Kernel List <linux-arm-kernel@lists•infradead.org>,
Linux Power Management List <linux-pm@vger•kernel.org>
Subject: Re: [PATCH 1/3] cpufreq: brcmstb-avs-cpufreq: more flexible interface for __issue_avs_command()
Date: Fri, 29 May 2020 14:13:24 -0700 [thread overview]
Message-ID: <35e51785-e5f2-792f-321e-e083572a21b5@gmail.com> (raw)
In-Reply-To: <20200528182014.20021-1-mmayer@broadcom.com>
On 5/28/20 11:20 AM, Markus Mayer wrote:
> We are changing how parameters are passed to __issue_avs_command(), so we
> can pass input *and* output arguments with the same command, rather than
> just one or the other.
>
> Signed-off-by: Markus Mayer <mmayer@broadcom•com>
Acked-by: Florian Fainelli <f.fainelli@gmail•com>
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-29 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 18:20 [PATCH 1/3] cpufreq: brcmstb-avs-cpufreq: more flexible interface for __issue_avs_command() Markus Mayer
2020-05-28 18:20 ` [PATCH 2/3] cpufreq: brcmstb-avs-cpufreq: Support polling AVS firmware Markus Mayer
2020-05-28 18:20 ` [PATCH 3/3] cpufreq: brcmstb-avs-cpufreq: send S2_ENTER / S2_EXIT commands to AVS Markus Mayer
2020-05-29 21:13 ` Florian Fainelli
2020-05-29 21:13 ` Florian Fainelli [this message]
2020-06-15 6:05 ` [PATCH 1/3] cpufreq: brcmstb-avs-cpufreq: more flexible interface for __issue_avs_command() Viresh Kumar
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=35e51785-e5f2-792f-321e-e083572a21b5@gmail.com \
--to=f.fainelli@gmail$(echo .)com \
--cc=bcm-kernel-feedback-list@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=markus.mayer@broadcom$(echo .)com \
--cc=rjw@rjwysocki$(echo .)net \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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