From: Randy Dunlap <rdunlap@infradead.org>
To: Roy Im <roy.im.opensource@diasemi.com>,
Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Brian Masney <masneyb@onstation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
Lee Jones <lee.jones@linaro.org>, Luca Weiss <luca@z3ntu.xyz>,
Maximilian Luz <luzmaximilian@gmail.com>,
Pascal PAILLET-LME <p.paillet@st.com>,
Rob Herring <robh@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Support Opensource <Support.Opensource@diasemi.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>
Subject: Re: [PATCH V17 3/3] Input: new da7280 haptic driver
Date: Thu, 23 Jul 2020 22:48:47 -0700 [thread overview]
Message-ID: <0f604bb1-f8b8-b262-c8ae-b346755b99f1@infradead.org> (raw)
Message-ID: <20200724054847.-NOl-RKZg6CRNfkGo1CuXk4znhuLGRT7PlpbUWsUddg@z> (raw)
In-Reply-To: <DB8PR10MB343624BF003338E8B34439AC85770@DB8PR10MB3436.EURPRD10.PROD.OUTLOOK.COM>
On 7/23/20 10:47 PM, Roy Im wrote:
> OK, thanks for your comments. To be clearer, I would like to update as below if you agree
>
> depends on INPUT && I2C
> ...
> The haptics can be controlled by PWM or GPIO
> with I2C communication.
Yes, that sounds good. Thanks.
--
~Randy
next prev parent reply other threads:[~2020-07-24 5:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1595516501.git.Roy.Im@diasemi.com>
2020-07-23 15:01 ` [PATCH V17 3/3] Input: new da7280 haptic driver Roy Im
2020-07-23 20:50 ` Randy Dunlap
2020-07-24 1:54 ` Roy Im
2020-07-24 2:56 ` Randy Dunlap
2020-07-24 5:47 ` Roy Im
2020-07-24 5:47 ` Roy Im
2020-07-24 5:48 ` Randy Dunlap [this message]
2020-07-24 5:48 ` Randy Dunlap
2020-07-23 20:55 ` Randy Dunlap
2020-07-24 2:06 ` Roy Im
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=0f604bb1-f8b8-b262-c8ae-b346755b99f1@infradead.org \
--to=rdunlap@infradead.org \
--cc=Support.Opensource@diasemi.com \
--cc=bgolaszewski@baylibre.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=luzmaximilian@gmail.com \
--cc=masneyb@onstation.org \
--cc=p.paillet@st.com \
--cc=robh@kernel.org \
--cc=roy.im.opensource@diasemi.com \
--cc=sameo@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).