Re: [PATCH] mmc: mmci: assume maintainership

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

 



On Fri, Mar 16, 2012 at 10:24:44AM +0100, Ulf Hansson wrote:
> On 03/16/2012 09:53 AM, Russell King wrote:
>> On Fri, Mar 16, 2012 at 09:48:07AM +0100, Ulf Hansson wrote:
>>> Although, right know I would vote for having a more active maintainer
>>> for MMCI; please no offense Russell, I realize that your are fully
>>> occupied with a lot of other cool stuff. I think Linus could play a
>>> great role in this; especially since he also will be able to test
>>> patches on many different ARM boards.
>>
>> No, I explained why I haven't applied your other patches, and I explained
>> at the time my concerns with your patches which zero out and restore the
>> power and clock registers.  I repeated those concerns several times but
>> the issue never got resolved.
>>
>> So that gives me no other option than to slow down applying your patches.
>> It's not that I'm not being responsive.  It's that I'm purposely being
>> slow over these changes because comments on the patches don't seem to be
>> hitting home.
>>
>
> Then I totally misunderstood you. I did send you an explanation to why  
> the registers could be zeroed out, which you did not respond to.

Yes, because you completely misunderstood what I said to you.  I showed
you with extracts from the code what happens on suspend - the IOS
handler will be called to turn power off unless mmc_card_keep_power()
is set (which only a very few SDIO cards would set.)

You replied saying that if the IOS handler is called, the card power and
clock will be cut.  Yes, we both agree with that, that's not what I'm
trying to discuss.  What I'm trying to find out is why you want to save
the power and clock registers after that's happened, zero them, and then
simply restore them on resume.

When you can properly explain that, it may be that a better solution is
to fix the core such when mmc_card_keep_power() is set, it really does
only stop the power being cut on suspend, but still results in the core
asking for the clock to be stopped.

> Moreover, I did not receive any comments/acks on the other patches. Are  
> you only looking at the first one in a patch series or do you mean that  
> the other onces looks OK?

No idea, it's been such a long time since I looked at them that I've long
forgotten what I thought about the remainder.  What I do know is that I
could not apply any further patches without the one which is under
discussion.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


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

  Powered by Linux