public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@stericsson.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Philip Rakity <prakity@marvell.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	David Vrabel <david.vrabel@csr.com>
Subject: Re: [PATCH] mmc: agressive clocking framework v9
Date: Mon, 8 Nov 2010 10:37:31 +0100	[thread overview]
Message-ID: <4CD7C4DB.7070105@stericsson.com> (raw)
In-Reply-To: <AANLkTimWg_EE+hg__b0NW792szvY+4Rc_4XsjbHN_tJv@mail.gmail.com>

Ohad Ben-Cohen wrote:

> So the decision whether to enable clock gating for SDIO should not be
> static (eventually. I'm not saying this is something Linus should take
> care of in his patch, it's up to us to make this work). By default,
> SDIO clock gating should be disabled, but we need to allow drivers to
> explicitly enable it if supported.

I currently (patch v8) disable gating for all SDIO cards,
but I guess there are two approaches to cases where you'd
like to enable it:

- Card (including SDIO device) whitelisting.

- Host whitelisting - for the case where as gateable SDIO
  device is soldered to the bus.

The first looks like big-ish so would be a separate patch, but a
host flag for the latter like MMC_CAP_GATE_SDIO can easily be
folded into a v10 of this patch.

Is that desireable?

Yours,
Linus Walleij

  reply	other threads:[~2010-11-08  9:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06  5:38 [PATCH] mmc: agressive clocking framework v9 Philip Rakity
2010-11-06 17:24 ` Ohad Ben-Cohen
2010-11-06 17:38   ` Philip Rakity
2010-11-07  1:44     ` Nicolas Pitre
2010-11-07 18:18       ` Philip Rakity
2010-11-08  4:33         ` Nicolas Pitre
2010-11-08  9:40         ` Linus Walleij
2010-11-08  9:45           ` Philip Rakity
2010-11-09 10:29           ` Jaehoon Chung
2010-11-09 16:52             ` Linus Walleij
2010-11-07  9:32     ` Ohad Ben-Cohen
2010-11-08  9:37       ` Linus Walleij [this message]
2010-11-08  9:47         ` Philip Rakity
2010-11-08 10:40           ` Linus Walleij
2010-11-08 18:49             ` Nicolas Pitre
2010-11-08 22:06               ` Linus Walleij
2010-11-08 18:47         ` Nicolas Pitre
2010-11-08  9:23 ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2010-11-04 11:16 Linus Walleij
2010-11-04 13:15 ` David Vrabel
2010-11-04 14:25   ` Linus Walleij
2010-11-04 17:01     ` Nicolas Pitre
2010-11-05  8:35       ` Linus Walleij
2010-11-05 10:03         ` Ohad Ben-Cohen
2010-11-04 21:20     ` Ohad Ben-Cohen

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=4CD7C4DB.7070105@stericsson.com \
    --to=linus.walleij@stericsson.com \
    --cc=david.vrabel@csr.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=prakity@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox