From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz, vojtech@ucw.cz
Subject: Re: [PATCH 8/11] serio sysfs integration
Date: Fri, 18 Jun 2004 07:50:26 -0500 [thread overview]
Message-ID: <200406180750.26570.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040618023853.5d4ee96a.akpm@osdl.org>
On Friday 18 June 2004 04:38 am, Andrew Morton wrote:
> Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> >
> > Input: serio sysfs integration
>
> What is the sysfs directory layout, and what do the chosen nodes do?
>
> What design decisions were made when choosing that layout?
>
> Is it so trivial that users don't need any documentation?
>
I do consider it trivial for now as the only thing that user can do is
"echo" desired driver into serioX/driver to rebind it. The typical node
looks like this:
[dtor@core dtor]$ ls -la /sys/bus/serio/devices/serio0/
total 0
-r--r--r-- 1 root root 4096 Jun 17 21:49 description
-rw-r--r-- 1 root root 4096 Jun 17 21:49 detach_state
-rw-r--r-- 1 root root 0 Jun 18 02:52 driver
-r--r--r-- 1 root root 4096 Jun 17 21:49 legacy_position
drwxr-xr-x 2 root root 0 Jun 17 21:49 power
drwxr-xr-x 3 root root 0 Jun 18 02:52 serio3
description - i8042 Aux Port
driver - psmouse
legacy_position - isa0060/serio1 (take from serio's phys, can be used
to match with /proc/bus/input/devices).
Every driver will have a set of custom attributes that will be documented
on one by one basis. Btw, where would you document it? Documentation
directory entry? Something else?
--
Dmitry
[dtor@core dtor]$ ls -laR /sys/bus/serio/
/sys/bus/serio/:
total 0
drwxr-xr-x 2 root root 0 Jun 18 02:52 devices
drwxr-xr-x 5 root root 0 Jun 18 02:52 drivers
/sys/bus/serio/devices:
total 0
lrwxrwxrwx 1 root root 0 Jun 17 21:49 serio0 -> ../../../devices/serio0
lrwxrwxrwx 1 root root 0 Jun 17 21:49 serio1 -> ../../../devices/serio1
lrwxrwxrwx 1 root root 0 Jun 18 02:52 serio3 -> ../../../devices/serio0/serio3
/sys/bus/serio/drivers:
total 0
drwxr-xr-x 2 root root 0 Jun 17 21:49 atkbd
drwxr-xr-x 2 root root 0 Jun 18 02:52 psmouse
drwxr-xr-x 2 root root 0 Jun 18 02:52 serio_raw
/sys/bus/serio/drivers/atkbd:
total 0
-r--r--r-- 1 root root 4096 Jun 17 21:49 description
lrwxrwxrwx 1 root root 0 Jun 17 21:49 serio1 -> ../../../../devices/serio1
/sys/bus/serio/drivers/psmouse:
total 0
-r--r--r-- 1 root root 4096 Jun 18 02:52 description
lrwxrwxrwx 1 root root 0 Jun 18 02:52 serio0 -> ../../../../devices/serio0
lrwxrwxrwx 1 root root 0 Jun 18 02:52 serio3 -> ../../../../devices/serio0/serio3
/sys/bus/serio/drivers/serio_raw:
total 0
-r--r--r-- 1 root root 4096 Jun 18 02:50 description
next prev parent reply other threads:[~2004-06-18 12:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200406180335.52843.dtor_core@ameritech.net>
2004-06-18 8:37 ` [PATCH 1/11] psmouse resync for KVM users Dmitry Torokhov
2004-06-18 8:37 ` [PATCH 2/11] psmouse state locking Dmitry Torokhov
2004-06-18 8:38 ` [PATCH 3/11] serio connect/disconnect mandatory Dmitry Torokhov
2004-06-18 8:39 ` [PATCH 4/11] serio renames 1 Dmitry Torokhov
2004-06-18 8:39 ` [PATCH 5/11] serio renames 2 Dmitry Torokhov
2004-06-18 8:40 ` [PATCH 6/11] serio dynamic allocation Dmitry Torokhov
2004-06-18 8:41 ` [PATCH 7/11] serio no recursion Dmitry Torokhov
2004-06-18 8:42 ` [PATCH 8/11] serio sysfs integration Dmitry Torokhov
2004-06-18 8:42 ` [PATCH 9/11] serio allow rebinding Dmitry Torokhov
2004-06-18 8:43 ` [PATCH 10/11] serio manual bind Dmitry Torokhov
2004-06-18 8:43 ` [PATCH 11/11] serio_raw driver Dmitry Torokhov
2004-06-18 9:19 ` [PATCH 9/11] serio allow rebinding Jan-Benedict Glaw
2004-06-18 9:38 ` [PATCH 8/11] serio sysfs integration Andrew Morton
2004-06-18 12:50 ` Dmitry Torokhov [this message]
2004-06-18 19:43 ` Andrew Morton
2004-06-20 5:07 ` [PATCH 6/11] serio dynamic allocation Andrew Morton
2004-06-20 5:30 ` Dmitry Torokhov
2004-06-20 6:27 ` Andrew Morton
2004-06-20 6:28 ` Andrew Morton
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=200406180750.26570.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
--cc=vojtech@ucw.cz \
/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.