All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raphael Derosso Pereira <raphaelpereira@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Atmel AT42QT2160 sensor chip input driver
Date: Tue, 22 Sep 2009 11:11:43 -0300	[thread overview]
Message-ID: <f20381800909220711g6e845feree34c15085a8b1c0@mail.gmail.com> (raw)
In-Reply-To: <f20381800909220441l57e7b636qdb96f6528505c7c2@mail.gmail.com>

Hello Dmitry,

I managed to get a working copy of your 'for-linus' branch.

I compiled and tested it and it is working fine! I would just remove
the first #include <autoconf.h> as it was only added for the
CONFIG_QT2160_DEBUG you removed.

Also, this chip is capable of performing some ajustments, like adding
keys to groups to avoid double detection, setting up sensibility,
detection thresholds, etc... I was wondering how to put that to
userspace, through sysfs, evdev ioctl or a /dev entry. What do you
suggest???

--
From: Raphael Derosso Pereira <raphaelpereira@gmail.com>

Inclusion cleanup

Signed-off-by: Raphael Derosso Pereira <raphaelpereira@gmail.com>
--
diff --git a/drivers/input/keyboard/qt2160.c b/drivers/input/keyboard/qt2160.c
index 0d57c17..191cc51 100644
--- a/drivers/input/keyboard/qt2160.c
+++ b/drivers/input/keyboard/qt2160.c
@@ -18,8 +18,6 @@
  *  Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
  */

-#include <linux/autoconf.h>
-
 #include <linux/kernel.h>
 #include <linux/init.h>
 #include <linux/module.h>


2009/9/22 Raphael Derosso Pereira <raphaelpereira@gmail.com>:
> Hello,
>
> 2009/9/22 Dmitry Torokhov <dmitry.torokhov@gmail.com>:
>> Hi Raphael,
>>
>>
>> I don't think we need a Kconfig entry for debugging. A person who wants
>> to debug such driver can easily turn on debugging manually.
>
> Ok.
>
>>
>> We normally try to allocate all necessary resources in probe() so that
>> if device is bound to a driver it should work unless it is broken. Since
>> there is no way to shut off IRQs while IRQ handler is registered it does
>> not make sense to have open and close if we allocate IRQ in probe().
>
> Agreed.
>
>>
>> Please take a look at the latest version that I have in 'for-linus'
>> branch in my tree on kernel.org and shout if you see something wrong.
>
> How am I supposed to do that?
>
>>
>> Thanks.
>>
>> --
>> Dmitry
>>
>
>
>
> --
> Raphael Derosso Pereira
> Engenheiro de Computação
> msn: rderossopereira@hotmail.com
> Skype: rderossopereira
>



-- 
Raphael Derosso Pereira
Engenheiro de Computação
msn: rderossopereira@hotmail.com
Skype: rderossopereira
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-09-22 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 20:15 [PATCH] Atmel AT42QT2160 sensor chip input driver Raphael Derosso Pereira
2009-09-15  4:26 ` Dmitry Torokhov
2009-09-20 13:03   ` Raphael Derosso Pereira
2009-09-21 15:35   ` Raphael Derosso Pereira
2009-09-22  5:52     ` Dmitry Torokhov
2009-09-22 11:41       ` Raphael Derosso Pereira
2009-09-22 14:11         ` Raphael Derosso Pereira [this message]

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=f20381800909220711g6e845feree34c15085a8b1c0@mail.gmail.com \
    --to=raphaelpereira@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@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.