From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: ISA DMA controller hangs
Date: Thu, 16 Jun 2005 17:06:22 +0100 [thread overview]
Message-ID: <20050616170622.A1712@flint.arm.linux.org.uk> (raw)
In-Reply-To: <42B1A08B.8080601@drzeus.cx>; from drzeus-list@drzeus.cx on Thu, Jun 16, 2005 at 05:53:47PM +0200
On Thu, Jun 16, 2005 at 05:53:47PM +0200, Pierre Ossman wrote:
> So how do we solve this problem? We should do a master clear and then
> enable channel 4 after a suspend. The question is where. I see three
> possible places:
>
> * In the suspend code in kernel/power.
> * In the driver actually handling the suspend (ACPI/APM/etc.).
> * Via the device layer by adding a device for the DMA controller.
>
> Which would be the preferred solution?
Shouldn't there be a system device for the DMA controller? I think
that should have appropriate hooks into the power management system
to do the necessary magic to restore whatever's needed - just like
we do for the PIC.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-06-16 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 13:38 ISA DMA controller hangs Pierre Ossman
2005-05-28 13:51 ` Alan Cox
2005-06-05 8:21 ` Pierre Ossman
2005-06-05 14:03 ` Pierre Ossman
2005-06-16 15:53 ` Pierre Ossman
2005-06-16 16:06 ` Russell King [this message]
2005-06-18 8:15 ` Pierre Ossman
2005-06-19 15:45 ` Russell King
2005-06-30 8:00 ` Pierre Ossman
2005-06-30 11:28 ` Alan Cox
2005-06-30 12:20 ` Pierre Ossman
2005-06-30 17:55 ` [PATCH 1/2] ISA DMA suspend for i386 Pierre Ossman
2005-06-30 17:58 ` [PATCH 2/2] ISA DMA suspend for x86_64 Pierre Ossman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050616170622.A1712@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.