From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: PNP and bus association
Date: Fri, 28 Jan 2005 16:49:54 +0100 [thread overview]
Message-ID: <41FA5F22.5020008@drzeus.cx> (raw)
In-Reply-To: <41F97185.6030905@osdl.org>
Randy.Dunlap wrote:
> Pierre Ossman wrote:
>
>> I recently tried out adding PNP support to my driver to remove the
>> hassle of finding the correct parameters for it. This, however,
>> causes it to show up under the pnp bus, where as it previously was
>> located under the platform bus.
>>
>> Is the idea that PNP devices should only reside on the PNP bus or is
>> there some magic available to get the device to appear on several
>> buses? It's a bit of a hassle to search in two different places in
>> sysfs depending on if PNP is used or not.
>>
>> Also, the PNP bus doesn't really say that much about where the device
>> is physically connected. The other bus types usually give a hint
>> about this.
>
>
> Not to take away from your question, but:
> Is there "the PNP bus"? I've seen an ISA bus that (sort of)
> supports PNP, PCI PNP, NuBus PNP, USB PNP, IEEE 1394 PNP, etc.
>
It's not a physical bus but it is a bus as far as the kernel is
concerned. And that's really my problem. I want it to support PNP, but
also to associate with the physical bus it's connected to.
Rgds
Pierre
PS. Your outgoing mail server gives the wrong HELO
next prev parent reply other threads:[~2005-01-28 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 21:16 PNP and bus association Pierre Ossman
2005-01-27 22:56 ` Randy.Dunlap
2005-01-28 15:49 ` Pierre Ossman [this message]
2005-01-28 22:47 ` Adam Belay
2005-01-29 0:43 ` 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=41FA5F22.5020008@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--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