public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: dts: augment Ux500 to use DT cpufreq
Date: Wed, 16 Aug 2017 08:56:56 +0530	[thread overview]
Message-ID: <20170816032656.GC4233@vireshk-i7> (raw)
In-Reply-To: <CACRpkdZ-7yHA4Xz62K53_XM28pTNf1dNLV42Fo-Jzzx5Y7in8g@mail.gmail.com>

On 13-08-17, 14:23, Linus Walleij wrote:
> On Fri, Aug 11, 2017 at 7:15 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> 
> > For example, below will fail cpufreq on your board. You can try that
> > to make sure I am not dreaming.
> >
> > - Compile cpufreq-dt as a module.
> > - Boot the board.
> > - Offline CPU0 (i.e. Keep only CPU1 online).
> > - Boom, cpufreq failed.
> >
> > This will happen because the CPU1 doesn't have the operating-points
> > and other properties. We should have them in all the CPUs.
> 
> I don't think that will be a problem because CPU0 cannot be
> taken offline on this system.

Should be fine then.

-- 
viresh

  reply	other threads:[~2017-08-16  3:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 12:52 [PATCH 0/4] Switch Ux500 to use generic DT cpufreq Linus Walleij
2017-08-10 12:52 ` [PATCH 1/4] ARM: dts: augment Ux500 to use " Linus Walleij
2017-08-11  5:15   ` Viresh Kumar
2017-08-13 12:23     ` Linus Walleij
2017-08-16  3:26       ` Viresh Kumar [this message]
2017-08-10 12:52 ` [PATCH 2/4] cpufreq: enable the DT cpufreq driver on the Ux500 Linus Walleij
2017-08-11  5:17   ` Viresh Kumar
2017-08-10 12:52 ` [PATCH 3/4] mfd: db8500-prcmu: Get rid of cpufreq dependency Linus Walleij
2017-08-14  7:07   ` Lee Jones
2017-08-16  8:16     ` Linus Walleij
2017-08-16 11:27       ` Lee Jones
2017-08-10 12:52 ` [PATCH 4/4] cpufreq: dbx500: Delete obsolete driver Linus Walleij
2017-08-11  5:17   ` Viresh Kumar

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=20170816032656.GC4233@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --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