Re: Query: Regulator framework in EHCI driver

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

 



On Wed, Nov 04, 2009 at 08:20:46PM +0530, Gadiyar, Anand wrote:

> I meant: for the same driver (say EHCI in this case) on two different
> boards, if one of them needs a particular regulator (say the 1v8 from TWL4030)
> and the other needs none at all (but needs the regulator API in general for
> other devices on the board), then what would happen?

Like I say, if the kernel is built with regulator support then a fixed
voltage regulator should be defined representing the supply if it is
provided by a fixed voltage regulator - if the supply is essential to
the correct operation of the device this will reflect the actual
hardware.

If the supply is genuinely optional and need not be connected for
correct operation of the device then the consumer driver should
gracefully handle failure to acquire the regulator, for example by
disabling functionality that depends on the additional supply, but this
is relatively unusual.
--
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