Hi, Mark
On Friday, June 17, 2016 07:42 PM, Mark Brown wrote:
> On Fri, Jun 17, 2016 at 11:34:25AM +0800, Pingbo Wen wrote:
>> On Wednesday, June 15, 2016 09:32 PM, Mark Brown wrote:
>
>>> Having the consumer driver know that it's "critical" seems wrong since
>>> different systems may have differ
On Fri, Jun 17, 2016 at 11:34:25AM +0800, Pingbo Wen wrote:
> On Wednesday, June 15, 2016 09:32 PM, Mark Brown wrote:
> > Having the consumer driver know that it's "critical" seems wrong since
> > different systems may have different ideas about that, it's probably
> > better to hook this in with
On Wednesday, June 15, 2016 09:32 PM, Mark Brown wrote:
> On Wed, Jun 15, 2016 at 08:05:13PM +0800, Pingbo Wen wrote:
>> On Thursday, June 09, 2016 01:16 AM, Mark Brown wrote:
>
>> If we take modules under consideration, and to make this patch more
>> universal, I think what we really need is add
On Wed, Jun 15, 2016 at 08:05:13PM +0800, Pingbo Wen wrote:
> On Thursday, June 09, 2016 01:16 AM, Mark Brown wrote:
> > It doesn't, it postpones them until late_initacall(). This is both
> > after the consumers have loaded if they are built in and before any
> > consumers built as modules come u
Hi, Mark
On Thursday, June 09, 2016 01:16 AM, Mark Brown wrote:
> On Mon, May 09, 2016 at 03:05:08PM +0800, WEN Pingbo wrote:
>
>> And regulator core will postpone all operations until all consumers
>> have taked their place.
>
> It doesn't, it postpones them until late_initacall(). This is bot
On Mon, May 09, 2016 at 03:05:08PM +0800, WEN Pingbo wrote:
> In some platforms, critical shared regulator is initialized in
> bootloader. But during kernel booting, the driver probing order and
> conflicting operations from other regulator consumers, may set the
> regulator in a undefined state,
6 matches
Mail list logo
