linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq for freescale mx51
Date: Thu, 7 Oct 2010 09:50:12 +0200	[thread overview]
Message-ID: <20101007075012.GA28242@pengutronix.de> (raw)
In-Reply-To: <20101007074044.GG2457@matterhorn.lan>

On Thu, Oct 07, 2010 at 10:40:44AM +0300, Amit Kucheria wrote:
> On 10 Oct 07, Yong Shen wrote:
> > 
> > > > +static struct cpufreq_frequency_table imx_freq_table[4];
> > >
> > > Three frequencies should be enough for everyone, right? This should be
> > > dynamically allocated like in other cpufreq drivers.
> > >
> > 
> > Yes, we only support 3 work points, which is for sure. Actually, we only
> > support 2 points on most mx51 chips. I supposed it is ok to use static array
> > here.
> 
> This can become a common cpufreq driver for all i.MX platforms. We don't know
> how many work points will be supported in future versions of the silicon.
> That is why a static array is not ok.
> 
> I think Sascha was being ironic when he said "Three frequencies should be
> enough for everyone, right?" :)

Yes, the old 640k-is-enough-for-anyone joke.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2010-10-07  7:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1285738417-1638-1-git-send-email-yong.shen@linaro.org>
2010-09-30 10:48 ` [PATCH] cpufreq for freescale mx51 Amit Kucheria
2010-10-01  4:06   ` Yong Shen
2010-10-04  7:43     ` Amit Kucheria
2010-10-06  9:51   ` Sascha Hauer
2010-10-07  3:36     ` Yong Shen
2010-10-07  7:30       ` Sascha Hauer
2010-10-07 12:00         ` Yong Shen
2010-10-12  7:11           ` [PATCHv2] " Yong Shen
2010-10-07  7:40       ` [PATCH] " Amit Kucheria
2010-10-07  7:50         ` Sascha Hauer [this message]
2010-10-05 11:58 mx51 cpufreq driver yong.shen at linaro.org
2010-10-05 11:58 ` [PATCH] cpufreq for freescale mx51 yong.shen at linaro.org
2010-10-05 12:25   ` Arnd Bergmann
2010-10-06  5:38     ` Yong Shen
2010-10-06 11:15       ` Arnd Bergmann
2010-10-07  4:10         ` Yong Shen
  -- strict thread matches above, loose matches on Subject: below --
2010-10-07  5:36 mx51 cpufreq driver yong.shen at linaro.org
2010-10-07  5:36 ` [PATCH] cpufreq for freescale mx51 yong.shen at linaro.org
2010-10-07  8:03   ` Amit Kucheria
2010-10-07 11:33     ` Yong Shen
2010-10-07 11:45       ` Amit Kucheria

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=20101007075012.GA28242@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).