From: Stefan Wahren <info@lategoodbye.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Fabio Estevam <fabio.estevam@freescale.com>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: ARM: mx28: cpufreq-cpu0 support?
Date: Mon, 01 Sep 2014 08:31:05 +0200 [thread overview]
Message-ID: <540412A9.4090806@lategoodbye.de> (raw)
In-Reply-To: <CAOMZO5CnuWJ9EaLUW8DYFU1Dzeh=92tux0zoUBKoW-L=VWZhhg@mail.gmail.com>
Hi Fabio,
Am 30.08.2014 19:07, schrieb Fabio Estevam:
> On Sat, Aug 30, 2014 at 2:05 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Stefan,
>>
>> On Mon, Aug 25, 2014 at 7:30 AM, Stefan Wahren <info@lategoodbye.de> wrote:
>>
>>> As far as i know, the old Freescale BSP (2.6.35) contains a cpufreq driver
>>> for mxs, which never goes to mainline. So i'm not sure what would be the
>>> best way: porting the old driver or using cpufreq-cpu0.
>>
>> First step would be to port the PMU driver into mainline.
>
> I mean this regulator driver:
> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/drivers/regulator/mxs-regulator.c?h=imx_2.6.35_maintain
>
> ,so that you can do the voltage scaling.
>
thanks. Okay, that leads to more questions:
How can i test a ported mxs-regulator driver, that it's really working?
Is there any userspace interface?
Is there a good DT implementation of a similiar regulator driver, so i
can orientate on?
What are the recommend mailing lists for this porting (linux-pm and
linux-arm-kernel)?
BR Stefan
WARNING: multiple messages have this Message-ID (diff)
From: info@lategoodbye.de (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: mx28: cpufreq-cpu0 support?
Date: Mon, 01 Sep 2014 08:31:05 +0200 [thread overview]
Message-ID: <540412A9.4090806@lategoodbye.de> (raw)
In-Reply-To: <CAOMZO5CnuWJ9EaLUW8DYFU1Dzeh=92tux0zoUBKoW-L=VWZhhg@mail.gmail.com>
Hi Fabio,
Am 30.08.2014 19:07, schrieb Fabio Estevam:
> On Sat, Aug 30, 2014 at 2:05 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Stefan,
>>
>> On Mon, Aug 25, 2014 at 7:30 AM, Stefan Wahren <info@lategoodbye.de> wrote:
>>
>>> As far as i know, the old Freescale BSP (2.6.35) contains a cpufreq driver
>>> for mxs, which never goes to mainline. So i'm not sure what would be the
>>> best way: porting the old driver or using cpufreq-cpu0.
>>
>> First step would be to port the PMU driver into mainline.
>
> I mean this regulator driver:
> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/drivers/regulator/mxs-regulator.c?h=imx_2.6.35_maintain
>
> ,so that you can do the voltage scaling.
>
thanks. Okay, that leads to more questions:
How can i test a ported mxs-regulator driver, that it's really working?
Is there any userspace interface?
Is there a good DT implementation of a similiar regulator driver, so i
can orientate on?
What are the recommend mailing lists for this porting (linux-pm and
linux-arm-kernel)?
BR Stefan
next prev parent reply other threads:[~2014-09-01 6:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 9:47 ARM: mx28: cpufreq-cpu0 support? Stefan Wahren
2014-08-24 9:47 ` Stefan Wahren
2014-08-25 8:01 ` Shawn Guo
2014-08-25 8:01 ` Shawn Guo
2014-08-25 10:30 ` Stefan Wahren
2014-08-25 10:30 ` Stefan Wahren
2014-08-30 17:05 ` Fabio Estevam
2014-08-30 17:05 ` Fabio Estevam
2014-08-30 17:07 ` Fabio Estevam
2014-08-30 17:07 ` Fabio Estevam
2014-09-01 6:31 ` Stefan Wahren [this message]
2014-09-01 6:31 ` Stefan Wahren
2014-09-01 13:33 ` Fabio Estevam
2014-09-01 13:33 ` Fabio Estevam
2014-09-02 5:09 ` Stefan Wahren
2014-09-02 5:09 ` Stefan Wahren
2014-09-02 13:13 ` Fabio Estevam
2014-09-02 13:13 ` Fabio Estevam
2014-09-22 21:25 ` Stefan Wahren
2014-09-22 21:25 ` Stefan Wahren
2014-09-22 22:18 ` Fabio Estevam
2014-09-22 22:18 ` Fabio Estevam
2014-09-24 20:46 ` Stefan Wahren
2014-09-24 20:46 ` Stefan Wahren
2014-09-24 21:47 ` Fabio Estevam
2014-09-24 21:47 ` Fabio Estevam
2014-09-25 18:24 ` Stefan Wahren
2014-09-25 18:24 ` Stefan Wahren
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=540412A9.4090806@lategoodbye.de \
--to=info@lategoodbye.de \
--cc=cpufreq@vger.kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=otavio@ossystems.com.br \
--cc=shawn.guo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.