mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: <ilkka.koskinen@nokia.com>
Cc: <grant.likely@secretlab.ca>, <linux-input@vger.kernel.org>,
	<dmitry.torokhov@gmail.com>,
	<spi-devel-general@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] input: spi: Driver for SPI data stream driven vibrator
Date: Wed, 27 Oct 2010 10:19:35 +0100	[thread overview]
Message-ID: <20101027101935.1b50b9dd@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <F80267346F10C541946CBE8909F1C39E35932598BB@NOK-EUMSG-02.mgdnok.nokia.com>

> The driver could, of course, calculate the bit streams with help of
> board specific functions. It was just thought that tuning vibration
> device would be a lot easier, if we could just modify the bit streams
> provided by user space application. In fact, the bit stream basically
> consists of series of PWM pulses that are fed to the vibra.
> 
> Perhaps, calculating the waveforms in the driver at probe time would
> be the most natural choice :\

Or assuming its a trivial conversion accepting them in a standard format
and doing a quick pass across them ?

(and failing that adding and documenting the format..)

  parent reply	other threads:[~2010-10-27  9:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 13:31 Ilkka Koskinen
2010-10-26 11:13 ` Grant Likely
2010-10-26 11:17   ` Alan Cox
2010-10-26 16:52     ` ilkka.koskinen
2010-10-26 16:50   ` ilkka.koskinen
2010-10-27  8:47     ` Grant Likely
2010-10-27  8:58       ` Dmitry Torokhov
2010-10-27  9:19     ` Alan Cox [this message]
2010-10-26 16:09 ` Dmitry Torokhov
2010-10-27 12:55   ` ilkka.koskinen
2010-11-07 23:51 ` Alan Cox
2010-11-08 11:08   ` ilkka.koskinen
2010-11-08 11:38     ` Alan Cox
2010-11-08 12:18       ` ilkka.koskinen

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=20101027101935.1b50b9dd@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dmitry.torokhov@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=ilkka.koskinen@nokia.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®