linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trilok Soni <tsoni@codeaurora.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org,
	Mohan Pallaka <mpallaka@codeaurora.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH 2/2] input: misc: Add support for isa1200 chip
Date: Mon, 21 Mar 2011 12:36:09 +0530	[thread overview]
Message-ID: <4D86F8E1.8060502@codeaurora.org> (raw)
In-Reply-To: <1299496182-26177-3-git-send-email-mpallaka@codeaurora.org>

Hi Dmitry,

On 3/7/2011 4:39 PM, Mohan Pallaka wrote:
> From: Kyungmin Park <kyungmin.park@samsung.com>
> 
> isa1200 chip can be used to generate vibrations to indicate
> silent alerts, providing gaming haptic actions or vibrations
> in response to touches. It can operate in two modes, pwm
> generation and pwm input mode. Pwm generation mode requires
> external clock and pwm input mode needs the pwm signal to be
> given as input to the chip.
> 

Could you please review this patch series?

---Trilok Soni

-- 
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  parent reply	other threads:[~2011-03-21  7:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 11:09 [PATCH 0/2] Support for isa1200 haptic chip Mohan Pallaka
2011-03-07 11:09 ` [PATCH 1/2] pwm: Add __weak attributed functions for pwm operations Mohan Pallaka
2011-03-10 12:27   ` Mohan Pallaka
2011-03-07 11:09 ` [PATCH 2/2] input: misc: Add support for isa1200 chip Mohan Pallaka
     [not found]   ` <1299496182-26177-3-git-send-email-mpallaka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-03-10 12:28     ` Mohan Pallaka
2011-03-21  7:06   ` Trilok Soni [this message]
2011-03-24  7:49   ` Dmitry Torokhov
2011-04-06  6:03     ` Mohan Pallaka
2011-03-10 12:23 ` [PATCH 0/2] Support for isa1200 haptic chip Mohan Pallaka
  -- strict thread matches above, loose matches on Subject: below --
2011-04-13 12:25 Mohan Pallaka
     [not found] ` <1302697533-20456-1-git-send-email-mpallaka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-04-13 12:25   ` [PATCH 2/2] input: misc: Add support for isa1200 chip Mohan Pallaka
     [not found]     ` <1302697533-20456-3-git-send-email-mpallaka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-04-14  6:54       ` Mohan Pallaka
2011-04-29 12:48         ` Mohan Pallaka
     [not found]           ` <4DBAB3A2.9040100-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-05-01  5:31             ` Dmitry Torokhov
2011-05-13 12:43 [PATCH 0/2] Support for isa1200 haptic chip Mohan Pallaka
     [not found] ` <1305290602-29859-1-git-send-email-mpallaka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-05-13 12:43   ` [PATCH 2/2] input: misc: Add support for isa1200 chip Mohan Pallaka
2011-05-18  5:18 [PATCH 0/2] Support for isa1200 haptic chip Mohan Pallaka
2011-05-18  5:18 ` [PATCH 2/2] input: misc: Add support for isa1200 chip Mohan Pallaka

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=4D86F8E1.8060502@codeaurora.org \
    --to=tsoni@codeaurora.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpallaka@codeaurora.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;
as well as URLs for NNTP newsgroup(s).