mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Glow <sglow@embeddedintelligence.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to generate hotplug events in drivers?
Date: Fri, 13 Aug 2004 13:09:33 -0400	[thread overview]
Message-ID: <411CF5CD.9020207@embeddedintelligence.com> (raw)
In-Reply-To: <20040813070643.GA6785@kroah.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greg KH wrote:
| udev needs to see a file called "dev" in the proper structure show up in
| the sysfs tree in either /sys/class/* or /sys/block/*.  So, you need to
| either use the misc char device interface, the block interface, some
| other char interface that already has sysfs support, or add your own.
| If you need to add your own, I suggest looking into the class_simple
| interface, as that's a lot easier to work with to start out with.
|
| Hope this helps,
|
| greg k-h

Hi Greg;

Thanks for the response, things seem to be working now.

I'm still a little fuzzy about how all this works together, but the
picture is starting to become a bit clearer.  Here are the basic steps I
took in my PCI driver to get the device node to show up, please let me
know if anyone sees an error here:

In the init module function, I create a new class_simple pointer:

static struct class_simple *myclass;

int init_module( void )
{
~    ...
~    myclass = class_simple_create( THIS_MODULE, "myclassname" );
~    ...
}

This causes the new class directory to show up under /sys/class

In the PCI probe function I do the following:

probe(...)
{
~   ...

~   // Allocate a device numer
~   dev_t mydev;
~   alloc_chrdev_region( &mydev, 0, 1, "mydevicename" );

~   // Add this device number to my class.  Note I'm passing NULL for
~   // the device pointer.  I'm not exactly sure what this is for, but
~   // most devices in the kernel tree seem to pass NULL here.
~   class_simple_add_device( myclass, mydev, NULL, "mydevicename" );

~   // Finally, I init and add my cdev structure.
~   cdev_init( &mycdev, &myfops );
~   mycdev.owner = THIS_MODULE;
~   kobject_set_name( &mycdev.kobj, "mydevicename" );
~   cdev_add( &mycdev, mydev, 1 );

~   ...
}

Of course, my real code has error checking and does cleanup in the PCI
remove function and the module exit function.

Thanks again!

Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBHPXNDMBOo/wgA5QRAlAkAKCFrxmtrkEhVcCPQ8pBZzPQZccM5ACeJz/e
G/ulXO9/OdoScmgwSBJJ3xM=
=ylWm
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-08-13 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13  1:52 Stephen Glow
2004-08-13  7:06 ` Greg KH
2004-08-13 17:09   ` Stephen Glow [this message]
2004-08-13 17:23     ` Greg KH

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=411CF5CD.9020207@embeddedintelligence.com \
    --to=sglow@embeddedintelligence.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

all inboxes | Powered by JetHome®