All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Ulf Hansson <ulf.hansson@stericsson.com>
Cc: Linus WALLEIJ <linus.walleij@stericsson.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	Per FORLIN <per.forlin@stericsson.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Pawel Moll <pawel.moll@arm.com>
Subject: Re: [PATCH] mmc: mmci: assume maintainership
Date: Sat, 17 Mar 2012 08:58:09 +0000	[thread overview]
Message-ID: <20120317085809.GD17243@flint.arm.linux.org.uk> (raw)
In-Reply-To: <4F6306DC.5090601@stericsson.com>

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:

  reply	other threads:[~2012-03-17  8:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 14:30 [PATCH] mmc: mmci: assume maintainership Linus Walleij
2012-03-15 14:36 ` Ulf Hansson
2012-03-15 14:36 ` Per Förlin
2012-03-15 14:52 ` Pawel Moll
2012-03-15 17:30 ` Russell King
2012-03-15 17:42   ` Linus Walleij
2012-03-16  8:48   ` Ulf Hansson
2012-03-16  8:53     ` Russell King
2012-03-16  9:24       ` Ulf Hansson
2012-03-17  8:58         ` Russell King [this message]
2012-04-09 22:44   ` Chris Ball

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120317085809.GD17243@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=cjb@laptop.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=per.forlin@stericsson.com \
    --cc=ulf.hansson@stericsson.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.