From: Jiri Slaby <jirislaby@gmail.com>
To: Adam Nielsen <a.nielsen@shikadi.net>
Cc: LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: hid class and sysfs/hwmon
Date: Sat, 08 Nov 2008 22:51:06 +0100 [thread overview]
Message-ID: <491609CA.30303@gmail.com> (raw)
In-Reply-To: <4916087F.30100@shikadi.net>
Adam Nielsen napsal(a):
>>> If anyone can see why this might result in no sysfs files, please let me
>>> know! I previously had most of this code working with a platform_device
>>> instead of the hid_device, which is what makes me wonder about
>>> hdev->dev.kobj. (Not sure how to test if that variable is accurate,
>>> either.) Or perhaps it has already been used elsewhere and it can only
>>> be used once?
>>
>> I suppose it's under /sys/bus/hid/devices/.../, isn't it?
>
> Aha, yes! I didn't even think of checking there. I suppose this means
> I have to create another device (like a platform_device) in order to
> have the sysfs files appear in the correct place?
>
> Is a platform_device the correct type to create, or is there another way?
I don't know much about hwmon, but I would guess you should use hwmon_dev
for registering the attributes if you want it under /sys/class/hwmon/...
Such as:
sysfs_create_group(&odin_psu->hwmon_dev->kobj, &odin_attr_group);
No?
next prev parent reply other threads:[~2008-11-08 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 7:51 led and hid class - hid_device vs led_classdev Adam Nielsen
2008-11-04 21:48 ` Jiri Slaby
2008-11-08 6:18 ` hid class and sysfs/hwmon (was: led and hid class - hid_device vs led_classdev) Adam Nielsen
2008-11-08 14:16 ` hid class and sysfs/hwmon Jiri Slaby
2008-11-08 21:45 ` Adam Nielsen
2008-11-08 21:51 ` Jiri Slaby [this message]
2008-11-08 22:02 ` Adam Nielsen
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=491609CA.30303@gmail.com \
--to=jirislaby@gmail.com \
--cc=a.nielsen@shikadi.net \
--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