From: Balaji Rao <balajirrao@openmoko.org>
To: Mark Brown <broonie@sirena.org.uk>
Cc: linux-kernel@vger.kernel.org, Andy Green <andy@openmoko.com>,
Liam Girdwood <lrg@simlogic.co.uk>
Subject: Re: [PATCH 7/7] regulator: PCF50633 pmic driver
Date: Mon, 15 Dec 2008 19:34:50 +0530 [thread overview]
Message-ID: <20081215140448.GA2625@cff.thadambail> (raw)
In-Reply-To: <20081215113547.GC31145@sirena.org.uk>
On Mon, Dec 15, 2008 at 11:35:49AM +0000, Mark Brown wrote:
> On Sun, Dec 14, 2008 at 04:34:00PM +0530, Balaji Rao wrote:
>
> > +struct regulator_ops pcf50633_regulator_ops = {
> > + .set_voltage = pcf50633_regulator_set_voltage,
> > + .get_voltage = pcf50633_regulator_get_voltage,
> > + .enable = pcf50633_regulator_enable,
> > + .disable = pcf50633_regulator_disable,
> > + .is_enabled = pcf50633_regulator_is_enabled,
> > + .set_suspend_enable = pcf50633_regulator_enable,
> > + .set_suspend_disable = pcf50633_regulator_disable,
> > +};
>
> Are you sure that the suspend variants of the operations should be the
> same as the regular versions?
>
Yes, basically the chip doesn't change state during suspend/resume.
We just enable or disable them the usual way.
> > +struct platform_driver pcf50633_regulator_driver = {
> > + .driver = {
> > + .name = "pcf50633-regltr",
> > + },
> > + .probe = pcf50633_regulator_probe,
> > + .remove = __devexit_p(pcf50633_regulator_remove),
> > +};
>
> Not that it matters too much but I have a hard time liking "regltr".
Ha! The name pcf50633-regulator exceeds 20 chars and there is no space
remaining for the ".0" or ".1" at the end. This gave me a sysfs warning
and so I changed it.
- Balaji
next prev parent reply other threads:[~2008-12-15 14:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 11:01 [PATCH 0/7] PCF50633 support Balaji Rao
2008-12-14 11:02 ` [PATCH 1/7] mfd: PCF50633 core driver Balaji Rao
2008-12-14 11:02 ` [PATCH 2/7] mfd: PCF50633 adc driver Balaji Rao
2008-12-14 11:02 ` [PATCH 3/7] mfd: PCF50633 gpio support Balaji Rao
2008-12-14 11:03 ` [PATCH 4/7] rtc: PCF50633 rtc driver Balaji Rao
2008-12-14 19:29 ` Alessandro Zummo
2008-12-14 22:04 ` Balaji Rao
2008-12-14 22:21 ` [rtc-linux] " Alessandro Zummo
2008-12-14 23:29 ` Balaji Rao
2008-12-14 23:39 ` Alessandro Zummo
2008-12-14 11:03 ` [PATCH 5/7] power_supply: PCF50633 battery charger driver Balaji Rao
2008-12-14 22:10 ` Balaji Rao
2008-12-15 22:38 ` Anton Vorontsov
2008-12-16 15:24 ` Balaji Rao
2008-12-14 11:03 ` [PATCH 6/7] input: PCF50633 input driver Balaji Rao
2008-12-15 7:35 ` Dmitry Torokhov
2008-12-16 15:18 ` Balaji Rao
2008-12-14 11:04 ` [PATCH 7/7] regulator: PCF50633 pmic driver Balaji Rao
2008-12-15 11:35 ` Mark Brown
2008-12-15 14:04 ` Balaji Rao [this message]
2008-12-16 10:27 ` 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=20081215140448.GA2625@cff.thadambail \
--to=balajirrao@openmoko.org \
--cc=andy@openmoko.com \
--cc=broonie@sirena.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@simlogic.co.uk \
/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