Re: omap3: regulator_get() failure in ads7846

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 07, 2010 at 03:16:21PM +0300, Igor Grinberg wrote:

> I think, this can help:
> http://www.spinics.net/lists/arm-kernel/msg94759.html

> Seems like there were not enough interest and it is still floating.
> May be a little ping can help ;)

This is a really bad idea unless the supplies genuinely are optional -
we shouldn't be doing this sort of bodge in the drivers, that's just
going to lead to lots of repetitive code adding complexity every time
the regulator API is used.  It also makes the error handling rather more
obscure since systems that genuinely need the regulator won't be
reporting problems clearly.

The regulator API has facilties on several levels to deal with systems
that have problems here: it provides fixed voltage regulators, it
provides the option to substitute in dummy regulators automatically and
if the regulator API is disabled then the stub functions provided will
report success.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux