From: "Thomas Maier" <balagi@justmail.de>
To: "Greg KH" <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, "petero2@telia.com" <petero2@telia.com>
Subject: Re: [PATCH] pktcdvd: added sysfs interface + bio write queue handling fix
Date: Sun, 10 Sep 2006 21:27:53 +0200 [thread overview]
Message-ID: <op.tfogcsaaiudtyh@master> (raw)
In-Reply-To: <20060909213054.GC19188@kroah.com>
Hello,
Am 09.09.2006, 23:30 Uhr, schrieb Greg KH <greg@kroah.com>:
> Use /sys/class/pktcdvd/ and use struct device instead of struct
> class_device, so I don't have to convert the code later :)
I moved the pktcdvd control files (device add/remove/map)
into /sys/class/pktcdvd/.
I only use "struct class", no need to use struct class_device,
since this /sys/class/pktcdvd represents not a real device.
The real devices are in /sys/block/pktcdvd[0-7] as created
by a "struct gendisk".
I have a little improvement request for the class code:
since the create_class() function has no attributes parameter,
i have to copy+paste the class_create() code into the module,
assign the class attribute array to the struct class and do a
class_register().
Would be nice if class_create() can be passed the class
attribute array...
The file layout is now as follows:
/sys/block/pktcdvd[0-7]/ # device dir created by gendisk
packet/ # pktcdvd subdir
<files> # pktcdvd per device files
mapped_to # symlink to mapped device in /sys/block
/sys/class/pktcdvd/ # class dir for control files
add # add new device mapping, creates new pktcdvd device
remove # ...
device_map
packet_buffers
/debugfs/pktcdvd[0-7]/ # per device debugfs dir entry
info # lot of human readable device infos, previous
# found in /proc/driver/pktcdvd[0-7]
Suggestions/Alteratives:
* should there be pktcdvd[0-7] subdirs in /sys/class/pktcdvd/ ?
With content stored in /sys/block/../packet/ ? Or a symlink to it?
* the files in /sys/class/pktcdvd can be moved to /sys/module/pktcdvd/ ?!
Seems that some modules have control files in their /sys/module directory.
-Thomas Maier
next prev parent reply other threads:[~2006-09-10 19:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 17:55 [PATCH] pktcdvd: added sysfs interface + bio write queue handling fix Thomas Maier
2006-09-08 18:53 ` Phillip Susi
2006-09-09 18:03 ` Thomas Maier
2006-09-08 21:00 ` Greg KH
2006-09-08 21:40 ` Phillip Susi
2006-09-08 22:01 ` Greg KH
2006-09-09 18:11 ` Thomas Maier
2006-09-09 21:30 ` Greg KH
2006-09-09 22:53 ` Kay Sievers
2006-09-10 19:33 ` Thomas Maier
2006-09-10 22:25 ` Kay Sievers
2006-09-10 19:27 ` Thomas Maier [this message]
2006-09-11 20:11 ` Thomas Maier
2006-09-11 20:07 ` [PATCH] class.c: added class_create_attrs() function Thomas Maier
-- strict thread matches above, loose matches on Subject: below --
2006-09-05 18:51 [PATCH] pktcdvd: added sysfs interface + bio write queue handling fix Thomas Maier
2006-09-03 18:20 Thomas Maier
2006-09-03 22:18 ` Randy.Dunlap
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=op.tfogcsaaiudtyh@master \
--to=balagi@justmail.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/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