Input: cap11xx - Add support for CAP1114
Subsystems (3)
v3 cover Input: cap11xx - Add support for CAP1114
CAP1114 is a 14-channel capacitive touch sensor with 11 LED outputs and hardware reset support.
Patches 1-4 perform driver cleanup and DT binding tweaks. Patches 5-6 add reset-gpios support for CAP11xx. Patches 7-10 add support for CAP1114.
Changes in v3:
- Simplified the logic of the reset pin operation.
- Adjust linux,keycodes configuration for CAP11xx.
- Drop unnecessary CAP11XX_REG_SENSOR_THRESH(8).
- Checks for the presence of microchip,calib-sensitivity and microchip,signal-guard properties before processing them.
- Link to v2:
https://lore.kernel.org/all/[email protected]/
Changes in v2:
- Drop LED property tweaks, keep only reg changes and node regex update in DT bindings.
- Split microchip,cap1126 LED reg constraints into a separate patch.
- Replace usleep_range() with msleep() for 500 ms delay during reset pin handling.
- Add missing <linux/delay.h> for usleep_range() and msleep().
- Add CAP1114 to unsupported enum for microchip,signal-guard and microchip,calib-sensitivity
- Add constraint for linux,keycodes to support CAP1114.
- When reading CAP1114 button status, mask STATUS1 to bits 0-5 and OR with STATUS2.
- Adjust code style.
- Link to v1:
https://lore.kernel.org/all/[email protected]
Jun Yan (10):
Input: cap11xx - clean up duplicate log and add probe error logs
Input: cap11xx - remove unused register macros
dt-bindings: input: microchip,cap11xx: Update datasheet URL and LED
reg range
dt-bindings: input: microchip,cap11xx: Add microchip,cap1126 LED reg
constraints
dt-bindings: input: microchip,cap11xx: Add reset-gpios property
Input: cap11xx - add reset gpio support
Input: cap11xx - refactor code for better CAP1114 support.
Input: cap11xx - guard unsupported DT properties before parsing
dt-bindings: input: microchip,cap11xx: Add CAP1114 support
Input: cap11xx - add support for CAP1114
.../bindings/input/microchip,cap11xx.yaml | 90 +++++- drivers/input/keyboard/cap11xx.c | 280 +++++++++++------- 2 files changed, 253 insertions(+), 117 deletions(-)
Signature · 1 line
2.54.0
PATCH v3 1/10 Input: cap11xx - clean up duplicate log and add probe error logs
Duplicated device detection log exists at line 537 and line 542, which brings redundant kernel print messages. Drop one redundant log entry to clean up dmesg output.
Meanwhile add missing error logs when I2C communication fails during driver probe(), helping debug.
--- drivers/input/keyboard/cap11xx.c | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-)
drivers/input/keyboard/cap11xx.c +4 -7
@@ -512,7 +512,7 @@ static int cap11xx_i2c_probe(struct i2c_client *i2c_client) error =regmap_read (priv->regmap,CAP11XX_REG_PRODUCT_ID , &val);if (error) -return error; +return dev_err_probe (dev, error,"Failed to read product ID\n" );if (val != cap->product_id) { dev_err(dev, "Product ID: Got 0x%02x, expected 0x%02x\n",
@@ -522,7 +522,7 @@ static int cap11xx_i2c_probe(struct i2c_client *i2c_client) error =regmap_read (priv->regmap,CAP11XX_REG_MANUFACTURER_ID , &val);if (error) -return error; +return dev_err_probe (dev, error,"Failed to read manufacturer ID\n" );if (val !=CAP11XX_MANUFACTURER_ID ) { dev_err(dev, "Manufacturer ID: Got 0x%02x, expected 0x%02x\n",
@@ -531,11 +531,8 @@ static int cap11xx_i2c_probe(struct i2c_client *i2c_client) } error =regmap_read (priv->regmap,CAP11XX_REG_REVISION , &rev); -if (error <0 ) -return error; - -dev_info (dev,"CAP11XX detected, model %s, revision 0x%02x\n" , - id->name, rev); +if (error) +return dev_err_probe (dev, error,"Failed to read revision\n" ); priv->model = cap;
Signature · 1 line
2.54.0
PATCH v3 2/10 Input: cap11xx - remove unused register macros
In reply to Jun YanRemove unused register address macros and unused definitions in the cap11xx_reg_defaults array and cap11xx_volatile_reg.
This cleanup reduces code clutter and makes the driver easier to maintain without affecting functionality.
--- drivers/input/keyboard/cap11xx.c | 58 -------------------------------- 1 file changed, 58 deletions(-)
drivers/input/keyboard/cap11xx.c +0 -58
@@ -20,53 +20,23 @@#define CAP11XX_REG_MAIN_CONTROL_GAIN_SHIFT (6)#define CAP11XX_REG_MAIN_CONTROL_GAIN_MASK (0xc0)#define CAP11XX_REG_MAIN_CONTROL_DLSEEP BIT(4) -#define CAP11XX_REG_GENERAL_STATUS 0x02#define CAP11XX_REG_SENSOR_INPUT 0x03 -#define CAP11XX_REG_NOISE_FLAG_STATUS 0x0a -#define CAP11XX_REG_SENOR_DELTA (X ) (0x10 + (X))#define CAP11XX_REG_SENSITIVITY_CONTROL 0x1f#define CAP11XX_REG_SENSITIVITY_CONTROL_DELTA_SENSE_MASK 0x70 -#define CAP11XX_REG_CONFIG 0x20 -#define CAP11XX_REG_SENSOR_ENABLE 0x21 -#define CAP11XX_REG_SENSOR_CONFIG 0x22 -#define CAP11XX_REG_SENSOR_CONFIG2 0x23 -#define CAP11XX_REG_SAMPLING_CONFIG 0x24 -#define CAP11XX_REG_CALIBRATION 0x26 -#define CAP11XX_REG_INT_ENABLE 0x27#define CAP11XX_REG_REPEAT_RATE 0x28#define CAP11XX_REG_SIGNAL_GUARD_ENABLE 0x29 -#define CAP11XX_REG_MT_CONFIG 0x2a -#define CAP11XX_REG_MT_PATTERN_CONFIG 0x2b -#define CAP11XX_REG_MT_PATTERN 0x2d -#define CAP11XX_REG_RECALIB_CONFIG 0x2f#define CAP11XX_REG_SENSOR_THRESH (X ) (0x30 + (X)) -#define CAP11XX_REG_SENSOR_NOISE_THRESH 0x38 -#define CAP11XX_REG_STANDBY_CHANNEL 0x40 -#define CAP11XX_REG_STANDBY_CONFIG 0x41 -#define CAP11XX_REG_STANDBY_SENSITIVITY 0x42 -#define CAP11XX_REG_STANDBY_THRESH 0x43#define CAP11XX_REG_CONFIG2 0x44#define CAP11XX_REG_CONFIG2_ALT_POL BIT(6) -#define CAP11XX_REG_SENSOR_BASE_CNT (X ) (0x50 + (X)) -#define CAP11XX_REG_LED_POLARITY 0x73#define CAP11XX_REG_LED_OUTPUT_CONTROL 0x74#define CAP11XX_REG_CALIB_SENSITIVITY_CONFIG 0x80#define CAP11XX_REG_CALIB_SENSITIVITY_CONFIG2 0x81 - -#define CAP11XX_REG_LED_DUTY_CYCLE_1 0x90 -#define CAP11XX_REG_LED_DUTY_CYCLE_2 0x91 -#define CAP11XX_REG_LED_DUTY_CYCLE_3 0x92#define CAP11XX_REG_LED_DUTY_CYCLE_4 0x93 -#define CAP11XX_REG_LED_DUTY_MIN_MASK (0x0f) -#define CAP11XX_REG_LED_DUTY_MIN_MASK_SHIFT (0)#define CAP11XX_REG_LED_DUTY_MAX_MASK (0xf0)#define CAP11XX_REG_LED_DUTY_MAX_MASK_SHIFT (4)#define CAP11XX_REG_LED_DUTY_MAX_VALUE (15) -#define CAP11XX_REG_SENSOR_CALIB (0xb1 + (X)) -#define CAP11XX_REG_SENSOR_CALIB_LSB1 0xb9 -#define CAP11XX_REG_SENSOR_CALIB_LSB2 0xba#define CAP11XX_REG_PRODUCT_ID 0xfd#define CAP11XX_REG_MANUFACTURER_ID 0xfe#define CAP11XX_REG_REVISION 0xff
@@ -111,37 +81,15 @@ struct cap11xx_hw_model {static const struct reg_default cap11xx_reg_defaults[] = { {CAP11XX_REG_MAIN_CONTROL ,0x00 }, - {CAP11XX_REG_GENERAL_STATUS ,0x00 }, - {CAP11XX_REG_SENSOR_INPUT ,0x00 }, - {CAP11XX_REG_NOISE_FLAG_STATUS ,0x00 }, {CAP11XX_REG_SENSITIVITY_CONTROL ,0x2f }, - {CAP11XX_REG_CONFIG ,0x20 }, - {CAP11XX_REG_SENSOR_ENABLE ,0x3f }, - {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_MT_CONFIG ,0x80 }, - {CAP11XX_REG_MT_PATTERN_CONFIG ,0x00 }, - {CAP11XX_REG_MT_PATTERN ,0x3f }, - {CAP11XX_REG_RECALIB_CONFIG ,0x8a }, {CAP11XX_REG_SENSOR_THRESH (0 ),0x40 }, {CAP11XX_REG_SENSOR_THRESH (1 ),0x40 }, {CAP11XX_REG_SENSOR_THRESH (2 ),0x40 }, {CAP11XX_REG_SENSOR_THRESH (3 ),0x40 }, {CAP11XX_REG_SENSOR_THRESH (4 ),0x40 }, {CAP11XX_REG_SENSOR_THRESH (5 ),0x40 }, - {CAP11XX_REG_SENSOR_NOISE_THRESH ,0x01 }, - {CAP11XX_REG_STANDBY_CHANNEL ,0x00 }, - {CAP11XX_REG_STANDBY_CONFIG ,0x39 }, - {CAP11XX_REG_STANDBY_SENSITIVITY ,0x02 }, - {CAP11XX_REG_STANDBY_THRESH ,0x40 }, {CAP11XX_REG_CONFIG2 ,0x40 }, - {CAP11XX_REG_LED_POLARITY ,0x00 }, - {CAP11XX_REG_SENSOR_CALIB_LSB1 ,0x00 }, - {CAP11XX_REG_SENSOR_CALIB_LSB2 ,0x00 }, };static bool cap11xx_volatile_reg (struct device *dev,unsigned int reg)
@@ -149,12 +97,6 @@ static bool cap11xx_volatile_reg(struct device *dev, unsigned int reg)switch (reg) {case CAP11XX_REG_MAIN_CONTROL :case CAP11XX_REG_SENSOR_INPUT : -case CAP11XX_REG_SENOR_DELTA (0 ): -case CAP11XX_REG_SENOR_DELTA (1 ): -case CAP11XX_REG_SENOR_DELTA (2 ): -case CAP11XX_REG_SENOR_DELTA (3 ): -case CAP11XX_REG_SENOR_DELTA (4 ): -case CAP11XX_REG_SENOR_DELTA (5 ):return true; }
Signature · 1 line
2.54.0
[email protected]
AI reviewRe: [PATCH v3 02/10] Input: cap11xx - remove unused register macros
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
New issues:
- [Medium] Removing sensor delta registers from the volatile register list causes regmap to incorrectly cache their values, breaking debugfs observability.
Pre-existing issues:
- [High] The driver requests its IRQ after registering the input device, creating a race condition where an unhandled interrupt can permanently disable the device. --
commit 72bbdd7bb3155f054afabfd004f5e097d568001b
Author: Jun Yan <[email protected]>
Input: cap11xx - remove unused register macros
Remove unused register address macros and unused definitions in the cap11xx_reg_defaults array and cap11xx_volatile_reg. This cleanup reduces code clutter and makes the driver easier to maintain.
Quoted 4 lines
drivers/input/keyboard/cap11xx.c +0
-0
[ ... ]
drivers/input/keyboard/cap11xx.c static bool cap11xx_volatile_reg(struct device *dev, unsigned int reg) · line 157
Quoted 10 lines
drivers/input/keyboard/cap11xx.c +0
-6@@ -149,12 +97,6 @@ static bool cap11xx_volatile_reg(struct device *dev, unsigned int reg)switch (reg) {case CAP11XX_REG_MAIN_CONTROL :case CAP11XX_REG_SENSOR_INPUT : -case CAP11XX_REG_SENOR_DELTA (0 ): -case CAP11XX_REG_SENOR_DELTA (1 ): -case CAP11XX_REG_SENOR_DELTA (2 ): -case CAP11XX_REG_SENOR_DELTA (3 ): -case CAP11XX_REG_SENOR_DELTA (4 ): -case CAP11XX_REG_SENOR_DELTA (5 ):
[Severity: Medium]
Does removing the sensor delta registers from the volatile list cause a regression for observability via the regmap debugfs interface?
These registers contain real-time capacitance delta hardware values that are continuously updated by the device. Treating them as non-volatile causes regmap to cache them on the first read, resulting in stale values for any subsequent reads by tuning tools or developers.
drivers/input/keyboard/cap11xx.c static bool cap11xx_volatile_reg(struct device *dev, unsigned int reg) · line 102
Quoted 3 lines
drivers/input/keyboard/cap11xx.c +0
-0return true; }
[Severity: High]
This isn't a bug introduced by this patch, but I noticed a pre-existing probe ordering flaw in cap11xx_i2c_probe():
error = input_register_device(priv->idev); if (error) return error; error = devm_request_threaded_irq(dev, i2c_client->irq, NULL, cap11xx_thread_func, IRQF_ONESHOT, dev_name(dev), priv);
Could this sequence lead to the interrupt being permanently disabled?
Since input_register_device() exposes the device to userspace, a daemon can immediately open the device, waking the sensor from deep sleep.
If the sensor generates a hardware interrupt before devm_request_threaded_irq() completes, the generic IRQ core will receive an interrupt with no registered handler.
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=2
PATCH v3 3/10 dt-bindings: input: microchip,cap11xx: Update datasheet URL and LED reg range
In reply to Jun Yan- Add datasheet links for all supported CAP11xx variants.
- Update LED node regex and replace enum constraints with minimum/maximum for LED reg ranges in preparation for CAP1114 support.
CAP1114 has 11 LED channels. minimum/maximum constraints are easier to maintain than long enum lists when expanding channel count later.
--- .../bindings/input/microchip,cap11xx.yaml | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +14 -3
@@ -10,6 +10,15 @@ description: | The Microchip CAP1xxx Family of RightTouchTM multiple-channel capacitive touch controllers and LED drivers. The device communication via I2C only. + For more product information please see the links below: + CAP1106: https://ww1.microchip.com/downloads/en/DeviceDoc/00001624B.pdf + CAP1126: https://ww1.microchip.com/downloads/en/DeviceDoc/00001623B.pdf + CAP1188: https://ww1.microchip.com/downloads/en/DeviceDoc/00001620C.pdf + CAP1203: https://ww1.microchip.com/downloads/en/DeviceDoc/00001572B.pdf + CAP1206: https://ww1.microchip.com/downloads/en/DeviceDoc/00001567B.pdf + CAP1293: https://ww1.microchip.com/downloads/en/DeviceDoc/00001566B.pdf + CAP1298: https://ww1.microchip.com/downloads/en/DeviceDoc/00001571B.pdf + maintainers: - Rob Herring <[email protected]>
@@ -124,14 +133,16 @@ properties: The number of entries must correspond to the number of channels. patternProperties: - "^led@[0-7]$": + "^led@[0-9a-f]$": type: object description: CAP11xx LEDs $ref: /schemas/leds/common.yaml# properties: reg: - enum: [0, 1, 2, 3, 4, 5, 6, 7] + description: LED channel number + minimum: 0 + maximum: 7 label: true
@@ -158,7 +169,7 @@ allOf: - microchip,cap1298 then: patternProperties: - "^led@[0-7]$": false + "^led@": false - if: properties:
Signature · 1 line
2.54.0
Re: [PATCH v3 03/10] dt-bindings: input: microchip,cap11xx: Update datasheet URL and LED reg range
Quoted 33 lines · Jun Yan
- Add datasheet links for all supported CAP11xx variants.
- Update LED node regex and replace enum constraints with minimum/maximum for LED reg ranges in preparation for CAP1114 support.CAP1114 has 11 LED channels. minimum/maximum constraints are easier to maintain than long enum lists when expanding channel count later.
Signed-off-by Jun Yan <[email protected]>--- .../bindings/input/microchip,cap11xx.yaml | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +9
-0@@ -10,6 +10,15 @@ description: | The Microchip CAP1xxx Family of RightTouchTM multiple-channel capacitive touch controllers and LED drivers. The device communication via I2C only. + For more product information please see the links below: + CAP1106: https://ww1.microchip.com/downloads/en/DeviceDoc/00001624B.pdf + CAP1126: https://ww1.microchip.com/downloads/en/DeviceDoc/00001623B.pdf + CAP1188: https://ww1.microchip.com/downloads/en/DeviceDoc/00001620C.pdf + CAP1203: https://ww1.microchip.com/downloads/en/DeviceDoc/00001572B.pdf + CAP1206: https://ww1.microchip.com/downloads/en/DeviceDoc/00001567B.pdf + CAP1293: https://ww1.microchip.com/downloads/en/DeviceDoc/00001566B.pdf + CAP1298: https://ww1.microchip.com/downloads/en/DeviceDoc/00001571B.pdf + maintainers: - Rob Herring <[email protected]>
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml properties: · line 136
Quoted 5 lines
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +1
-1@@ -124,14 +133,16 @@ properties: The number of entries must correspond to the number of channels. patternProperties: - "^led@[0-7]$": + "^led@[0-9a-f]$":
This should be done alongside the cap1114 change, not here I think. The constraint relaxation doesn't make sense because the user is arriving in a later patch.
With it moved,
Although, should it not be led@[0-9a-b] if the max is 11?
pw-bot: changes-requested
Cheers,
Conor.
Quoted 25 lines
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +4
-2type: object description: CAP11xx LEDs $ref: /schemas/leds/common.yaml# properties: reg: - enum: [0, 1, 2, 3, 4, 5, 6, 7] + description: LED channel number + minimum: 0 + maximum: 7 label: true@@ -158,7 +169,7 @@ allOf: - microchip,cap1298 then: patternProperties: - "^led@[0-7]$": false + "^led@": false - if: properties:Signature · 1 line
2.54.0
Re: [PATCH v3 03/10] dt-bindings: input: microchip,cap11xx: Update datasheet URL and LED reg range
Quoted 39 lines · Jun Yan
Quoted 7 lines
- Add datasheet links for all supported CAP11xx variants.
- Update LED node regex and replace enum constraints with minimum/maximum for LED reg ranges in preparation for CAP1114 support.
=20
CAP1114 has 11 LED channels. minimum/maximum constraints are easier to maintain than long enum lists when expanding channel count later. =20Review
Quoted 6 lines
Signed-off-by Jun Yan <[email protected]>--- .../bindings/input/microchip,cap11xx.yaml | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)=20
(quoted diff) +0
-0ml
b/Documentation/devicetree/bindings/input/microchip,cap11xx.yamlDocumentation/devicetree/bindings/input/microchip,cap11xx.yaml description: | · line 10
Quoted 5 lines
index
7ade03f1b32b..9578c7c206a2100644Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +0
-0@@ -10,6 +10,15 @@ description: | The Microchip CAP1xxx Family of RightTouchTM multiple-channel capaciti=ve
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml description: | · line 11
Quoted 1 line
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +0
-0touch controllers and LED drivers. The device communication via I2C on=ly.
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml
Quoted 3 lines
=20
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +2
-0+ For more product information please see the links below: + CAP1106: https://ww1.microchip.com/downloads/en/DeviceDoc/00001624B.=Quoted 1 line
+ CAP1126: https://ww1.microchip.com/downloads/en/DeviceDoc/00001623B.=
Quoted 1 line
+ CAP1188: https://ww1.microchip.com/downloads/en/DeviceDoc/00001620C.=
Quoted 1 line
+ CAP1203: https://ww1.microchip.com/downloads/en/DeviceDoc/00001572B.=
Quoted 1 line
+ CAP1206: https://ww1.microchip.com/downloads/en/DeviceDoc/00001567B.=
Quoted 1 line
+ CAP1293: https://ww1.microchip.com/downloads/en/DeviceDoc/00001566B.=
Quoted 1 line
+ CAP1298: https://ww1.microchip.com/downloads/en/DeviceDoc/00001571B.=
Quoted 15 lines
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml properties: · line 136
Quoted 10 lines
+
maintainers:
- Rob Herring <[email protected]>
=20Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +0
-0@@ -124,14 +133,16 @@ properties: The number of entries must correspond to the number of channels.=20
patternProperties:Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +1
-1- "^led@[0-7]$": + "^led@[0-9a-f]$":This should be done alongside the cap1114 change, not here I think. The constraint relaxation doesn't make sense because the user is arriving in a later patch.
With it moved,
Thanks for your review feedback. I'll move this constraint change into the cap1114 patch and update it in v4.
Quoted 4 lines
Acked-by Conor Dooley <[email protected]>Although, should it not be led@[0-9a-b] if the max is 11?
Agreed. I will fix this in v4.
Quoted 30 lines
pw-bot: changes-requested
Cheers,
Conor.Quoted 25 lines
type: object
description: CAP11xx LEDs
$ref: /schemas/leds/common.yaml#
=20
properties:
reg:Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +3
-1- enum: [0, 1, 2, 3, 4, 5, 6, 7] + description: LED channel number + minimum: 0 + maximum: 7=20
label: true
=20Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +1
-1@@ -158,7 +169,7 @@ allOf: - microchip,cap1298 then: patternProperties: - "^led@[0-7]$": false + "^led@": false=20
- if:
properties:
--=20
2.54.0
=20
PATCH v3 4/10 dt-bindings: input: microchip,cap11xx: Add microchip,cap1126 LED reg constraints
In reply to Jun YanApply per-chip LED channel limits:
- CAP1126: max 2 channels (0-1)
- CAP1188: max 8 channels (0-7)
- CAP1106, CAP12xx: no LED support
--- .../bindings/input/microchip,cap11xx.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+)
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +13 -0
@@ -171,6 +171,19 @@ allOf: patternProperties: "^led@": false + - if: + properties: + compatible: + contains: + enum: + - microchip,cap1126 + then: + patternProperties: + "^led@": + properties: + reg: + maximum: 1 + - if: properties: compatible:
Signature · 1 line
2.54.0
Re: [PATCH v3 04/10] dt-bindings: input: microchip,cap11xx: Add microchip,cap1126 LED reg constraints
pw-bot: not-applicable
PATCH v3 5/10 dt-bindings: input: microchip,cap11xx: Add reset-gpios property
In reply to Jun YanAdd support for the optional reset-gpios property to describe the active-high reset pin for CAP1126/CAP1188 devices. Driving the GPIO high asserts reset and deep sleep, while driving it low releases reset for normal operation.
Restrict this property to be available only on CAP1126 and CAP1188 chips, as other CAP11xx variants do not have a hardware reset pin.
--- .../bindings/input/microchip,cap11xx.yaml | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+)
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +25 -0
@@ -49,6 +49,13 @@ properties: device's ALERT#/CM_IRQ# pin is connected to. The device only has one interrupt source. + reset-gpios: + description: | + GPIO connected to the active-high RESET pin of the chip; + driving it high asserts reset and deep sleep, while driving + it low releases reset for normal operation. + maxItems: 1 + autorepeat: description: | Enables the Linux input system's autorepeat feature on the input device.
@@ -157,6 +164,20 @@ patternProperties: allOf: - $ref: input.yaml + - if: + properties: + compatible: + contains: + enum: + - microchip,cap1106 + - microchip,cap1203 + - microchip,cap1206 + - microchip,cap1293 + - microchip,cap1298 + then: + properties: + reset-gpios: false + - if: properties: compatible:
@@ -207,6 +228,8 @@ additionalProperties: false examples: - | + #include <dt-bindings/gpio/gpio.h> + i2c { #address-cells = <1>; #size-cells = <0>;
@@ -228,6 +251,8 @@ examples: <109>, /* KEY_PAGEDOWN */ <104>; /* KEY_PAGEUP */ + reset-gpios = <&gpio 17 GPIO_ACTIVE_HIGH>; + #address-cells = <1>; #size-cells = <0>;
Signature · 1 line
2.54.0
PATCH v3 6/10 Input: cap11xx - add reset gpio support
In reply to Jun YanSome CAP11xx devices (CAP1126/CAP1188) have a dedicated RESET pin. Add hardware reset operation to improve device reliability and ensure proper initialization on probe.
--- drivers/input/keyboard/cap11xx.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
drivers/input/keyboard/cap11xx.c +15 -0
@@ -5,6 +5,7 @@* (c) 2014 Daniel Mack <[email protected]> */ +#include <linux/delay.h> #include <linux/kernel.h> #include <linux/module.h> #include <linux/interrupt.h>
@@ -43,6 +44,9 @@#define CAP11XX_MANUFACTURER_ID 0x5d +#define CAP11XX_T_RST_FILT_MIN_US 10000 +#define CAP11XX_T_RST_ON_MIN_MS 400 + #ifdef CONFIG_LEDS_CLASS struct cap11xx_led { struct cap11xx_priv *priv;
@@ -55,6 +59,7 @@ struct cap11xx_priv {struct regmap *regmap;struct device *dev;struct input_dev *idev; +struct gpio_desc *reset_gpio;const struct cap11xx_hw_model *model;struct cap11xx_led *leds;
@@ -452,6 +457,16 @@ static int cap11xx_i2c_probe(struct i2c_client *i2c_client)if (IS_ERR (priv->regmap))return PTR_ERR (priv->regmap); + priv->reset_gpio =devm_gpiod_get_optional (dev,"reset" ,GPIOD_OUT_HIGH ); +if (IS_ERR (priv->reset_gpio)) +return dev_err_probe (dev,PTR_ERR (priv->reset_gpio), +"Failed to get 'reset' GPIO\n" ); +else if (priv->reset_gpio) { +usleep_range (CAP11XX_T_RST_FILT_MIN_US ,CAP11XX_T_RST_FILT_MIN_US *2 ); +gpiod_set_value_cansleep (priv->reset_gpio,0 ); +msleep (CAP11XX_T_RST_ON_MIN_MS ); + } + error =regmap_read (priv->regmap,CAP11XX_REG_PRODUCT_ID , &val);if (error)return dev_err_probe (dev, error,"Failed to read product ID\n" );
Signature · 1 line
2.54.0
[email protected]
AI reviewRe: [PATCH v3 06/10] Input: cap11xx - add reset gpio support
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Low] Coding style violations: redundant 'else' after 'return' and inconsistent brace usage. --
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Coding style violations: redundant 'else' after 'return' and inconsistent brace usage. --
commit 2a7317102372f10d4bd76864cfeaec2d7955c415
Author: Jun Yan <[email protected]>
Input: cap11xx - add reset gpio support
This commit adds support for an optional hardware reset pin on CAP11xx devices to improve reliability and ensure proper initialization during probe.
Quoted 3 lines
drivers/input/keyboard/cap11xx.c +0
-0
[ ... ]
drivers/input/keyboard/cap11xx.c static int cap11xx_i2c_probe(struct i2c_client *i2c_client) · line 464
Quoted 9 lines
drivers/input/keyboard/cap11xx.c +5
-0@@ -452,6 +457,16 @@ static int cap11xx_i2c_probe(struct i2c_client *i2c_client)if (IS_ERR (priv->regmap))return PTR_ERR (priv->regmap); + priv->reset_gpio =devm_gpiod_get_optional (dev,"reset" ,GPIOD_OUT_HIGH ); +if (IS_ERR (priv->reset_gpio)) +return dev_err_probe (dev,PTR_ERR (priv->reset_gpio), +"Failed to get 'reset' GPIO\n" ); +else if (priv->reset_gpio) {
[Severity: Low]
This isn't a bug, but does this follow the standard kernel coding style?
Since the preceding if statement ends with a return, the else keyword here is redundant. Additionally, kernel style guidelines generally prefer that if one branch of a conditional requires braces, all branches should use them.
Could this be simplified by dropping the else and just using a separate if statement for checking priv->reset_gpio?
Quoted 6 lines
drivers/input/keyboard/cap11xx.c +5
-0+usleep_range (CAP11XX_T_RST_FILT_MIN_US ,CAP11XX_T_RST_FILT_MIN_US *2 ); +gpiod_set_value_cansleep (priv->reset_gpio,0 ); +msleep (CAP11XX_T_RST_ON_MIN_MS ); + } + error =regmap_read (priv->regmap,CAP11XX_REG_PRODUCT_ID , &val);
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=6
PATCH v3 7/10 Input: cap11xx - refactor code for better CAP1114 support.
In reply to Jun YanExtend cap11xx_hw_model structure to support CAP1114 with different register offsets and hardware characteristics:
- led_output_control_reg_base: different address on CAP1114
- sensor_input_reg_base: different address on CAP1114
- num_sensor_thresholds: separate value from num_channels for CAP1114
- has_repeat_en: repeat enable support, disabled by default on CAP1114
Include linux/bits.h, update the register operations related to LEDs.
--- drivers/input/keyboard/cap11xx.c | 73 +++++++++++++++++++++++--------- 1 file changed, 53 insertions(+), 20 deletions(-)
drivers/input/keyboard/cap11xx.c +53 -20
@@ -5,6 +5,7 @@* (c) 2014 Daniel Mack <[email protected]> */ +#include <linux/bits.h> #include <linux/delay.h> #include <linux/kernel.h> #include <linux/module.h>
@@ -35,7 +36,6 @@#define CAP11XX_REG_LED_DUTY_CYCLE_4 0x93#define CAP11XX_REG_LED_DUTY_MAX_MASK (0xf0) -#define CAP11XX_REG_LED_DUTY_MAX_MASK_SHIFT (4)#define CAP11XX_REG_LED_DUTY_MAX_VALUE (15)#define CAP11XX_REG_PRODUCT_ID 0xfd
@@ -76,10 +76,14 @@ struct cap11xx_priv {struct cap11xx_hw_model {u8 product_id; +u8 led_output_control_reg_base; +u8 sensor_input_reg_base;unsigned int num_channels;unsigned int num_leds; +unsigned int num_sensor_thresholds;bool has_gain;bool has_irq_config; +bool has_repeat_en;bool has_sensitivity_control;bool has_signal_guard; };
@@ -204,8 +208,8 @@ static int cap11xx_init_keys(struct cap11xx_priv *priv) }if (!of_property_read_u32_array (node,"microchip,input-threshold" , - priv->thresholds, priv->model->num_channels)) { -for (i =0 ; i < priv->model->num_channels; i++) { + priv->thresholds, priv->model->num_sensor_thresholds)) { +for (i =0 ; i < priv->model->num_sensor_thresholds; i++) {if (priv->thresholds[i] >127 ) {dev_err (dev,"Invalid input-threshold value %u\n" , priv->thresholds[i]);
@@ -279,10 +283,12 @@ static int cap11xx_init_keys(struct cap11xx_priv *priv)of_property_read_u32_array (node,"linux,keycodes" , priv->keycodes, priv->model->num_channels); -/* Disable autorepeat. The Linux input system has its own handling. */ - error =regmap_write (priv->regmap,CAP11XX_REG_REPEAT_RATE ,0 ); -if (error) -return error; +if (priv->model->has_repeat_en) { +/* Disable autorepeat. The Linux input system has its own handling. */ + error =regmap_write (priv->regmap,CAP11XX_REG_REPEAT_RATE ,0 ); +if (error) +return error; + }return 0 ; }
@@ -301,7 +307,7 @@ static irqreturn_t cap11xx_thread_func(int irq_num, void *data)if (ret <0 ) goto out; - ret =regmap_read (priv->regmap,CAP11XX_REG_SENSOR_INPUT , &status); + ret =regmap_read (priv->regmap, priv->model->sensor_input_reg_base, &status);if (ret <0 ) goto out;
@@ -355,7 +361,7 @@ static int cap11xx_led_set(struct led_classdev *cdev,* 0 (OFF) and 1 (ON). */ return regmap_update_bits (priv->regmap, -CAP11XX_REG_LED_OUTPUT_CONTROL , + priv->model->led_output_control_reg_base,BIT (led->reg), value ?BIT (led->reg) :0 ); }
@@ -367,6 +373,7 @@ static int cap11xx_init_leds(struct device *dev,struct cap11xx_led *led;int cnt =of_get_child_count (node);int error; +u32 duty_val;if (!num_leds || !cnt)return 0 ;
@@ -380,15 +387,18 @@ static int cap11xx_init_leds(struct device *dev, priv->leds = led; +/* Set all LEDs to off */ error =regmap_update_bits (priv->regmap, -CAP11XX_REG_LED_OUTPUT_CONTROL ,0xff ,0 ); + priv->model->led_output_control_reg_base, +GENMASK (min (num_leds,8 ) -1 ,0 ),0 );if (error)return error; + duty_val =FIELD_PREP (CAP11XX_REG_LED_DUTY_MAX_MASK , +CAP11XX_REG_LED_DUTY_MAX_VALUE ); + error =regmap_update_bits (priv->regmap,CAP11XX_REG_LED_DUTY_CYCLE_4 , -CAP11XX_REG_LED_DUTY_MAX_MASK , -CAP11XX_REG_LED_DUTY_MAX_VALUE << -CAP11XX_REG_LED_DUTY_MAX_MASK_SHIFT ); +CAP11XX_REG_LED_DUTY_MAX_MASK , duty_val);if (error)return error;
@@ -553,41 +563,64 @@ static int cap11xx_i2c_probe(struct i2c_client *i2c_client) }static const struct cap11xx_hw_model cap1106_model = { - .product_id =0x55 , .num_channels =6 , .num_leds =0 , + .product_id =0x55 , + .num_channels =6 , .num_leds =0 , .num_sensor_thresholds =6 , + .sensor_input_reg_base =CAP11XX_REG_SENSOR_INPUT , .has_gain = true, .has_irq_config = true, + .has_repeat_en = true, };static const struct cap11xx_hw_model cap1126_model = { - .product_id =0x53 , .num_channels =6 , .num_leds =2 , + .product_id =0x53 , + .num_channels =6 , .num_leds =2 , .num_sensor_thresholds =6 , + .led_output_control_reg_base =CAP11XX_REG_LED_OUTPUT_CONTROL , + .sensor_input_reg_base =CAP11XX_REG_SENSOR_INPUT , .has_gain = true, .has_irq_config = true, + .has_repeat_en = true, };static const struct cap11xx_hw_model cap1188_model = { - .product_id =0x50 , .num_channels =8 , .num_leds =8 , + .product_id =0x50 , + .num_channels =8 , .num_leds =8 , .num_sensor_thresholds =8 , + .led_output_control_reg_base =CAP11XX_REG_LED_OUTPUT_CONTROL , + .sensor_input_reg_base =CAP11XX_REG_SENSOR_INPUT , .has_gain = true, .has_irq_config = true, + .has_repeat_en = true, };static const struct cap11xx_hw_model cap1203_model = { - .product_id =0x6d , .num_channels =3 , .num_leds =0 , + .product_id =0x6d , + .num_channels =3 , .num_leds =0 , .num_sensor_thresholds =3 , + .sensor_input_reg_base =CAP11XX_REG_SENSOR_INPUT , + .has_repeat_en = true, };static const struct cap11xx_hw_model cap1206_model = { - .product_id =0x67 , .num_channels =6 , .num_leds =0 , + .product_id =0x67 , + .num_channels =6 , .num_leds =0 , .num_sensor_thresholds =6 , + .sensor_input_reg_base =CAP11XX_REG_SENSOR_INPUT , + .has_repeat_en = true, };static const struct cap11xx_hw_model cap1293_model = { - .product_id =0x6f , .num_channels =3 , .num_leds =0 , + .product_id =0x6f , + .num_channels =3 , .num_leds =0 , .num_sensor_thresholds =3 , + .sensor_input_reg_base =CAP11XX_REG_SENSOR_INPUT , .has_gain = true, + .has_repeat_en = true, .has_sensitivity_control = true, .has_signal_guard = true, };static const struct cap11xx_hw_model cap1298_model = { - .product_id =0x71 , .num_channels =8 , .num_leds =0 , + .product_id =0x71 , + .num_channels =8 , .num_leds =0 , .num_sensor_thresholds =8 , + .sensor_input_reg_base =CAP11XX_REG_SENSOR_INPUT , .has_gain = true, + .has_repeat_en = true, .has_sensitivity_control = true, .has_signal_guard = true, };
Signature · 1 line
2.54.0
PATCH v3 8/10 Input: cap11xx - guard unsupported DT properties before parsing
In reply to Jun YanCheck of_property_present() before parsing microchip,calib-sensitivity and microchip,signal-guard, so that models which do not support these properties (e.g. CAP1114) skip the parsing entirely.
This prevents a potential buffer overflow in calib_sensitivities[8] and signal_guard_inputs_mask when a model with more than 8 channels (CAP1114 has 14) would otherwise call of_property_read_u32_array() with num_channels as the element count.
--- drivers/input/keyboard/cap11xx.c | 52 +++++++++++++++++--------------- 1 file changed, 27 insertions(+), 25 deletions(-)
drivers/input/keyboard/cap11xx.c +27 -25
@@ -224,10 +224,13 @@ static int cap11xx_init_keys(struct cap11xx_priv *priv) } } -if (!of_property_read_u32_array (node,"microchip,calib-sensitivity" , - priv->calib_sensitivities, - priv->model->num_channels)) { -if (priv->model->has_sensitivity_control) { +if (of_property_present (node,"microchip,calib-sensitivity" )) { +if (!priv->model->has_sensitivity_control) { +dev_warn (dev, +"This model doesn't support 'calib-sensitivity'\n" ); + }else if (!of_property_read_u32_array (node,"microchip,calib-sensitivity" , + priv->calib_sensitivities, + priv->model->num_channels)) {for (i =0 ; i < priv->model->num_channels; i++) {if (!is_power_of_2 (priv->calib_sensitivities[i]) || priv->calib_sensitivities[i] >4 ) {
@@ -247,32 +250,31 @@ static int cap11xx_init_keys(struct cap11xx_priv *priv)if (error)return error; } - }else { -dev_warn (dev, -"This model doesn't support 'calib-sensitivity'\n" ); } } -for (i =0 ; i < priv->model->num_channels; i++) { -if (!of_property_read_u32_index (node,"microchip,signal-guard" , - i, &u32_val)) { -if (u32_val >1 ) -return -EINVAL ; -if (u32_val) - priv->signal_guard_inputs_mask |=0x01 << i; - } - } - -if (priv->signal_guard_inputs_mask) { -if (priv->model->has_signal_guard) { - error =regmap_write (priv->regmap, -CAP11XX_REG_SIGNAL_GUARD_ENABLE , - priv->signal_guard_inputs_mask); -if (error) -return error; - }else { +if (of_property_present (node,"microchip,signal-guard" )) { +if (!priv->model->has_signal_guard) {dev_warn (dev,"This model doesn't support 'signal-guard'\n" ); + }else { +for (i =0 ; i < priv->model->num_channels; i++) { +if (!of_property_read_u32_index (node,"microchip,signal-guard" , + i, &u32_val)) { +if (u32_val >1 ) +return -EINVAL ; +if (u32_val) + priv->signal_guard_inputs_mask |=0x01 << i; + } + } + +if (priv->signal_guard_inputs_mask) { + error =regmap_write (priv->regmap, +CAP11XX_REG_SIGNAL_GUARD_ENABLE , + priv->signal_guard_inputs_mask); +if (error) +return error; + } } }
Signature · 1 line
2.54.0
PATCH v3 9/10 dt-bindings: input: microchip,cap11xx: Add CAP1114 support
In reply to Jun YanCAP1114 is a 14-channel capacitive touch sensor with 11 LED outputs and hardware reset support.
Add the compatible string for CAP1114, add its datasheet URL, update the maximum of LED channel reg, and add constraint for linux,keycodes.
Previously, the LED reg property had a default maximum of 7 for CAP1188. With the addition of CAP1114, the default maximum is now 11. An if-then constraint is added to limit the LED count for CAP1188.
Update description for microchip,input-threshold: CAP1114 only provides eight threshold entries, which does not match its total channel count.
CAP1114 does not support microchip,signal-guard and microchip,calib-sensitivity.
Add CAP1114 to the unsupported enum list.
--- .../bindings/input/microchip,cap11xx.yaml | 37 ++++++++++++++++++- 1 file changed, 35 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/input/microchip,cap11xx.yaml +35 -2
@@ -12,6 +12,7 @@ description: | For more product information please see the links below: CAP1106: https://ww1.microchip.com/downloads/en/DeviceDoc/00001624B.pdf + CAP1114: https://ww1.microchip.com/downloads/en/DeviceDoc/00002444A.pdf CAP1126: https://ww1.microchip.com/downloads/en/DeviceDoc/00001623B.pdf CAP1188: https://ww1.microchip.com/downloads/en/DeviceDoc/00001620C.pdf CAP1203: https://ww1.microchip.com/downloads/en/DeviceDoc/00001572B.pdf
@@ -26,6 +27,7 @@ properties: compatible: enum: - microchip,cap1106 + - microchip,cap1114 - microchip,cap1126 - microchip,cap1188 - microchip,cap1203
@@ -62,7 +64,7 @@ properties: linux,keycodes: minItems: 3 - maxItems: 8 + maxItems: 14 description: | Specifies an array of numeric keycode values to be used for the channels. If this property is
@@ -122,6 +124,8 @@ properties: is required for a touch to be registered, making the touch sensor less sensitive. The number of entries must correspond to the number of channels. + CAP1114 is an exception where channels 8~14 reuse the eighth entry's + threshold, so counts differ. microchip,calib-sensitivity: $ref: /schemas/types.yaml#/definitions/uint32-array
@@ -149,7 +153,7 @@ patternProperties: reg: description: LED channel number minimum: 0 - maximum: 7 + maximum: 10 label: true
@@ -178,6 +182,21 @@ allOf: properties: reset-gpios: false + - if: + properties: + compatible: + contains: + enum: + - microchip,cap1114 + then: + properties: + linux,keycodes: + minItems: 14 + else: + properties: + linux,keycodes: + maxItems: 8 + - if: properties: compatible:
@@ -205,12 +224,26 @@ allOf: reg: maximum: 1 + - if: + properties: + compatible: + contains: + enum: + - microchip,cap1188 + then: + patternProperties: + "^led@": + properties: + reg: + maximum: 7 + - if: properties: compatible: contains: enum: - microchip,cap1106 + - microchip,cap1114 - microchip,cap1126 - microchip,cap1188 - microchip,cap1203
Signature · 1 line
2.54.0
Re: [PATCH v3 09/10] dt-bindings: input: microchip,cap11xx: Add CAP1114 support
pw-bot: not-applicable
PATCH v3 10/10 Input: cap11xx - add support for CAP1114
In reply to Jun YanCAP1114 is a 14-channel capacitive touch sensor with 11 LED outputs and hardware reset support.
The CAP1114 uses two control registers for LED output management and requires two button status registers for touch input state reporting.
By default, channels CS8~CS14 operate as a single grouped block. Set the corresponding register enable bit to enable these channels as independent touch inputs. Note these channels share the input threshold of the eighth entry, causing num_sensor_thresholds to differ from num_channels.
--- drivers/input/keyboard/cap11xx.c | 73 ++++++++++++++++++++++++++++++-- 1 file changed, 69 insertions(+), 4 deletions(-)
drivers/input/keyboard/cap11xx.c +69 -4
@@ -18,6 +18,12 @@#include <linux/gpio/consumer.h> #include <linux/bitfield.h> +#define CAP1114_REG_BUTTON_STATUS1 0x03 +#define CAP1114_REG_BUTTON_STATUS2 0x04 +#define CAP1114_REG_CONFIG2 0x40 +#define CAP1114_REG_CONFIG2_VOL_UP_DOWN BIT(1) +#define CAP1114_REG_LED_OUTPUT_CONTROL1 0x73 +#define CAP11XX_REG_MAIN_CONTROL 0x00#define CAP11XX_REG_MAIN_CONTROL_GAIN_SHIFT (6)#define CAP11XX_REG_MAIN_CONTROL_GAIN_MASK (0xc0)
@@ -82,6 +88,7 @@ struct cap11xx_hw_model {unsigned int num_leds;unsigned int num_sensor_thresholds;bool has_gain; +bool has_grouped_sensors;bool has_irq_config;bool has_repeat_en;bool has_sensitivity_control;
@@ -98,6 +105,8 @@ static const struct reg_default cap11xx_reg_defaults[] = { { 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_CONFIG2, 0x40 }, };
@@ -106,6 +115,12 @@ static bool cap11xx_volatile_reg(struct device *dev, unsigned int reg)switch (reg) {case CAP11XX_REG_MAIN_CONTROL :case CAP11XX_REG_SENSOR_INPUT : +/* +* CAP1114_REG_BUTTON_STATUS1 (CAP11XX_REG_SENSOR_INPUT) and +* CAP1114_REG_BUTTON_STATUS2 is volatile for the CAP1114, +* which supports more than 8 touch channels. +*/ +case CAP1114_REG_BUTTON_STATUS2 :return true; }
@@ -285,6 +300,17 @@ static int cap11xx_init_keys(struct cap11xx_priv *priv)of_property_read_u32_array (node,"linux,keycodes" , priv->keycodes, priv->model->num_channels); +/* +* CAP1114 needs dedicated configuration to split +* grouped sensors into independent inputs. +*/ +if (priv->model->has_grouped_sensors) { + error =regmap_set_bits (priv->regmap,CAP1114_REG_CONFIG2 , +CAP1114_REG_CONFIG2_VOL_UP_DOWN ); +if (error) +return error; + } +if (priv->model->has_repeat_en) {/* Disable autorepeat. The Linux input system has its own handling. */ error =regmap_write (priv->regmap,CAP11XX_REG_REPEAT_RATE ,0 );
@@ -313,6 +339,21 @@ static irqreturn_t cap11xx_thread_func(int irq_num, void *data)if (ret <0 ) goto out; +if (priv->model->num_channels >8 ) { +unsigned int status2; + + ret =regmap_read (priv->regmap, priv->model->sensor_input_reg_base +1 , &status2); +if (ret <0 ) + goto out; + +/* +* CAP1114 STATUS1 register only contains data for the first 6 channels. +* the remaining channels is stored in STATUS2. +*/ + status &=GENMASK (5 ,0 ); + status |=FIELD_PREP (GENMASK (13 ,6 ), status2); + } +for (i =0 ; i < priv->idev->keycodemax; i++)input_report_key (priv->idev, priv->keycodes[i], status & (1 << i));
@@ -362,10 +403,16 @@ static int cap11xx_led_set(struct led_classdev *cdev,* limitation. Brightness levels per LED are either * 0 (OFF) and 1 (ON). */ -return regmap_update_bits (priv->regmap, - priv->model->led_output_control_reg_base, -BIT (led->reg), - value ?BIT (led->reg) :0 ); +if (led->reg >=8 ) +return regmap_update_bits (priv->regmap, + priv->model->led_output_control_reg_base +1 , +BIT (led->reg -8 ), + value ?BIT (led->reg -8 ) :0 ); +else +return regmap_update_bits (priv->regmap, + priv->model->led_output_control_reg_base, +BIT (led->reg), + value ?BIT (led->reg) :0 ); } static int cap11xx_init_leds(struct device *dev,
@@ -396,6 +443,14 @@ static int cap11xx_init_leds(struct device *dev,if (error)return error; +if (num_leds >8 ) { + error =regmap_update_bits (priv->regmap, + priv->model->led_output_control_reg_base +1 , +GENMASK (num_leds -8 -1 ,0 ),0 ); +if (error) +return error; + } + duty_val =FIELD_PREP (CAP11XX_REG_LED_DUTY_MAX_MASK ,CAP11XX_REG_LED_DUTY_MAX_VALUE );
@@ -573,6 +628,14 @@ static const struct cap11xx_hw_model cap1106_model = { .has_repeat_en = true, }; +static const struct cap11xx_hw_model cap1114_model = { + .product_id =0x3a , + .num_channels =14 , .num_leds =11 , .num_sensor_thresholds =8 , + .led_output_control_reg_base =CAP1114_REG_LED_OUTPUT_CONTROL1 , + .sensor_input_reg_base =CAP1114_REG_BUTTON_STATUS1 , + .has_grouped_sensors = true, +}; +static const struct cap11xx_hw_model cap1126_model = { .product_id =0x53 , .num_channels =6 , .num_leds =2 , .num_sensor_thresholds =6 ,
@@ -629,6 +692,7 @@ static const struct cap11xx_hw_model cap1298_model = {static const struct of_device_id cap11xx_dt_ids[] = { { .compatible ="microchip,cap1106" , .data = &cap1106_model }, + { .compatible ="microchip,cap1114" , .data = &cap1114_model }, { .compatible ="microchip,cap1126" , .data = &cap1126_model }, { .compatible ="microchip,cap1188" , .data = &cap1188_model }, { .compatible ="microchip,cap1203" , .data = &cap1203_model },
@@ -641,6 +705,7 @@ MODULE_DEVICE_TABLE(of, cap11xx_dt_ids);static const struct i2c_device_id cap11xx_i2c_ids[] = { { .name ="cap1106" , .driver_data = (kernel_ulong_t)&cap1106_model }, + { .name ="cap1114" , .driver_data = (kernel_ulong_t)&cap1114_model }, { .name ="cap1126" , .driver_data = (kernel_ulong_t)&cap1126_model }, { .name ="cap1188" , .driver_data = (kernel_ulong_t)&cap1188_model }, { .name ="cap1203" , .driver_data = (kernel_ulong_t)&cap1203_model },
Signature · 1 line
2.54.0