On 10 March 2016 at 11:30, Ludovic Desroches
wrote:
> It was impossible to wake-up on card detect event because when sdhci
> controller is runtime suspend, it is assumed that all the clocks are
> disabled so we can't get irqs.
> If the device is removable and there is
On 10 March 2016 at 11:30, Ludovic Desroches
wrote:
> It was impossible to wake-up on card detect event because when sdhci
> controller is runtime suspend, it is assumed that all the clocks are
> disabled so we can't get irqs.
> If the device is removable and there is no gpio to manage the card
>
On Thu, Mar 10, 2016 at 11:30:58AM +0100, Ludovic Desroches wrote:
> It was impossible to wake-up on card detect event because when sdhci
> controller is runtime suspend, it is assumed that all the clocks are
> disabled so we can't get irqs.
> If the device is removable and there is no gpio to
On Thu, Mar 10, 2016 at 11:30:58AM +0100, Ludovic Desroches wrote:
> It was impossible to wake-up on card detect event because when sdhci
> controller is runtime suspend, it is assumed that all the clocks are
> disabled so we can't get irqs.
> If the device is removable and there is no gpio to
It was impossible to wake-up on card detect event because when sdhci
controller is runtime suspend, it is assumed that all the clocks are
disabled so we can't get irqs.
If the device is removable and there is no gpio to manage the card
detection then card detection polling is used.
Signed-off-by:
It was impossible to wake-up on card detect event because when sdhci
controller is runtime suspend, it is assumed that all the clocks are
disabled so we can't get irqs.
If the device is removable and there is no gpio to manage the card
detection then card detection polling is used.
Signed-off-by:
+ PM mailing list since the discussion is mixing PM and sdhci
On Tue, Mar 08, 2016 at 10:56:31PM +0100, Ulf Hansson wrote:
> +Ludovic
>
> On 8 March 2016 at 22:54, Ulf Hansson wrote:
> > On 4 March 2016 at 14:48, Ludovic Desroches
> >
+ PM mailing list since the discussion is mixing PM and sdhci
On Tue, Mar 08, 2016 at 10:56:31PM +0100, Ulf Hansson wrote:
> +Ludovic
>
> On 8 March 2016 at 22:54, Ulf Hansson wrote:
> > On 4 March 2016 at 14:48, Ludovic Desroches
> > wrote:
[snip]
> >>
> >> Coming back to the initial
+Ludovic
On 8 March 2016 at 22:54, Ulf Hansson wrote:
> On 4 March 2016 at 14:48, Ludovic Desroches
> wrote:
>> Hi Ulf,
>>
>> On Fri, Mar 04, 2016 at 10:09:37AM +0100, Ulf Hansson wrote:
>>> On 17 February 2016 at 11:35, Ludovic Desroches
>>
+Ludovic
On 8 March 2016 at 22:54, Ulf Hansson wrote:
> On 4 March 2016 at 14:48, Ludovic Desroches
> wrote:
>> Hi Ulf,
>>
>> On Fri, Mar 04, 2016 at 10:09:37AM +0100, Ulf Hansson wrote:
>>> On 17 February 2016 at 11:35, Ludovic Desroches
>>
>> [snip]
>>
>>> > I am wondering if I should take
On 4 March 2016 at 14:48, Ludovic Desroches wrote:
> Hi Ulf,
>
> On Fri, Mar 04, 2016 at 10:09:37AM +0100, Ulf Hansson wrote:
>> On 17 February 2016 at 11:35, Ludovic Desroches
>
> [snip]
>
>> > I am wondering if I should take account of sdio irq enabled or not here.
On 4 March 2016 at 14:48, Ludovic Desroches wrote:
> Hi Ulf,
>
> On Fri, Mar 04, 2016 at 10:09:37AM +0100, Ulf Hansson wrote:
>> On 17 February 2016 at 11:35, Ludovic Desroches
>
> [snip]
>
>> > I am wondering if I should take account of sdio irq enabled or not here.
>> >
>> > I have a sdio
Hi Ulf,
On Fri, Mar 04, 2016 at 10:09:37AM +0100, Ulf Hansson wrote:
> On 17 February 2016 at 11:35, Ludovic Desroches
[snip]
> > I am wondering if I should take account of sdio irq enabled or not here.
> >
> > I have a sdio device which drives me crazy because of power management.
> > The
Hi Ulf,
On Fri, Mar 04, 2016 at 10:09:37AM +0100, Ulf Hansson wrote:
> On 17 February 2016 at 11:35, Ludovic Desroches
[snip]
> > I am wondering if I should take account of sdio irq enabled or not here.
> >
> > I have a sdio device which drives me crazy because of power management.
> > The
+ Ludovic
On 4 March 2016 at 10:09, Ulf Hansson wrote:
> On 17 February 2016 at 11:35, Ludovic Desroches
> wrote:
>> On Tue, Feb 16, 2016 at 04:22:04PM +0100, Ludovic Desroches wrote:
>>> On Tue, Feb 16, 2016 at 03:38:29PM +0100, Ulf Hansson
+ Ludovic
On 4 March 2016 at 10:09, Ulf Hansson wrote:
> On 17 February 2016 at 11:35, Ludovic Desroches
> wrote:
>> On Tue, Feb 16, 2016 at 04:22:04PM +0100, Ludovic Desroches wrote:
>>> On Tue, Feb 16, 2016 at 03:38:29PM +0100, Ulf Hansson wrote:
>>> > On 13 February 2016 at 10:56, Ludovic
On 17 February 2016 at 11:35, Ludovic Desroches
wrote:
> On Tue, Feb 16, 2016 at 04:22:04PM +0100, Ludovic Desroches wrote:
>> On Tue, Feb 16, 2016 at 03:38:29PM +0100, Ulf Hansson wrote:
>> > On 13 February 2016 at 10:56, Ludovic Desroches
>> >
On 17 February 2016 at 11:35, Ludovic Desroches
wrote:
> On Tue, Feb 16, 2016 at 04:22:04PM +0100, Ludovic Desroches wrote:
>> On Tue, Feb 16, 2016 at 03:38:29PM +0100, Ulf Hansson wrote:
>> > On 13 February 2016 at 10:56, Ludovic Desroches
>> > wrote:
>> > > When suspending the sdhci host, the
On Sat, Feb 13, 2016 at 10:56:40AM +0100, Ludovic Desroches wrote:
> When suspending the sdhci host, the only hardware event that could wake
> up the host is a sdio irq if they are enabled. If we want to wakeup on
> card detect events, a gpio as to be used.
> If we don't want to use a gpio but the
On Sat, Feb 13, 2016 at 10:56:40AM +0100, Ludovic Desroches wrote:
> When suspending the sdhci host, the only hardware event that could wake
> up the host is a sdio irq if they are enabled. If we want to wakeup on
> card detect events, a gpio as to be used.
> If we don't want to use a gpio but the
On Tue, Feb 16, 2016 at 04:22:04PM +0100, Ludovic Desroches wrote:
> On Tue, Feb 16, 2016 at 03:38:29PM +0100, Ulf Hansson wrote:
> > On 13 February 2016 at 10:56, Ludovic Desroches
> > wrote:
> > > When suspending the sdhci host, the only hardware event that could
On Tue, Feb 16, 2016 at 04:22:04PM +0100, Ludovic Desroches wrote:
> On Tue, Feb 16, 2016 at 03:38:29PM +0100, Ulf Hansson wrote:
> > On 13 February 2016 at 10:56, Ludovic Desroches
> > wrote:
> > > When suspending the sdhci host, the only hardware event that could wake
> > > up the host is a
On Tue, Feb 16, 2016 at 03:38:29PM +0100, Ulf Hansson wrote:
> On 13 February 2016 at 10:56, Ludovic Desroches
> wrote:
> > When suspending the sdhci host, the only hardware event that could wake
> > up the host is a sdio irq if they are enabled. If we want to wakeup
On Tue, Feb 16, 2016 at 03:38:29PM +0100, Ulf Hansson wrote:
> On 13 February 2016 at 10:56, Ludovic Desroches
> wrote:
> > When suspending the sdhci host, the only hardware event that could wake
> > up the host is a sdio irq if they are enabled. If we want to wakeup on
> > card detect events, a
On 13 February 2016 at 10:56, Ludovic Desroches
wrote:
> When suspending the sdhci host, the only hardware event that could wake
> up the host is a sdio irq if they are enabled. If we want to wakeup on
> card detect events, a gpio as to be used.
> If we don't want to
On 13 February 2016 at 10:56, Ludovic Desroches
wrote:
> When suspending the sdhci host, the only hardware event that could wake
> up the host is a sdio irq if they are enabled. If we want to wakeup on
> card detect events, a gpio as to be used.
> If we don't want to use a gpio but the card
When suspending the sdhci host, the only hardware event that could wake
up the host is a sdio irq if they are enabled. If we want to wakeup on
card detect events, a gpio as to be used.
If we don't want to use a gpio but the card detect pio of the controller
then we need to keep enabled the clock
When suspending the sdhci host, the only hardware event that could wake
up the host is a sdio irq if they are enabled. If we want to wakeup on
card detect events, a gpio as to be used.
If we don't want to use a gpio but the card detect pio of the controller
then we need to keep enabled the clock
28 matches
Mail list logo