On 11/28/11 12:07, Eliad Peller wrote:
> On Mon, Nov 28, 2011 at 12:01 PM, Igor Grinberg
> wrote:
>> On 11/28/11 11:23, Eliad Peller wrote:
>>> hi Igor,
>>>
>>> On Mon, Nov 28, 2011 at 11:15 AM, Igor Grinberg
>>> wrote:
On 11/22/11 16:02, Eliad Peller wrote:
> Add pm_caps field to omap
On Mon, Nov 28, 2011 at 12:01 PM, Igor Grinberg wrote:
> On 11/28/11 11:23, Eliad Peller wrote:
>> hi Igor,
>>
>> On Mon, Nov 28, 2011 at 11:15 AM, Igor Grinberg
>> wrote:
>>> On 11/22/11 16:02, Eliad Peller wrote:
Add pm_caps field to omap2_hsmmc_info and omap_mmc_slot_data
structs, s
On 11/28/11 11:23, Eliad Peller wrote:
> hi Igor,
>
> On Mon, Nov 28, 2011 at 11:15 AM, Igor Grinberg
> wrote:
>> On 11/22/11 16:02, Eliad Peller wrote:
>>> Add pm_caps field to omap2_hsmmc_info and omap_mmc_slot_data
>>> structs, so we will be able to indicate mmc pm capabilities
>>> in the boa
hi Igor,
On Mon, Nov 28, 2011 at 11:15 AM, Igor Grinberg wrote:
> On 11/22/11 16:02, Eliad Peller wrote:
>> Add pm_caps field to omap2_hsmmc_info and omap_mmc_slot_data
>> structs, so we will be able to indicate mmc pm capabilities
>> in the board file.
>
> Shouldn't this be user space runtime co
Hi Eliad,
On 11/22/11 16:02, Eliad Peller wrote:
> Add pm_caps field to omap2_hsmmc_info and omap_mmc_slot_data
> structs, so we will be able to indicate mmc pm capabilities
> in the board file.
Shouldn't this be user space runtime controllable?
Instead of being a static per board decision?
>
>
Add pm_caps field to omap2_hsmmc_info and omap_mmc_slot_data
structs, so we will be able to indicate mmc pm capabilities
in the board file.
Signed-off-by: Eliad Peller
---
arch/arm/mach-omap2/hsmmc.c |1 +
arch/arm/mach-omap2/hsmmc.h |1 +
arch/arm/plat-omap/include/p
