[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1103011525040.2034-100000@iolanthe.rowland.org>
Date: Tue, 1 Mar 2011 15:27:54 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Pierre Tardy <tardyp@...il.com>
cc: linux-kernel@...r.kernel.org,
<linux-pm@...ts.linux-foundation.org>, <linux-mmc@...r.kernel.org>
Subject: Re: [linux-pm] [RFC, PATCHv3 3/3] mmc: sdhci: handle wake-up from
runtime_pm
On Tue, 1 Mar 2011, Pierre Tardy wrote:
> >> + if (pm_runtime_suspended()) {
> >> + host->waking_up = 1;
> >> + /* Note that we disable temporarly the interrupt until we do the
> >> + * resume. If we don't then we'll get constantly interrupted
> >> + * until we actually resume.
> >> + *
> >> + * as the irq is shared, this might not be very friendly to our
> >> + * irq sharers but the pm_runtime workqueue should really be
> >> + * called soon.
> >
> > Instead of disabling the IRQ, would it be possible to tell the device
> > to stop generating an interrupt request?
>
> Well, the device is power gated, so any access to it will cause a bus
> timeout (depending of the platform)
But could you gate the power back on and then turn off the interrupt
request?
It seems like a foolish design to have an interrupt request that can't
be turned off by an interrupt handler.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists