From: Marcel Holtmann <marcel@holtmann.org>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: Mario Limonciello <mario_limonciello@dell.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
cezary.jackiewicz@gmail.com
Subject: Re: [PATCH 3/3] Drop platform sysfs support
Date: Tue, 18 Aug 2009 14:45:34 -0700 [thread overview]
Message-ID: <1250631934.5150.3.camel@localhost.localdomain> (raw)
In-Reply-To: <9b2b86520908180623i4e7ce5cv9a4cd6b1704a0e5f@mail.gmail.com>
Hi Alan,
> >> In practice I suspect it makes no difference that the rfkill and
> >> backlight devices are exported as virtual devices with no physical
> >> parent. I just don't think it's "right" :-).
> >
> > it actually does make a difference for hardware detection. We wanna have
> > them hanging of the compal platform device.
>
> Ok. I wasn't sure that userspace was allowed to rely on that, but I
> re-read Documentation/ABI/testing/sysfs-devices and I see now that it
> can be allowed.
>
> Some of these issues with the compal-laptop work may come from copying
> dell-laptop. dell-laptop is the only driver which creates rfkill
> devices without a parent device. In fact, it doesn't even create a
> platform device :-).
then that should be fixed. All RFKILL switches should really have a
parent and not dangling around the virtual tree. Especially since they
have physical hardware in the system.
> I'll try sending a patch or two to clean up dell-laptop. I don't have
> the hardware but it should be pretty mechanical, almost a copy+paste
> job from a "good" driver.
That would be good. I don't have the hardware either, but others here
can test it.
Regards
Marcel
prev parent reply other threads:[~2009-08-18 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 23:27 [PATCH 3/3] Drop platform sysfs support Mario Limonciello
2009-08-18 8:43 ` Alan Jenkins
2009-08-18 9:54 ` Marcel Holtmann
2009-08-18 13:23 ` Alan Jenkins
2009-08-18 17:48 ` Mario Limonciello
2009-08-18 21:45 ` Marcel Holtmann [this message]
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=1250631934.5150.3.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=cezary.jackiewicz@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=sourcejedi.lkml@googlemail.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