All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	Joonyoung Shim <jy0922.shim@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Myungjoo Ham <myungjoo.ham@samsung.com>,
	Ben Dooks <ben-linux@fluff.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 3/3] ARM: S5PV210: Add voltage consumer of WM8994 to	the regulator framework
Date: Mon, 04 Oct 2010 21:50:04 +0900	[thread overview]
Message-ID: <4CA9CD7C.5080907@samsung.com> (raw)
In-Reply-To: <20101001182752.GD21157@opensource.wolfsonmicro.com>

Mark Brown wrote:
> On Fri, Oct 01, 2010 at 05:25:43PM +0900, Kyungmin Park wrote:
>> On Fri, Oct 1, 2010 at 4:24 PM, Mark Brown
> 
>>> It's still good to show the actual connection on the board for clarity -
>>> like I say, the regulator API can handle always on regulators and
>>> keeping the regulator setup in software close to the schematic helps
>>> make the code easier to follow.
> 
>> It's best but in most case schematic is confidential. so it's impossible.
> 
> Right, this is normal - even with widely available reference boards the
> schematics are often distributed only under NDA.  Since the information
> exposed is at the same level as describing where the devices are on
> buses and so on this isn't usually a problem.
> 
>> And as you concerns there's no power issues related with codes. it's
>> already verified design. I think wolfsonmicro already confirmed.
> 
> Using a fixed voltage regulator won't cause a problem in operation, the
> issue is one of code quality.

Hi, Mark.

Do you have additional comment on this patch?

Best Regards,
Chanwoo Choi

WARNING: multiple messages have this Message-ID (diff)
From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: S5PV210: Add voltage consumer of WM8994 to	the regulator framework
Date: Mon, 04 Oct 2010 21:50:04 +0900	[thread overview]
Message-ID: <4CA9CD7C.5080907@samsung.com> (raw)
In-Reply-To: <20101001182752.GD21157@opensource.wolfsonmicro.com>

Mark Brown wrote:
> On Fri, Oct 01, 2010 at 05:25:43PM +0900, Kyungmin Park wrote:
>> On Fri, Oct 1, 2010 at 4:24 PM, Mark Brown
> 
>>> It's still good to show the actual connection on the board for clarity -
>>> like I say, the regulator API can handle always on regulators and
>>> keeping the regulator setup in software close to the schematic helps
>>> make the code easier to follow.
> 
>> It's best but in most case schematic is confidential. so it's impossible.
> 
> Right, this is normal - even with widely available reference boards the
> schematics are often distributed only under NDA.  Since the information
> exposed is at the same level as describing where the devices are on
> buses and so on this isn't usually a problem.
> 
>> And as you concerns there's no power issues related with codes. it's
>> already verified design. I think wolfsonmicro already confirmed.
> 
> Using a fixed voltage regulator won't cause a problem in operation, the
> issue is one of code quality.

Hi, Mark.

Do you have additional comment on this patch?

Best Regards,
Chanwoo Choi

  reply	other threads:[~2010-10-04 12:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  4:23 [PATCH 3/3] ARM: S5PV210: Add voltage consumer of WM8994 to the regulator framework Chanwoo Choi
2010-10-01  4:23 ` Chanwoo Choi
2010-10-01  5:31 ` Mark Brown
2010-10-01  5:31   ` Mark Brown
2010-10-01  5:40   ` Kyungmin Park
2010-10-01  5:40     ` Kyungmin Park
2010-10-01  7:24     ` Mark Brown
2010-10-01  7:24       ` Mark Brown
2010-10-01  8:25       ` Kyungmin Park
2010-10-01  8:25         ` Kyungmin Park
2010-10-01 18:27         ` Mark Brown
2010-10-01 18:27           ` Mark Brown
2010-10-04 12:50           ` Chanwoo Choi [this message]
2010-10-04 12:50             ` Chanwoo Choi
2010-10-04 15:17             ` Mark Brown
2010-10-04 15:17               ` Mark Brown
2010-10-14  0:37 ` Kukjin Kim
2010-10-14  0:37   ` Kukjin Kim

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=4CA9CD7C.5080907@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jy0922.shim@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=kmpark@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=myungjoo.ham@samsung.com \
    /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.