Re: [PATCH RESEND] ARM: tegra: set regulator full constraints

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

 



On 11/13/2013 12:07 PM, Mark Brown wrote:
> On Wed, Nov 13, 2013 at 10:29:07AM -0700, Stephen Warren wrote:
> 
>> It seems slightly odd to tightly link the drivers/of and 
>> drivers/regulator code like that, but I guess with the
>> appropriate ifdefs it'll work out OK.
> 
> This isn't really regulator specific - it's something that applies
> in general to things implementing deferred probing - so we ought to
> have a generic "we know if devices can appear later or not" flag
> that subsystems can check.

I guess I misunderstand then, since given that modules exist, wouldn't
that flag always be true?

IIUC, the issue being discussed here isn't about deferred probe at
all. You always must defer probe if an object is specified as existing
yet the provider isn't available yet. The issue here is when a
regulator isn't specified as existing, yet something asks for that
regulator, should the regulator subsystem automatically provide a
dummy regulator instead, rather than erroring out.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [ARM Kernel]     [Linux ARM]     [Linux ARM MSM]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux