All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: How can I specify a specific 'sub-device' of a device for udev
Date: Mon, 01 Mar 2004 12:36:10 +0000	[thread overview]
Message-ID: <1078144569.1312.41.camel@pim> (raw)
In-Reply-To: <4042D36F.9020909@kuiki.net>

On Mon, 2004-03-01 at 07:08, Jonathan Steinert wrote:
> Morning everybody,
> 
> I'm trying to find how I can write a rule which allows me to say "The 
> usb-serial bus interface inside the usb device with a sysfs serial of 
> "304087" should be named "foo"
> 
> I'll paste my udevinfo output for the device in question (A Belkin USB 
> to serial dongle) at the bottom, but I am running into a similar issue 
> with my Griffin Powermate.
> 
> The rule I came up with, which does not work nor seem correct in the 
> first place is:
> 
> BUS="usb-serial", SYSFS{serial}="304087", NAME="foo"

Yes, the rule is incorrect. It's not on the same device.

> Since this does not work, I am asuming that the sysfs attributes to not 
> trickle down a driver chain for matching in more specific devices.

It walks down, just like udevinfo does. But you can only match
attributes of _one_ device not combine attributes from different devices
on the chain.

> This does leave me puzzled about two things:
> 
> 1) Why does udev have a flag to crawl up the sysfs tree (Asuming my 
> observations of udev are correct) but no flag to show the attributes of 
> only the device I specify? or only 'n' layers down for that matter?

Do you really need this? Why?

> 2) How can I write a rule to match the usb-serial interface of a usb 
> device with a particular serial number?

>   looking at the device chain at 
> '/sys/devices/pci0000:00/0000:00:1d.2/usb2/2-1':
>     BUS="usb"
...
>     SYSFS{serial}="304087"

Your serial number belongs the "usb"-device and not the virtual
"usb-serial"-device. A match for the "hardware" behind your serial
device should work fine:

  BUS="usb", SYSFS{serial}="304087", NAME="foo"

If you really need to match this particular device interface, you may
use its bus-id:

  BUS="usb", ID="2-1:1.0", NAME="foo"


hope that helps,
Kay



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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:[~2004-03-01 12:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01  6:08 How can I specify a specific 'sub-device' of a device for udev naming? Jonathan Steinert
2004-03-01 12:36 ` Kay Sievers [this message]
2004-03-01 16:23 ` How can I specify a specific 'sub-device' of a device for udev Jonathan Steinert
2004-03-01 17:00 ` Kay Sievers
2004-03-01 23:56 ` Jonathan Steinert
2004-03-02  0:37 ` How can I specify a specific 'sub-device' of a device for udev naming? Kay Sievers
2004-03-04  7:19 ` How can I specify a specific 'sub-device' of a device for udev Jonathan Steinert
2004-03-04 19:53 ` How can I specify a specific 'sub-device' of a device for udev naming? 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=1078144569.1312.41.camel@pim \
    --to=kay.sievers@vrfy.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.