From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Vasily Khoruzhick' <anarsoul@gmail.com>,
linux-arm-kernel@lists.infradead.org,
'MyungJoo Ham' <myungjoo.ham@samsung.com>,
linux-samsung-soc@vger.kernel.org,
'Russell King' <linux@arm.linux.org.uk>,
'Jassi Brar' <jassi.brar@samsung.com>,
'Kyungmin Park' <kyungmin.park@samsung.com>,
myungjoo.ham@gmail.com, 'Ben Dooks' <ben-linux@fluff.org>,
'Seungwhan Youn' <sw.youn@samsung.com>,
'Changhwan Youn' <chaos.youn@samsung.com>,
'Marek Szyprowski' <m.szyprowski@samsung.com>
Subject: Re: [PATCH v3 1/6] Samsung SoC ADC: use regulator (VDD for ADC).
Date: Tue, 19 Jul 2011 16:40:03 +0100 [thread overview]
Message-ID: <20110719154003.GK9652@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <037301cc4376$3d7f5a20$b87e0e60$%kim@samsung.com>
On Sat, Jul 16, 2011 at 02:07:13PM +0900, Kukjin Kim wrote:
> Mark Brown wrote:
> > If there isn't a separate supply for the regulators on S3C24xx devices
> > then I guess the best option is to provide that supply as a dummy
> > regulator in the s3c24xx core code.
> OK, but it means I can't apply this until adding a dummy regulator for
> S3C24XX?
That could always come later as a bug fix :) The regulator API does
have a couple of methods of substituting in a dummy regulator itself,
though it does complain a bit, so it should mostly be a simple config
change to work around on affected systems.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/6] Samsung SoC ADC: use regulator (VDD for ADC).
Date: Tue, 19 Jul 2011 16:40:03 +0100 [thread overview]
Message-ID: <20110719154003.GK9652@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <037301cc4376$3d7f5a20$b87e0e60$%kim@samsung.com>
On Sat, Jul 16, 2011 at 02:07:13PM +0900, Kukjin Kim wrote:
> Mark Brown wrote:
> > If there isn't a separate supply for the regulators on S3C24xx devices
> > then I guess the best option is to provide that supply as a dummy
> > regulator in the s3c24xx core code.
> OK, but it means I can't apply this until adding a dummy regulator for
> S3C24XX?
That could always come later as a bug fix :) The regulator API does
have a couple of methods of substituting in a dummy regulator itself,
though it does complain a bit, so it should mostly be a simple config
change to work around on affected systems.
next prev parent reply other threads:[~2011-07-19 15:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 7:49 [PATCH v3 0/6] Update Samsung-SoC ADC to support recent CPUs MyungJoo Ham
2011-06-30 7:49 ` MyungJoo Ham
2011-06-30 7:49 ` [PATCH v3 1/6] Samsung SoC ADC: use regulator (VDD for ADC) MyungJoo Ham
2011-06-30 7:49 ` MyungJoo Ham
2011-06-30 8:22 ` Vasily Khoruzhick
2011-06-30 8:22 ` Vasily Khoruzhick
2011-06-30 8:22 ` Vasily Khoruzhick
2011-06-30 9:03 ` MyungJoo Ham
2011-06-30 9:03 ` MyungJoo Ham
2011-06-30 16:05 ` Mark Brown
2011-06-30 16:05 ` Mark Brown
2011-07-16 5:07 ` Kukjin Kim
2011-07-16 5:07 ` Kukjin Kim
2011-07-19 15:40 ` Mark Brown [this message]
2011-07-19 15:40 ` Mark Brown
2011-07-20 12:23 ` Kukjin Kim
2011-07-20 12:23 ` Kukjin Kim
2011-06-30 7:49 ` [PATCH v3 2/6] Samsung SoC ADC: Channel selection for S5PV210, S5PC110, and Exynos4 MyungJoo Ham
2011-06-30 7:49 ` MyungJoo Ham
2011-06-30 7:49 ` [PATCH v3 3/6] Samsung SoC ADC: Revise PM for 12-bit ADC operations MyungJoo Ham
2011-06-30 7:49 ` MyungJoo Ham
2011-06-30 7:49 ` [PATCH v3 4/6] ARM: EXYNOS4: Support ADC MyungJoo Ham
2011-06-30 7:49 ` MyungJoo Ham
2011-06-30 7:49 ` [PATCH v3 5/6] ARM: S5PC110/S5PV210: " MyungJoo Ham
2011-06-30 7:49 ` MyungJoo Ham
2011-06-30 7:49 ` [PATCH v3 6/6] Samsung SoC: header file revised to prevent declaring duplicated MyungJoo Ham
2011-06-30 7:49 ` MyungJoo Ham
2011-07-20 12:22 ` [PATCH v3 0/6] Update Samsung-SoC ADC to support recent CPUs Kukjin Kim
2011-07-20 12:22 ` 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=20110719154003.GK9652@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anarsoul@gmail.com \
--cc=ben-linux@fluff.org \
--cc=chaos.youn@samsung.com \
--cc=jassi.brar@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=myungjoo.ham@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=sw.youn@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.