From: Pierre Ossman <drzeus-list@drzeus.cx>
To: LKML <linux-kernel@vger.kernel.org>
Subject: PNP and bus association
Date: Thu, 27 Jan 2005 22:16:50 +0100 [thread overview]
Message-ID: <41F95A42.40001@drzeus.cx> (raw)
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.
Rgds
Pierre
next reply other threads:[~2005-01-27 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 21:16 Pierre Ossman [this message]
2005-01-27 22:56 ` PNP and bus association Randy.Dunlap
2005-01-28 15:49 ` Pierre Ossman
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=41F95A42.40001@drzeus.cx \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).