On 14 September 2012 14:49, Ulf Hansson <[email protected]> wrote:
> On 14 September 2012 10:25, Girish K S <[email protected]>
> wrote:
>> On 14 September 2012 12:37, Ulf Hansson <[email protected]> wrote:
>>> Hi Girish,
>>>
>>> I should also have stated that this patch has not been tested with an
>>> eMMC 4.5 device, thus the power off notification is not fully tested.
>>> Unfortunate I don't have such a device available right now. What I did
>>> test was that patch must not break anything and tested that the
>>> suspend/resume sequence is fixed for eMMC with sleep support. I also
>>> tested this with MMC_CAP2_POWEROFF_NOTIFY enabled.
>>>
>>> Are you able to help out in testing with a eMMC 4.5 device with
>>> POWER_OFF_NOTIFY support?
>> I am also facing the same problem. The board that i used earlier to
>> upstream 4.5 patches is not functioning. Thats the reason for the
>> delay in upstreaming or sending the patch. Once i get it repaired i ll
>> definitely do it.
>> It would be helpful if somebody in the list can do this in the mean time.
>
> Ah, I see.
>
> If not possible to test soon, I anyway think we should go ahead with
> this patch, since it fixes the supend/resume sequence for eMMC with
> sleep, which to me is far more important right know, it has been
> broken for several month now. If there are any issues with power off
> notify feature, we can fix that later on. What do you think of that
> approach?
OK i do agree with it.
you can add my signoff or ack for this
>
> Kind regards
> Ulf Hansson
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
