SUPERH platform development
 help / color / mirror / Atom feed
From: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: kzm9g: add REGULATOR settings to kzm9g_defconfig
Date: Tue, 03 Jul 2012 10:31:38 +0000	[thread overview]
Message-ID: <4FF2CA0A.6090306@kmckk.co.jp> (raw)
In-Reply-To: <4FF2C282.5030000@kmckk.co.jp>

Hello, Guennadi

(2012/07/03 19:12), Guennadi Liakhovetski wrote:
> Hello
>
> On Tue, 3 Jul 2012, Tetsuyuki Kobayashi wrote:
>
>> Add REGULATOR settings to kernel config file of kzm9g.
>>
>> Signed-off-by: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
>> ---
>> Hello,
>>
>> I found Guennadi's
>> "ARM: mach-shmobile: add fixed voltage regulators to kzm9g"
>> requires REGULATOR setting in kernel config.
>> Without this, it causes these errors at boot time.
>
> Thanks for the patch. However, I think, this error will only appear if you
> enable REGULATOR in the kernel, but both REGULATOR_FIXED_VOLTAGE and
> REGULATOR_DUMMY are disabled. To fix this fixing the defconfig is good,

Oh yes, you are right. I made bad combination as you said.
if CONFIG_REGULATOR is not set, it goes well as before.

> but not sufficient, I think. How about adding something like
>
> 	select REGULATOR_FIXED_VOLTAGE if REGULATOR
>
> to either the CPU or the arch section in respective Kconfig? I would
> actually propose to add these to both arm/mach-shmobile and sh. Any
> objections?
>

Thank you.
I withdraw my config patch and wait for your proposal to Kconfig.



  parent reply	other threads:[~2012-07-03 10:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  9:59 [PATCH] ARM: shmobile: kzm9g: add REGULATOR settings to kzm9g_defconfig Tetsuyuki Kobayashi
2012-07-03 10:06 ` Mark Brown
2012-07-03 10:12 ` Guennadi Liakhovetski
2012-07-03 10:31 ` Tetsuyuki Kobayashi [this message]
2012-07-03 11:15 ` Tetsuyuki Kobayashi
2012-07-03 12:44 ` Guennadi Liakhovetski
2012-07-03 13:22 ` Mark Brown
2012-07-03 13:44 ` Guennadi Liakhovetski
2012-07-03 14:45 ` Mark Brown
2012-07-03 15:05 ` Guennadi Liakhovetski
2012-07-03 15:06 ` Mark Brown
2012-07-03 15:35 ` Guennadi Liakhovetski
2012-07-03 19:33 ` Mark Brown
2012-07-04  6:39 ` Guennadi Liakhovetski
2012-07-04 10:38 ` Mark Brown
2012-07-04 10:40 ` Rafael J. Wysocki
2012-07-04 10:41 ` Magnus Damm
2012-07-04 10:46 ` Paul Mundt
2012-07-04 10:48 ` Mark Brown
2012-07-04 10:51 ` Guennadi Liakhovetski
2012-07-04 10:53 ` Guennadi Liakhovetski
2012-07-04 10:55 ` Rafael J. Wysocki
2012-07-04 10:58 ` Magnus Damm
2012-07-04 11:00 ` Magnus Damm
2012-07-04 11:05 ` Guennadi Liakhovetski
2012-07-04 11:08 ` Guennadi Liakhovetski
2012-07-04 11:22 ` Rafael J. Wysocki
2012-07-04 13:31 ` Magnus Damm
2012-07-04 14:29 ` Mark Brown

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=4FF2CA0A.6090306@kmckk.co.jp \
    --to=koba@kmckk.co.jp \
    --cc=linux-sh@vger.kernel.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