linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: imx: add cpufreq support for i.mx6sx
Date: Thu, 26 Jun 2014 11:21:40 +0800	[thread overview]
Message-ID: <20140626032139.GO2224@dragon> (raw)
In-Reply-To: <CAOMZO5AzgcavwQMW=41eWJVBiZ+5onJWUyQWKwS4NJcvGA5OVw@mail.gmail.com>

On Thu, Jun 26, 2014 at 12:11:37AM -0300, Fabio Estevam wrote:
> On Thu, Jun 26, 2014 at 12:06 AM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Wed, Jun 25, 2014 at 11:53 PM, Anson.Huang at freescale.com
> > <Anson.Huang@freescale.com> wrote:
> >> Hi, Fabio
> >>         I have already sent cpufreq driver patch for review which is supporting i.MX6SX, you may need to add it by yourself if you want to test it, I attached the patch, hope it helps.
> >
> > Thanks. It works fine now.
> 
> Forgot to mention that this error still appears:
> 
> cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)

The driver checks if platform supplies an OPP table by attempting to
call dev_pm_opp_get_opp_count() and check the return.  So there is no
real issue behind this message.

Shawn

  parent reply	other threads:[~2014-06-26  3:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  9:10 [PATCH V2] ARM: imx: add cpufreq support for i.mx6sx Anson Huang
2014-06-25  9:33 ` Viresh Kumar
2014-06-25 16:14 ` Shawn Guo
2014-06-26  1:23 ` Fabio Estevam
2014-06-26  1:55   ` Fabio Estevam
2014-06-26  2:53   ` Anson.Huang at freescale.com
2014-06-26  3:06     ` Fabio Estevam
2014-06-26  3:11       ` Fabio Estevam
2014-06-26  3:15         ` Anson.Huang at freescale.com
2014-06-26  3:21           ` Fabio Estevam
2014-06-26  3:21         ` Shawn Guo [this message]
2014-06-26  5:54   ` Shawn Guo
2014-06-26  7:34     ` Anson.Huang at freescale.com
2014-08-18  5:24     ` Shawn Guo

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=20140626032139.GO2224@dragon \
    --to=shawn.guo@freescale.com \
    --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).