From: Jon Smirl <jonsmirl@gmail.com>
To: perex@suse.cz
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, "Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: Intel ICH - sound/pci/intel8x0.c
Date: Mon, 6 Sep 2004 00:07:21 -0400 [thread overview]
Message-ID: <9e473391040905210762427f42@mail.gmail.com> (raw)
In-Reply-To: <20040905190937.36e72b49.rddunlap@osdl.org>
> On Sun, 05 Sep 2004 21:49:50 +0100 Alan Cox wrote:
> | On Sul, 2004-09-05 at 22:24, Jon Smirl wrote:
> | > I'd don't know enough about the LPC bridge chip to know what the
> | > correct answer is for this. Right now I tend to think that the PCI
> | > driver should own the bridge chip. If not the PCI driver then there
> | > should be an explicit bridge driver. I don' think it is correct that a
> | > joystick driver is attaching to a bridge chip given the simple fact
> |
> | Nobody else currently needs to attach to it so why make life needlessly
> | complicated.
I just spent a while looking at the code. The joystick driver doesn't
need to exist. Instead the snd_intel8x0_probe() routine could have a
loop that does pci_get_subsys() over the ID's in
snd_intel8x0_joystick_ids[]. When it finds one, use the config space
to enable the joystick/midiports. You can locate the ports since
pci_get_subsys() returns the pci_dev* for the bridge device. Save the
pci_dev* and set the ports back in snd_intel8x0_remove(). Don't forget
to pci_put() the bridge device.
This isn't a device driver for the bridge, we just want to locate it
and flip some bits. Later on if a driver for the bridge get written it
should support an API for setting these bits and the search loop can
be removed.
All of these devices are listed as Intel LPC bridges:
2410, 2420, 2440, 244c, 2450, 2480, 2484, 24c0, 24cc, 24d0, 24dc,
25a1, 2640, 2641, 2642
I have a 24D0 which isn't in the driver list, this is probably why
MIDI doesn't work on my system.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-06 4:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 18:48 Intel ICH - sound/pci/intel8x0.c Matthieu Castet
2004-09-05 21:24 ` Jon Smirl
2004-09-05 20:49 ` Alan Cox
2004-09-06 2:09 ` Randy.Dunlap
2004-09-06 4:07 ` Jon Smirl [this message]
2004-09-06 2:13 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2004-09-06 15:48 Matthieu Castet
2004-09-06 8:40 Matthieu Castet
2004-09-06 8:31 Matthieu Castet
2004-09-06 11:27 ` Alan Cox
2004-09-06 14:11 ` Jon Smirl
2004-09-05 2:43 Jon Smirl
2004-09-05 11:55 ` Alan Cox
2004-09-05 15:26 ` Jon Smirl
2004-09-06 10:57 ` Takashi Iwai
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=9e473391040905210762427f42@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox