From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 6/9] ARM: mxs: Provide regulator to pwm-backlight
Date: Wed, 20 Mar 2013 09:23:18 +0100 [thread overview]
Message-ID: <20130320082318.GA28775@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5148E252.9050900@wwwdotorg.org>
On Tue, Mar 19, 2013 at 04:10:26PM -0600, Stephen Warren wrote:
> On 03/19/2013 03:27 PM, Marek Vasut wrote:
> > Do we really need a mandatory regulator? Why can't it be optional?
> IIRC, the previous advice I've seen is that if a device (driver) uses a
> regulator, it must /require/ a regulator, and if a particular board
> doesn't actually have a SW-controlled regulator, then a fixed- or dummy-
> regulator should be provided to satisfy this requirement.
> CC'ing Mark Brown to make sure I really do Recall Correctly.
Yes, and it should be fixed rather than dummy. The issue is partly that
it's probably important that the device has power so we don't want to
just ignore errors and partly that this is something which applies to
essentially all devices so whatever we do for this case ought to be done
by the core so all devices can benefit and we don't have to duplicate
lots of code in individual drivers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130320/4d5a045b/attachment-0001.sig>
next prev parent reply other threads:[~2013-03-20 8:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 18:59 [PATCH V4 0/9] Add mandatory regulator for all users of pwm-backlight Andrew Chew
2013-03-19 18:59 ` [PATCH V4 1/9] ARM: OMAP: board-4430sdp: Provide regulator to pwm-backlight Andrew Chew
2013-03-19 18:59 ` [PATCH V4 2/9] ARM: S3C24XX: " Andrew Chew
2013-03-19 18:59 ` [PATCH V4 3/9] ARM: pxa: " Andrew Chew
2013-03-19 18:59 ` [PATCH V4 4/9] ARM: EXYNOS: " Andrew Chew
2013-03-19 18:59 ` [PATCH V4 5/9] unicore32: " Andrew Chew
2013-03-19 18:59 ` [PATCH V4 6/9] ARM: mxs: " Andrew Chew
2013-03-19 21:27 ` Marek Vasut
2013-03-19 21:31 ` Andrew Chew
2013-03-19 21:35 ` Marek Vasut
2013-03-19 22:10 ` Stephen Warren
2013-03-20 8:23 ` Mark Brown [this message]
2013-03-20 14:03 ` Marek Vasut
2013-03-20 3:13 ` Shawn Guo
2013-03-19 18:59 ` [PATCH V4 7/9] ARM: vt8500: " Andrew Chew
2013-03-20 18:18 ` [Bulk] " Tony Prisk
2013-03-19 18:59 ` [PATCH V4 8/9] ARM: tegra: " Andrew Chew
2013-03-21 20:01 ` Stephen Warren
2013-03-22 10:29 ` Thierry Reding
2013-03-19 18:59 ` [PATCH V4 9/9] pwm_bl: Add mandatory backlight enable regulator Andrew Chew
2013-03-20 18:00 ` Stephen Warren
2013-03-20 22:19 ` Thierry Reding
2013-03-20 2:14 ` [PATCH V4 0/9] Add mandatory regulator for all users of pwm-backlight Shawn Guo
2013-03-20 2:24 ` Alex Courbot
2013-03-20 3:08 ` Shawn Guo
2013-03-20 7:13 ` Tony Prisk
2013-03-22 1:57 ` Alex Courbot
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=20130320082318.GA28775@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).