From: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
To: linux-input@vger.kernel.org
Cc: linux-can@vger.kernel.org,
Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
Subject: [PATCH 5/6] cap11xx: enable all 8 inputs
Date: Sun, 29 Dec 2019 20:21:16 +0100 [thread overview]
Message-ID: <1577647277-8298-6-git-send-email-dev.kurt@vandijck-laurijssen.be> (raw)
In-Reply-To: <1577647277-8298-1-git-send-email-dev.kurt@vandijck-laurijssen.be>
Signed-off-by: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
---
drivers/input/keyboard/cap11xx.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/input/keyboard/cap11xx.c b/drivers/input/keyboard/cap11xx.c
index b666e9e..cdcc89b9 100644
--- a/drivers/input/keyboard/cap11xx.c
+++ b/drivers/input/keyboard/cap11xx.c
@@ -117,13 +117,13 @@ enum {
{ CAP11XX_REG_NOISE_FLAG_STATUS, 0x00 },
{ CAP11XX_REG_SENSITIVITY_CONTROL, 0x2f },
{ CAP11XX_REG_CONFIG, 0x20 },
- { CAP11XX_REG_SENSOR_ENABLE, 0x3f },
+ { CAP11XX_REG_SENSOR_ENABLE, 0xff },
{ CAP11XX_REG_SENSOR_CONFIG, 0xa4 },
{ CAP11XX_REG_SENSOR_CONFIG2, 0x07 },
{ CAP11XX_REG_SAMPLING_CONFIG, 0x39 },
{ CAP11XX_REG_CALIBRATION, 0x00 },
- { CAP11XX_REG_INT_ENABLE, 0x3f },
- { CAP11XX_REG_REPEAT_RATE, 0x3f },
+ { CAP11XX_REG_INT_ENABLE, 0xff },
+ { CAP11XX_REG_REPEAT_RATE, 0xff },
{ CAP11XX_REG_MT_CONFIG, 0x80 },
{ CAP11XX_REG_MT_PATTERN_CONFIG, 0x00 },
{ CAP11XX_REG_MT_PATTERN, 0x3f },
@@ -134,6 +134,8 @@ enum {
{ CAP11XX_REG_SENSOR_THRESH(3), 0x40 },
{ CAP11XX_REG_SENSOR_THRESH(4), 0x40 },
{ CAP11XX_REG_SENSOR_THRESH(5), 0x40 },
+ { CAP11XX_REG_SENSOR_THRESH(6), 0x40 },
+ { CAP11XX_REG_SENSOR_THRESH(7), 0x40 },
{ CAP11XX_REG_SENSOR_NOISE_THRESH, 0x01 },
{ CAP11XX_REG_STANDBY_CHANNEL, 0x00 },
{ CAP11XX_REG_STANDBY_CONFIG, 0x39 },
@@ -157,6 +159,8 @@ static bool cap11xx_volatile_reg(struct device *dev, unsigned int reg)
case CAP11XX_REG_SENOR_DELTA(3):
case CAP11XX_REG_SENOR_DELTA(4):
case CAP11XX_REG_SENOR_DELTA(5):
+ case CAP11XX_REG_SENOR_DELTA(6):
+ case CAP11XX_REG_SENOR_DELTA(7):
case CAP11XX_REG_PRODUCT_ID:
case CAP11XX_REG_MANUFACTURER_ID:
case CAP11XX_REG_REVISION:
--
1.8.5.rc3
next prev parent reply other threads:[~2019-12-29 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 19:21 [RFC] input: cap11xx: plasma globe proof Kurt Van Dijck
2019-12-29 19:21 ` [PATCH 1/6] cap11xx: set device driver_data Kurt Van Dijck
2019-12-29 19:21 ` [PATCH 2/6] cap11xx: support cap1208 Kurt Van Dijck
2019-12-29 19:21 ` [PATCH 3/6] cap11xx: polling mode without irq Kurt Van Dijck
2019-12-29 19:21 ` [PATCH 4/6] cap11xx: add register definition for LED_LINK Kurt Van Dijck
2019-12-29 19:21 ` Kurt Van Dijck [this message]
2019-12-29 19:21 ` [PATCH 6/6] cap11xx: export major chip settings to sysfs Kurt Van Dijck
2020-01-09 20:03 ` [RFC] input: cap11xx: plasma globe proof Kurt Van Dijck
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=1577647277-8298-6-git-send-email-dev.kurt@vandijck-laurijssen.be \
--to=dev.kurt@vandijck-laurijssen.be \
--cc=linux-can@vger.kernel.org \
--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.