From: Thomas Renninger <trenn@suse.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: ALSA devel <alsa-devel@alsa-project.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"yakui.zhao" <yakui.zhao@intel.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
akpm <akpm@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [alsa-devel] [PATCH 2/3] PNP cleanups - Unify the pnp macros to access resources in the pnp resource table
Date: Tue, 27 Nov 2007 17:34:51 +0100 [thread overview]
Message-ID: <1196181292.23251.53.camel@queen.suse.de> (raw)
In-Reply-To: <s5hejejj559.wl%tiwai@suse.de>
On Wed, 2007-11-21 at 10:53 +0100, Takashi Iwai wrote:
> At Tue, 20 Nov 2007 15:31:26 +0100,
> Rene Herman wrote:
> >
> > On 20-11-07 15:19, Thomas Renninger wrote:
> >
> > > At the end is some example code how things could get even more cleaned
> > > up. It shows how I think pnp layer and one example driver would get
> > > adjusted. There are not that much drivers making use of
> > > pnp_resource_change...
> >
> > The ALSA ISA-PnP drivers do in what I personally consider a bad layering
> > violation. Brought up not doing that a while ago on alsa-devel, but no
> > discussion ensued. If the PnP maintainer(s) agree with me though, I'd be
> > more than happy to rip all of that out of ALSA.
Rene: Could you do that, pls.
>
> I'm fine with removal of that stuff now. It was implemented in that
> way because there was no proper way to re-assign ISA PnP resources on
> 2.4 kernel time. On 2.6, it makes no longer any sense (except for
> compatibility, but this is almost no problem for PnP boards).
I wasted some time on thinking about how this pnp_resource_change and
pnp_manual_config_dev could get workarounded..., but it's impossible
without changing the (more a workaround than an) interface.
If you worked on this already, would you mind ripping these out?
If I understand Takashi correctly, the driver code using
pnp_resource_change and pnp_manual_config_dev can simply be removed and
devices could get resources assigned via sysfs "set" interface.
Thanks,
Thomas
next prev parent reply other threads:[~2007-11-27 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 9:51 [PATCH 2/3] PNP cleanups - Unify the pnp macros to access resources in the pnp resource table Thomas Renninger
2007-11-20 10:17 ` Rene Herman
2007-11-20 12:31 ` Alan Cox
2007-11-20 14:19 ` Thomas Renninger
2007-11-20 14:31 ` Rene Herman
2007-11-20 16:48 ` Thomas Renninger
2007-11-21 9:53 ` [alsa-devel] " Takashi Iwai
2007-11-27 16:34 ` Thomas Renninger [this message]
2007-11-27 16:52 ` Rene Herman
2007-11-20 15:14 ` Alan Cox
2007-11-20 18:59 ` Andi Kleen
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=1196181292.23251.53.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=shaohua.li@intel.com \
--cc=tiwai@suse.de \
--cc=yakui.zhao@intel.com \
/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