> I don't see that - as I say above, the correct sequence is:
>
> - host device resume
> - calls mmc_resume_host()
> - child's device resume (mmc_blk_resume)
> - mmc_queue_resume()
>
Of course, I understand that this is a correct sequence. It simply was not
obvious to me that host
I don't see that - as I say above, the correct sequence is:
- host device resume
- calls mmc_resume_host()
- child's device resume (mmc_blk_resume)
- mmc_queue_resume()
Of course, I understand that this is a correct sequence. It simply was not
obvious to me that host
will
On Sat, Feb 17, 2007 at 05:46:35PM -0800, Alex Dubov wrote:
> The problem here is that mmc_block's device is a child of real device
> (tifm_dev here), so it gets resumed right after it.
The host driver is supposed to call mmc_resume_host from it's resume
callback. This should be called before
--- Pavel Machek <[EMAIL PROTECTED]> wrote:
> On Sun 2007-02-18 00:35:33, Pierre Ossman wrote:
> > Alex Dubov wrote:
> > > And today: yet another problem with mmc.
> > > It so happens that after resume mmc layer issues requests to the device
> > > before
> mmc_resume_host is
> > > called at
On Sun 2007-02-18 00:35:33, Pierre Ossman wrote:
> Alex Dubov wrote:
> > And today: yet another problem with mmc.
> > It so happens that after resume mmc layer issues requests to the device
> > before mmc_resume_host is
> > called at all. Moreover, this prevents the machine from resuming, unless
Alex Dubov wrote:
> And today: yet another problem with mmc.
> It so happens that after resume mmc layer issues requests to the device
> before mmc_resume_host is
> called at all. Moreover, this prevents the machine from resuming, unless
> worked around, because
> software timer does not work at
And today: yet another problem with mmc.
It so happens that after resume mmc layer issues requests to the device before
mmc_resume_host is
called at all. Moreover, this prevents the machine from resuming, unless worked
around, because
software timer does not work at this stage of the resume and
And today: yet another problem with mmc.
It so happens that after resume mmc layer issues requests to the device before
mmc_resume_host is
called at all. Moreover, this prevents the machine from resuming, unless worked
around, because
software timer does not work at this stage of the resume and
Alex Dubov wrote:
And today: yet another problem with mmc.
It so happens that after resume mmc layer issues requests to the device
before mmc_resume_host is
called at all. Moreover, this prevents the machine from resuming, unless
worked around, because
software timer does not work at this
On Sun 2007-02-18 00:35:33, Pierre Ossman wrote:
Alex Dubov wrote:
And today: yet another problem with mmc.
It so happens that after resume mmc layer issues requests to the device
before mmc_resume_host is
called at all. Moreover, this prevents the machine from resuming, unless
worked
--- Pavel Machek [EMAIL PROTECTED] wrote:
On Sun 2007-02-18 00:35:33, Pierre Ossman wrote:
Alex Dubov wrote:
And today: yet another problem with mmc.
It so happens that after resume mmc layer issues requests to the device
before
mmc_resume_host is
called at all. Moreover, this
On Sat, Feb 17, 2007 at 05:46:35PM -0800, Alex Dubov wrote:
The problem here is that mmc_block's device is a child of real device
(tifm_dev here), so it gets resumed right after it.
The host driver is supposed to call mmc_resume_host from it's resume
callback. This should be called before the
12 matches
Mail list logo
