public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: class_device_create() and class_interfaces ?
Date: Tue, 18 Apr 2006 17:29:39 -0700	[thread overview]
Message-ID: <adabquycsr0.fsf@cisco.com> (raw)
In-Reply-To: <20060419000438.GA6522@kroah.com> (Greg KH's message of "Tue, 18 Apr 2006 17:04:38 -0700")

    Greg> I'm working toward getting rid of class_devices entirely.
    Greg> What you can do is use a struct device heirachy, right?  If
    Greg> so, take a look at this patch:
    Greg> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/device-class.patch
    Greg> which implements the start of this changeover.  So, if you
    Greg> were to do this, you can just create a separate "bus" and
    Greg> drivers for these different devices, and everything should
    Greg> bind just fine.

Hmm, that seems a lot more complicated that what I need.  And it seems
I end up needing to handle some sort of registration myself anyway,
because someone has to create the virtual devices when a real device
shows up (since multiple drivers can't bind to the same device).

I think I'll just code my own simple registration for sub-drivers of
the combo device -- it will just take a list_head, a mutex and a few
of lines of code.  That seems simpler to me than creating a fake bus
and fake devices for each combo device.

Thanks,
  Roland

      reply	other threads:[~2006-04-19  0:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 23:46 class_device_create() and class_interfaces ? Roland Dreier
2006-04-19  0:04 ` Greg KH
2006-04-19  0:29   ` Roland Dreier [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=adabquycsr0.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=greg@kroah.com \
    --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