linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Clacherty <justin@redfish-group.com>
To: linux-hotplug@vger.kernel.org
Subject: udev rule for custom driver
Date: Tue, 19 Dec 2006 00:41:09 +0000	[thread overview]
Message-ID: <45873525.8050007@redfish-group.com> (raw)

Hi,

I've been trying to get a udev rule to automatically create the /dev 
entries for the custom spi driver I've written for my board but am 
having no luck.  I've created the file /etc/udev/rules.d/10-spi.rules 
which contains the following line:

SUBSYSTEM="spi", SYSFS{modalias}="nexus_spi", NAME="nspi%n"

If I run udevmonitor and do a udev trigger I see the following line in 
the output:

UEVENT[1166449657.257561] add@/devices/platform/pxa2xx-spi.1/spi1.0

Running udevinfo on /devices/platform/pxa2xx-spi.1/spi1.0 gives:

  looking at device '/devices/platform/pxa2xx-spi.1/spi1.0':
    KERNEL="spi1.0"
    SUBSYSTEM="spi"
    SYSFS{modalias}="nexus_spi"

  looking at parent device '/devices/platform/pxa2xx-spi.1':
    ID="pxa2xx-spi.1"
    BUS="platform"
    DRIVER="pxa2xx-spi"
    SYSFS{modalias}="pxa2xx-spi"

  looking at parent device '/devices/platform':
    ID="platform"
    BUS=""
    DRIVER=""

Running udevtest on the sysfs tree gives the following output:

main: looking at device '/devices/platform/pxa2xx-spi.1/spi1.0' from 
subsystem 'spi'
main: run: 'socket:/org/kernel/udev/monitor'

Obviously I've missed something here, can anyone point to the problem?  
Do I need to add something to my driver for this to work or is my udev 
setup at fault?

Regards,
Justin.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2006-12-19  0:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19  0:41 Justin Clacherty [this message]
2006-12-19  0:53 ` udev rule for custom driver Alex Merry
2006-12-19  1:19 ` Justin Clacherty
2006-12-19  3:33 ` Justin Clacherty
2006-12-19  7:31 ` Kay Sievers

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=45873525.8050007@redfish-group.com \
    --to=justin@redfish-group.com \
    --cc=linux-hotplug@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).