linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Kyungmin Park <kmpark@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	soni.trilok@gmail.com
Subject: Re: [PATCH] Haptic class support (v2)
Date: Mon, 12 Oct 2009 17:42:08 +0200	[thread overview]
Message-ID: <ac3eb2510910120842m3129b76fyaa11b509e7f97038@mail.gmail.com> (raw)
In-Reply-To: <20091006074533.GA28889@july>

On Tue, Oct 6, 2009 at 09:45, Kyungmin Park <kmpark@infradead.org> wrote:
> This patch includes two haptic devices, isa1000 and isa1200
> ISA1000 is gpio based haptic, but isa1200 is based on I2C
> Both are working on Samsung SoCs and tested.
>
> To enable the haptic, echo 1 > /sys/class/haptic/${name}/enable
> You can adjust the level by echo ${level} > /sys/class/haptic/${name}/enable
> or
> With oneshot feature, echo ${msec time} > /sys/class/haptic/${name}/oneshot

Please never add any custom files to the top-level of a class
directory. This place is reserved for devices, and not for custom
files. It's a serious bug in the layout and API of sysfs that this
allowed at all.

If you need these subsystem-wide contols please use a bus and not a
class to stuff these files into a place where they don't mix up with
the list of devices belonging to a class. Buses have all devices in a
devices/ subdir so they will not conflict.

Thanks,
Kay

  parent reply	other threads:[~2009-10-12 15:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  7:45 [PATCH] Haptic class support (v2) Kyungmin Park
2009-10-06 15:25 ` Randy Dunlap
2009-10-06 18:35 ` Trilok Soni
2009-10-07  5:13   ` Kyungmin Park
2009-10-11  9:05 ` Pavel Machek
2009-10-12  0:32   ` Kyungmin Park
2009-10-12 13:44     ` Trilok Soni
2009-10-12 14:40       ` Greg KH
2009-10-13 11:05     ` Pavel Machek
2009-10-12 15:42 ` Kay Sievers [this message]
2009-10-12 16:20   ` Mark Brown
2009-10-13 16:45 ` Kay Sievers
2009-10-20  6:44   ` Trilok Soni

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=ac3eb2510910120842m3129b76fyaa11b509e7f97038@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=kmpark@infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soni.trilok@gmail.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;
as well as URLs for NNTP newsgroup(s).