From: Stefan Wahren <info@lategoodbye.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
Otavio Salvador <otavio@ossystems.com.br>,
linux-arm-kernel@lists.infradead.org, cpufreq@vger.kernel.org
Subject: Re: ARM: mx28: cpufreq-cpu0 support?
Date: Mon, 25 Aug 2014 12:30:25 +0200 [thread overview]
Message-ID: <53FB1041.5010208@lategoodbye.de> (raw)
In-Reply-To: <20140825080123.GA12289@dragon>
Am 25.08.2014 10:01, schrieb Shawn Guo:
> On Sun, Aug 24, 2014 at 11:47:43AM +0200, Stefan Wahren wrote:
>> Hi,
>>
>> could you please tell me, is i.MX28 supported by cpufreq-cpu0?
>>
>> Do we need only the necessary DT entries like operating points or is
>> it more?
>
> Clock might as simple as adding DT entries, but I'm not sure we have
> voltage scaling support for i.MX28 in kernel.
>
> Shawn
>
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.
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, 25 Aug 2014 12:30:25 +0200 [thread overview]
Message-ID: <53FB1041.5010208@lategoodbye.de> (raw)
In-Reply-To: <20140825080123.GA12289@dragon>
Am 25.08.2014 10:01, schrieb Shawn Guo:
> On Sun, Aug 24, 2014 at 11:47:43AM +0200, Stefan Wahren wrote:
>> Hi,
>>
>> could you please tell me, is i.MX28 supported by cpufreq-cpu0?
>>
>> Do we need only the necessary DT entries like operating points or is
>> it more?
>
> Clock might as simple as adding DT entries, but I'm not sure we have
> voltage scaling support for i.MX28 in kernel.
>
> Shawn
>
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.
Stefan
next prev parent reply other threads:[~2014-08-25 10:30 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 [this message]
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
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=53FB1041.5010208@lategoodbye.de \
--to=info@lategoodbye.de \
--cc=cpufreq@vger.kernel.org \
--cc=fabio.estevam@freescale.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.