All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@stericsson.com>
To: Philip Rakity <prakity@marvell.com>
Cc: Ohad Ben-Cohen <ohad@wizery.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 11:40:21 +0100	[thread overview]
Message-ID: <4CD7D395.8040804@stericsson.com> (raw)
In-Reply-To: <C771C677-E21B-41FC-ABEE-DBEFEFA8569D@marvell.com>

Philip Rakity wrote:
> On Nov 8, 2010, at 1:37 AM, Linus Walleij wrote:
>> - Card (including SDIO device) whitelisting.
> 
> do not understand the term whitelisting ..  please explain.

The idea would be to have a database with ID:s for cards
that may be gated. Any SDIO card not it this list would
not be gated.

>> - 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.
> 
> Nico was not in favor of this.  He thought it best to have
> the core/ layer handle this.

My patch is indeed to the core?

This was to be a flag for explicitly letting the core
gate some specific hosts on the MMC bus, in the case
where you (when defining platform data) already know that
a gateable SDIO card was soldered hardly onto a certain
host.

Anyway, if we have such needs they can be fixed later.

Yours,
Linus Walleij

  reply	other threads:[~2010-11-08 10:40 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
2010-11-08  9:47         ` Philip Rakity
2010-11-08 10:40           ` Linus Walleij [this message]
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=4CD7D395.8040804@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 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.