From: Markus Mayer <markus.mayer@broadcom.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
Device Tree List <devicetree@vger.kernel.org>,
Power Management List <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] cpufreq: brcmstb-avs-cpufreq: AVS CPUfreq driver for Broadcom STB SoCs
Date: Wed, 12 Oct 2016 09:08:24 -0700 [thread overview]
Message-ID: <CAGt4E5uV4y3mKarxNL1hjYAZSu02H6eHdRTCRgc-U03hb5ApLw@mail.gmail.com> (raw)
In-Reply-To: <20161012053842.GF19385@vireshk-i7>
On 11 October 2016 at 22:38, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 07-10-16, 16:21, Markus Mayer wrote:
>> +static int brcm_avs_cpufreq_exit(struct cpufreq_policy *policy)
>> +{
>> + struct private_data *priv = policy->driver_data;
>> +
>> + iounmap(priv->base);
>> + iounmap(priv->avs_intr_base);
>> +
>> + return 0;
>> +}
>
> Shouldn't the above be done in the below routine instead ?
Good point. I'll move it.
>> +static int brcm_avs_cpufreq_remove(struct platform_device *pdev)
>> +{
>> + platform_set_drvdata(pdev, NULL);
>> +
>> + return cpufreq_unregister_driver(&brcm_avs_driver);
>> +}
>
> --
> viresh
next prev parent reply other threads:[~2016-10-12 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 23:21 [PATCH v3 0/3] Broadcom STB AVS CPUfreq driver Markus Mayer
[not found] ` <1475882487-2155-1-git-send-email-mmayer-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-10-07 23:21 ` [PATCH v3 1/3] dt: cpufreq: brcm: New binding document for brcmstb-avs-cpufreq Markus Mayer
2016-10-07 23:21 ` [PATCH v3 2/3] cpufreq: brcmstb-avs-cpufreq: AVS CPUfreq driver for Broadcom STB SoCs Markus Mayer
[not found] ` <1475882487-2155-3-git-send-email-mmayer-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-10-12 5:38 ` Viresh Kumar
2016-10-12 16:08 ` Markus Mayer [this message]
2016-10-07 23:21 ` [PATCH v3 3/3] cpufreq: brcmstb-avs-cpufreq: add debugfs support Markus Mayer
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=CAGt4E5uV4y3mKarxNL1hjYAZSu02H6eHdRTCRgc-U03hb5ApLw@mail.gmail.com \
--to=markus.mayer@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).