From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>
Subject: Re: [PATCH 0/4] Current ad7879 patches
Date: Wed, 30 Jun 2010 01:03:45 -0700 [thread overview]
Message-ID: <20100630080345.GC4154@core.coreip.homeip.net> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D5917712E66DFF408@LIMKCMBX1.ad.analog.com>
On Tue, Jun 29, 2010 at 01:10:38PM +0100, Hennerich, Michael wrote:
> Dmitry Torokhov wrote on 2010-06-25:
> > Mike, Michael,
> >
> > I was looking through outstanding patches to ad7879 and here they are.
> > Since I made some changes to the patches you wrote and there also some
> > new code and I do not have the hardware I'd appreciate if you could
> > try them out so they can be applied.
> >
> > Thank you.
> >
>
> Hi Dmitry,
>
> I tested your ad7879 patch set -
> A few issues see patch below.
>
> -Fix ad7879_probe() parameter passing.
> -Add missing input_set_drvdata()
> -Avoid unbalanced irq enable warning: disable_irq() after request.
> -Fix sysfs disable hook logic: the file is called disable so don't treat it as enable.
>
Thanks for catching all the mistakes Michael. Regardgin disable_irq() -
do you think it would be even better to call __ad7879_disable() there to
make sure the chip is in low power mode? And I guess we need to add
matching enable_irq() in error handlig path and in ad7879_remove() in
case we reload the driver...
BTW, I will be applying the other 2 patches you sent.
--
Dmitry
next prev parent reply other threads:[~2010-06-30 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 8:22 [PATCH 0/4] Current ad7879 patches Dmitry Torokhov
2010-06-25 8:22 ` [PATCH 1/4] Input: ad7879 - use threaded IRQ Dmitry Torokhov
2010-06-25 8:22 ` [PATCH 2/4] Input: ad7879 - split bus logic out Dmitry Torokhov
2010-06-29 6:08 ` Mike Frysinger
2010-06-25 8:22 ` [PATCH 3/4] Input: ad7879 - add open and close methods Dmitry Torokhov
2010-06-25 8:22 ` [PATCH 4/4] Input: ad7879 - use i2c_smbus_read_i2c_block_data() to lower overhead Dmitry Torokhov
2010-06-29 12:10 ` [PATCH 0/4] Current ad7879 patches Hennerich, Michael
2010-06-30 8:03 ` Dmitry Torokhov [this message]
2010-06-30 8:40 ` Hennerich, Michael
2010-06-30 9:07 ` Dmitry Torokhov
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=20100630080345.GC4154@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=linux-input@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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).