RE: Query: Regulator framework in EHCI driver

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

 



Mark Brown:
> On Wed, Nov 04, 2009 at 08:15:02PM +0530, Gadiyar, Anand wrote:
> 
> > So, if a board does not need a regulator at all, then the APIs do nothing?
> 
> If the kernel is built without regulator API support then the get,
> release, enable and disable functions are stubbed out to always report
> success.  If the kernel has been built with regulator support then
> generally a fixed voltage regulator should be defined by the board.  The
> expectation is that if the regulator API is of no use on a board since
> there are no regulators set up then it'll be disabled in Kconfig.
> 

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?
--
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