From: Mark Brown <broonie@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Pi-Cheng Chen <pi-cheng.chen@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Chen Fan <fan.chen@mediatek.com>,
Mike Turquette <mturquette@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Howard Chen <ibanezchen@gmail.com>,
"Joe.C" <yingjoe.chen@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Sascha Hauer <s.hauer@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Eddie Huang <eddie.huang@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ashwin Chaugule <ashwin.chaugule@linaro.org>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v2 3/4] cpufreq: mediatek: add Mediatek cpufreq driver
Date: Wed, 11 Mar 2015 10:53:07 +0000 [thread overview]
Message-ID: <20150311105307.GW28806@sirena.org.uk> (raw)
In-Reply-To: <CAKohpokT7fSniPGX2BfM61AtMoMCxEP8WDtbZ34bozUXscEWyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Tue, Mar 10, 2015 at 08:20:43AM +0530, Viresh Kumar wrote:
Please don't send upstream e-mail to my work account, I use this address
pretty consistently for upstream. Upstream mail to my work account
frequently ends up unread.
> On 6 March 2015 at 11:19, Pi-Cheng Chen <pi-cheng.chen@linaro.org> wrote:
> > On 5 March 2015 at 17:55, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > About putting
> > those stuff into regulator driver, I think you mean creating a
> > "virtual regulator
> > device" and put all the voltage controlling complex into the driver, right?
> > Maybe it's a good idea in this case, but I am sure if this kind of
> > virtual regulator is acceptable.
> @Mark: Is this allowed to create virtual regulator for a CPU ?
I don't really know what the above means or what problem it's supposed
to solve.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-03-11 10:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 8:49 [PATCH v2 0/4] cpufreq: add cpufreq driver for Mediatek MT8173 SoC pi-cheng.chen
2015-03-04 8:49 ` [PATCH v2 1/4] cpufreq-dt: add clock domain and intermediate frequency support pi-cheng.chen
2015-03-04 10:15 ` Viresh Kumar
2015-03-04 10:17 ` Viresh Kumar
2015-03-05 3:32 ` Pi-Cheng Chen
2015-03-05 3:58 ` Viresh Kumar
2015-03-05 7:28 ` Pi-Cheng Chen
2015-03-04 8:49 ` [PATCH v2 2/4] cpufreq: dt-bindings: add bindings for mtk-cpufreq driver pi-cheng.chen
2015-03-04 10:29 ` Viresh Kumar
2015-03-04 8:49 ` [PATCH v2 3/4] cpufreq: mediatek: add Mediatek cpufreq driver pi-cheng.chen
2015-03-04 11:09 ` Viresh Kumar
2015-03-05 7:27 ` Pi-Cheng Chen
2015-03-05 9:55 ` Viresh Kumar
2015-03-06 5:49 ` Pi-Cheng Chen
2015-03-10 2:50 ` Viresh Kumar
2015-03-11 10:53 ` Mark Brown [this message]
2015-03-11 11:03 ` Viresh Kumar
2015-03-11 11:42 ` Lucas Stach
2015-03-11 11:46 ` Viresh Kumar
2015-03-11 12:46 ` Mark Brown
2015-03-11 12:45 ` Mark Brown
2015-03-12 9:28 ` Viresh Kumar
2015-03-12 11:15 ` Pi-Cheng Chen
2015-03-18 6:59 ` Viresh Kumar
2015-03-09 16:28 ` Russell King - ARM Linux
2015-03-10 1:57 ` Pi-Cheng Chen
2015-03-04 8:49 ` [PATCH v2 4/4] ARM64: dts: mediatek: add cpufreq dts for MT8173 SoC pi-cheng.chen
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=20150311105307.GW28806@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ashwin.chaugule@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=fan.chen@mediatek.com \
--cc=galak@codeaurora.org \
--cc=ibanezchen@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@linaro.org \
--cc=pawel.moll@arm.com \
--cc=pi-cheng.chen@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=thomas.petazzoni@free-electrons.com \
--cc=viresh.kumar@linaro.org \
--cc=will.deacon@arm.com \
--cc=yingjoe.chen@mediatek.com \
/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®