From: Trilok Soni <soni.trilok@gmail.com>
To: Kyungmin Park <kyungmin.park@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Bill Gatliff <bgat@billgatliff.com>,
ben-linux@fluff.org
Subject: Re: [PATCH 5/6] haptic: Samsung SoCs PWM controlled haptic support
Date: Thu, 8 Oct 2009 23:58:37 +0530 [thread overview]
Message-ID: <5d5443650910081128l58f45148m87735185a0094c31@mail.gmail.com> (raw)
In-Reply-To: <20091007061822.GA7602@july>
Adding Bill Gatliff.
Hi Kyungmin,
Most of the driver looks fine. I have only one generic comment, but
not for this driver:
- Someone should really work on getting PWM framework (may be the one
written by Bill Gatliff) into the kernel, because
if we don't do this and if new PWM controller provides it's own APIs
then we can't leverage the chips using them, like the
case here for ISA1000 and ISA1200. These chips are using the pwm
APIs exported by Samsung PWM controller, but it would
be painful to integrate other PWM controller if that has slightly
little different API due to its nature.
So, it would be better to get one generic PWM framework mainline in
the kernel.
> +static int __devexit samsung_pwm_haptic_remove(struct platform_device *pdev)
> +{
> + struct samsung_pwm_haptic *haptic = platform_get_drvdata(pdev);
> +
> + samsung_pwm_haptic_set(&haptic->cdev, HAPTIC_OFF);
> + del_timer_sync(&haptic->timer);
cancel_work_sync ?
--
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni
next prev parent reply other threads:[~2009-10-08 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 6:18 [PATCH 5/6] haptic: Samsung SoCs PWM controlled haptic support Kyungmin Park
2009-10-08 18:28 ` Trilok Soni [this message]
2009-10-08 18:36 ` Bill Gatliff
2009-10-08 23:51 ` Kyungmin Park
2009-10-09 8:30 ` Trilok Soni
2009-10-09 8:32 ` Trilok Soni
2009-10-09 20:41 ` Bill Gatliff
2009-10-12 19:22 ` RFC: Proposed PWM device API Bill Gatliff
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=5d5443650910081128l58f45148m87735185a0094c31@mail.gmail.com \
--to=soni.trilok@gmail.com \
--cc=ben-linux@fluff.org \
--cc=bgat@billgatliff.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.