From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH] mmc: agressive clocking framework v9 Date: Mon, 8 Nov 2010 10:37:31 +0100 Message-ID: <4CD7C4DB.7070105@stericsson.com> References: <43E4817426ED174AA81263BCECB4351D131D9D41BC@sc-vexch3.marvell.com> <041757E8-9FCD-4FA8-8079-7A3FC07E4038@marvell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from eu1sys200aog109.obsmtp.com ([207.126.144.127]:50499 "EHLO eu1sys200aog109.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751684Ab0KHJh4 (ORCPT ); Mon, 8 Nov 2010 04:37:56 -0500 In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Ohad Ben-Cohen Cc: Philip Rakity , "linux-mmc@vger.kernel.org" , David Vrabel 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