Re: [PATCH 1/3] mmc: replacing hardcoded value for runtime PM suspend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



在 2016/10/13 15:36, Ulf Hansson 写道:
On 4 September 2016 at 15:30, Alex Lemberg <Alex.Lemberg@xxxxxxxxxxx> wrote:
Hi Shawn,

On 9/2/16, 10:39 AM, "Shawn Lin" <shawn.lin@xxxxxxxxxxxxxx> wrote:

Hi

On 2016/9/1 22:24, alex lemberg wrote:
Add MMC_AUTOSUSPEND_DELAY_MS define

I'm thinking should we expose it to userspace
via sysfs, since I don't know why it should be 3ms, not 4ms, 5ms, etc.

Agree, we can consider exposing it to the user space.
The exposure to the user space is less critical to the current
patchset, but we can do it as a “follow-up change” once its approved.

No need for that, is already available for user-space. :-)

Each device with runtime PM autosuspend enabled, allows userspace to
change the delay via the "autosuspend_delay_ms" sysfs file.

Indeed, I just check it when enabling runtime PM for dw_mmc and could
able to change the value of autosuspend_delay_ms.

Thanks for sharing this.


Kind regards
Uffe
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



--
Best Regards
Shawn Lin

--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux