public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>,
	Andrew Morton <akpm@zip.com.au>
Subject: Re: Power management of old ISA devices (Re: mark older power managment as deprecated)
Date: Wed, 05 Jan 2005 17:26:04 +0100	[thread overview]
Message-ID: <s5his6byh9f.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050104202245.GB7924@elf.ucw.cz>

At Tue, 4 Jan 2005 21:22:45 +0100,
Pavel Machek wrote:
> 
> Hi!
> 
> > > What about this patch? It marks old power managemnt as obsolete (and
> > > also adds some sparse-style type checking; typedefs were already there
> > > so why not use them?). I think it should go in, so that we can get a
> > > rid of old power managment infrastructure post-2.6.11.
> > 
> > ALSA core part still includes pm_register/unregister() for old
> > (non-PnP) ISA devices.
> > 
> > What is the proper way to register/unregister PM hooks for such
> > devices?
> 
> How are PnP ISA devices handled?

Sorry, correction: pm_register() is used for both ISA PnP and non-PnP
devices.

> Right solution for ISA devices is probably to create an ISA bus in
> driver model, and hook such devices there....

Yep.

> Alternatively, you might just hang them onto platform bus, in similar
> way i8042 uses...

This looks easier to implement as a temporary solution until ISA bus
is implemented.  We know how many instances are to be initiailized in
advance, so each driver object can have a unique name.

> Imagine this configuration:
> 
> cpu -- PCI #1 -- PCI to PCI bridge -- PCI #2 -- PCI to ISA bridge -- sound card #1 on 0x100
>               \- PCI to PCI bridge -- PCI #3 -- PCI to ISA bridge -- sound card #2 on 0x100
> 
> ...would you say that's supported? If yes you'd need to create ISA
> buses and do it properly, otherwise hooking to platform bus is
> probably acceptable.

Well, I don't think this can be problematic on ISA soundcards with
platform_device.  Anyway, I'll try to implement platform_device at
first as a test...


Thanks!

Takashi

      reply	other threads:[~2005-01-05 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-04 12:46 mark older power managment as deprecated Pavel Machek
2005-01-04 13:04 ` Russell King
2005-01-04 13:08   ` Pavel Machek
2005-01-04 16:39 ` Power management of old ISA devices (Re: mark older power managment as deprecated) Takashi Iwai
2005-01-04 20:22   ` Pavel Machek
2005-01-05 16:26     ` Takashi Iwai [this message]

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=s5his6byh9f.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox