input synaptics-rmi4: Bug fixes to ATTN GPIO handling.
Subsystems (2)
PATCH v2 1/1 input synaptics-rmi4: Bug fixes to ATTN GPIO handling.
This patch fixes some bugs in handling of the RMI4 attention line GPIO.
1) in enable_sensor(), eliminate the complicated check on ATTN and just call process_interrupt_requests(). This will have minimal overhead if ATTN is not asserted, and clears the state of the RMI4 device in any case.
2) Correctly free the GPIO in rmi_driver_remove().
3) in rmi_driver_probe()
- declare the name of the attention gpio (GPIO_LABEL)
- use gpio_request_one() to get the gpio and export it.
- simplify conditional gpio acquisition logic and combine with interrupt setup
4) use gpio_is_valid() instead of comparing to 0.
---
drivers/input/rmi4/rmi_driver.c | 43 ++++++++++++++++++++++------------------- 1 file changed, 23 insertions(+), 20 deletions(-)
drivers/input/rmi4/rmi_driver.c +23 -20
@@ -140,7 +140,6 @@ static int enable_sensor(struct rmi_device *rmi_dev)struct rmi_driver_data *data =dev_get_drvdata (&rmi_dev->dev);struct rmi_phys_device *rmi_phys;int retval =0 ; -struct rmi_device_platform_data *pdata =to_rmi_platform_data (rmi_dev);if (data->enabled)return 0 ;
@@ -169,11 +168,7 @@ static int enable_sensor(struct rmi_device *rmi_dev) data->enabled = true; -if (!pdata->level_triggered && -gpio_get_value (pdata->attn_gpio) == pdata->attn_polarity) - retval =process_interrupt_requests (rmi_dev); - -return retval; +return process_interrupt_requests (rmi_dev); }static void rmi_free_function_list (struct rmi_device *rmi_dev)
@@ -800,13 +795,20 @@ static SIMPLE_DEV_PM_OPS(rmi_driver_pm, rmi_driver_suspend, rmi_driver_resume);static int rmi_driver_remove (struct device *dev) {struct rmi_device *rmi_dev =to_rmi_device (dev); +const struct rmi_device_platform_data *pdata = +to_rmi_platform_data (rmi_dev);disable_sensor (rmi_dev);rmi_free_function_list (rmi_dev); +if (gpio_is_valid (pdata->attn_gpio)) +gpio_free (pdata->attn_gpio); +return 0 ; } +static const char GPIO_LABEL [] ="attn" ; +static int rmi_driver_probe (struct device *dev) {struct rmi_driver *rmi_driver;
@@ -937,7 +939,7 @@ static int rmi_driver_probe(struct device *dev)mutex_init (&data->suspend_mutex); } -if (pdata->attn_gpio) { +if (gpio_is_valid (pdata->attn_gpio)) { data->irq =gpio_to_irq (pdata->attn_gpio);if (pdata->level_triggered) { data->irq_flags = IRQF_ONESHOT |
@@ -948,24 +950,17 @@ static int rmi_driver_probe(struct device *dev) (pdata->attn_polarity ==RMI_ATTN_ACTIVE_HIGH ) ?IRQF_TRIGGER_RISING :IRQF_TRIGGER_FALLING ; } - }else - data->poll_interval =ktime_set (0 , - (pdata->poll_interval_ms ? pdata->poll_interval_ms : -DEFAULT_POLL_INTERVAL_MS ) *1000 *1000 ); - -if (data->f01_container->dev.driver) { -/* Driver already bound, so enable ATTN now. */ -enable_sensor (rmi_dev); - } -if (IS_ENABLED (CONFIG_RMI4_DEV ) && pdata->attn_gpio) { - retval =gpio_export (pdata->attn_gpio, false); + retval =gpio_request_one (pdata->attn_gpio, +GPIOF_EXPORT |GPIOF_DIR_IN , +GPIO_LABEL );if (retval) { -dev_warn (dev,"WARNING: Failed to export ATTN gpio!\n" ); +dev_warn (dev,"WARNING: Failed to request ATTN gpio %d, code=%d.\n" , + pdata->attn_gpio, retval); retval =0 ; }else { retval =gpio_export_link (dev, -"attn" , pdata->attn_gpio); +GPIO_LABEL , pdata->attn_gpio);if (retval) {dev_warn (dev,"WARNING: Failed to symlink ATTN gpio!\n" );
@@ -975,6 +970,14 @@ static int rmi_driver_probe(struct device *dev) pdata->attn_gpio); } } + }else + data->poll_interval =ktime_set (0 , + (pdata->poll_interval_ms ? pdata->poll_interval_ms : +DEFAULT_POLL_INTERVAL_MS ) *1000 *1000 ); + +if (data->f01_container->dev.driver) { +/* Driver already bound, so enable ATTN now. */ +enable_sensor (rmi_dev); }return 0 ;
Dmitry Torokhov
maintainerHi Chris,
Quoted 52 lines · Christopher Heiny
This patch fixes some bugs in handling of the RMI4 attention line GPIO.
1) in
enable_sensor(), eliminate the complicated check on ATTN and just callprocess_interrupt_requests(). This will have minimal overhead if ATTN is not asserted, and clears the state of the RMI4 device in any case.2) Correctly free the GPIO in
rmi_driver_remove().3) in
rmi_driver_probe()
- declare the name of the attention gpio (GPIO_LABEL)
- usegpio_request_one()to get the gpio and export it.
- simplify conditional gpio acquisition logic and combine with interrupt setup4) use
gpio_is_valid()instead of comparing to 0.Signed-off-by Christopher Heiny <[email protected]>Cc Dmitry Torokhov <[email protected]>Cc Benjamin Tissoires <[email protected]>---
drivers/input/rmi4/rmi_driver.c | 43 ++++++++++++++++++++++------------------- 1 file changed, 23 insertions(+), 20 deletions(-)drivers/input/rmi4/rmi_driver.c +1
-6@@ -140,7 +140,6 @@ static int enable_sensor(struct rmi_device *rmi_dev)struct rmi_driver_data *data =dev_get_drvdata (&rmi_dev->dev);struct rmi_phys_device *rmi_phys;int retval =0 ; -struct rmi_device_platform_data *pdata =to_rmi_platform_data (rmi_dev);if (data->enabled)return 0 ;@@ -169,11 +168,7 @@ static int enable_sensor(struct rmi_device *rmi_dev) data->enabled = true; -if (!pdata->level_triggered && -gpio_get_value (pdata->attn_gpio) == pdata->attn_polarity) - retval =process_interrupt_requests (rmi_dev); - -return retval; +return process_interrupt_requests (rmi_dev); }static void rmi_free_function_list (struct rmi_device *rmi_dev)@@ -800,13 +795,20 @@ static SIMPLE_DEV_PM_OPS(rmi_driver_pm, rmi_driver_suspend, rmi_driver_resume);static int rmi_driver_remove (struct device *dev)
drivers/input/rmi4/rmi_driver.c static SIMPLE_DEV_PM_OPS(rmi_driver_pm, rmi_driver_suspend, rmi_driver_resume); · line 805
Quoted 10 lines
drivers/input/rmi4/rmi_driver.c +4
-0{struct rmi_device *rmi_dev =to_rmi_device (dev); +const struct rmi_device_platform_data *pdata = +to_rmi_platform_data (rmi_dev);disable_sensor (rmi_dev);rmi_free_function_list (rmi_dev); +if (gpio_is_valid (pdata->attn_gpio)) +gpio_free (pdata->attn_gpio);
It looks like you let driver registration to continue even if GPIO request fails. You probably need to introduce a flag indicating whether you successfully requested gpio or not. Or you can treat failure to acquire gpio as fatal.
Quoted 23 lines
drivers/input/rmi4/rmi_driver.c +4
-2+return 0 ; } +static const char GPIO_LABEL [] ="attn" ; +static int rmi_driver_probe (struct device *dev) {struct rmi_driver *rmi_driver;@@ -937,7 +939,7 @@ static int rmi_driver_probe(struct device *dev)mutex_init (&data->suspend_mutex); } -if (pdata->attn_gpio) { +if (gpio_is_valid (pdata->attn_gpio)) { data->irq =gpio_to_irq (pdata->attn_gpio);if (pdata->level_triggered) { data->irq_flags = IRQF_ONESHOT |@@ -948,24 +950,17 @@ static int rmi_driver_probe(struct device *dev) (pdata->attn_polarity ==RMI_ATTN_ACTIVE_HIGH ) ?IRQF_TRIGGER_RISING :IRQF_TRIGGER_FALLING ; } - }else
drivers/input/rmi4/rmi_driver.c static int rmi_driver_probe(struct device *dev) · line 961
Quoted 10 lines
drivers/input/rmi4/rmi_driver.c +0
-9- data->poll_interval =ktime_set (0 , - (pdata->poll_interval_ms ? pdata->poll_interval_ms : -DEFAULT_POLL_INTERVAL_MS ) *1000 *1000 ); - -if (data->f01_container->dev.driver) { -/* Driver already bound, so enable ATTN now. */ -enable_sensor (rmi_dev); - } -if (IS_ENABLED (CONFIG_RMI4_DEV ) && pdata->attn_gpio) {
Do you really need to export gpio if you do not have RMI4_DEV option?
Quoted 21 lines
drivers/input/rmi4/rmi_driver.c +7
-3- retval =gpio_export (pdata->attn_gpio, false); + retval =gpio_request_one (pdata->attn_gpio, +GPIOF_EXPORT |GPIOF_DIR_IN , +GPIO_LABEL );if (retval) { -dev_warn (dev,"WARNING: Failed to export ATTN gpio!\n" ); +dev_warn (dev,"WARNING: Failed to request ATTN gpio %d, code=%d.\n" , + pdata->attn_gpio, retval); retval =0 ; }else { retval =gpio_export_link (dev, -"attn" , pdata->attn_gpio); +GPIO_LABEL , pdata->attn_gpio);if (retval) {dev_warn (dev,"WARNING: Failed to symlink ATTN gpio!\n" );@@ -975,6 +970,14 @@ static int rmi_driver_probe(struct device *dev) pdata->attn_gpio); } } + }else
drivers/input/rmi4/rmi_driver.c static int rmi_driver_probe(struct device *dev) · line 983
Quoted 10 lines
drivers/input/rmi4/rmi_driver.c +7
-0+ data->poll_interval =ktime_set (0 , + (pdata->poll_interval_ms ? pdata->poll_interval_ms : +DEFAULT_POLL_INTERVAL_MS ) *1000 *1000 ); + +if (data->f01_container->dev.driver) { +/* Driver already bound, so enable ATTN now. */ +enable_sensor (rmi_dev); }return 0 ;
Thanks.
Signature · 1 line
Dmitry
Quoted 63 lines · Dmitry Torokhov
Hi Chris,
Quoted 60 lines · Christopher Heiny
This patch fixes some bugs in handling of the RMI4 attention line GPIO.
1) in
enable_sensor(), eliminate the complicated check on ATTN and just callprocess_interrupt_requests(). This will have minimal overhead if ATTN is not asserted, and clears the state of the RMI4 device in any case.2) Correctly free the GPIO in
rmi_driver_remove().3) in
rmi_driver_probe()
- declare the name of the attention gpio (GPIO_LABEL)
- usegpio_request_one()to get the gpio and export it.
- simplify conditional gpio acquisition logic and combine with interrupt setup4) use
gpio_is_valid()instead of comparing to 0.Signed-off-by Christopher Heiny <[email protected]>Cc Dmitry Torokhov <[email protected]>Cc Benjamin Tissoires <[email protected]>---
drivers/input/rmi4/rmi_driver.c | 43 ++++++++++++++++++++++------------------- 1 file changed, 23 insertions(+), 20 deletions(-)drivers/input/rmi4/rmi_driver.c +3
-6@@ -140,7 +140,6 @@ static int enable_sensor(struct rmi_device *rmi_dev)struct rmi_driver_data *data =dev_get_drvdata (&rmi_dev->dev);struct rmi_phys_device *rmi_phys;int retval =0 ; -struct rmi_device_platform_data *pdata =to_rmi_platform_data (rmi_dev);if (data->enabled)return 0 ;@@ -169,11 +168,7 @@ static int enable_sensor(struct rmi_device *rmi_dev) data->enabled = true; -if (!pdata->level_triggered && -gpio_get_value (pdata->attn_gpio) == pdata->attn_polarity) - retval =process_interrupt_requests (rmi_dev); - -return retval; +return process_interrupt_requests (rmi_dev); }static void rmi_free_function_list (struct rmi_device *rmi_dev)@@ -800,13 +795,20 @@ static SIMPLE_DEV_PM_OPS(rmi_driver_pm, rmi_driver_suspend, rmi_driver_resume);static int rmi_driver_remove (struct device *dev) {struct rmi_device *rmi_dev =to_rmi_device (dev); +const struct rmi_device_platform_data *pdata = +to_rmi_platform_data (rmi_dev);disable_sensor (rmi_dev);rmi_free_function_list (rmi_dev);
Quoted 7 lines
drivers/input/rmi4/rmi_driver.c static SIMPLE_DEV_PM_OPS(rmi_driver_pm, rmi_driver_suspend, rmi_driver_resume); · line 805
Quoted 2 lines
drivers/input/rmi4/rmi_driver.c +2
-0+if (gpio_is_valid (pdata->attn_gpio)) +gpio_free (pdata->attn_gpio);It looks like you let driver registration to continue even if GPIO request fails. You probably need to introduce a flag indicating whether you successfully requested gpio or not. Or you can treat failure to acquire gpio as fatal.
In testing, the driver continues to work even if the GPIO is not acquired, but some diagnostic features may not be available, so we treat the failure to acquire as a warning. I'll add a flag to indicate whether it was acquired or not.
Quoted 33 lines
Quoted 33 lines
drivers/input/rmi4/rmi_driver.c +4
-10+return 0 ; } +static const char GPIO_LABEL [] ="attn" ; +static int rmi_driver_probe (struct device *dev) {struct rmi_driver *rmi_driver;@@ -937,7 +939,7 @@ static int rmi_driver_probe(struct device *dev)mutex_init (&data->suspend_mutex); } -if (pdata->attn_gpio) { +if (gpio_is_valid (pdata->attn_gpio)) { data->irq =gpio_to_irq (pdata->attn_gpio);if (pdata->level_triggered) { data->irq_flags = IRQF_ONESHOT |@@ -948,24 +950,17 @@ static int rmi_driver_probe(struct device *dev) (pdata->attn_polarity ==RMI_ATTN_ACTIVE_HIGH ) ?IRQF_TRIGGER_RISING :IRQF_TRIGGER_FALLING ; } - }else - data->poll_interval =ktime_set (0 , - (pdata->poll_interval_ms ? pdata->poll_interval_ms : -DEFAULT_POLL_INTERVAL_MS ) *1000 *1000 ); - -if (data->f01_container->dev.driver) { -/* Driver already bound, so enable ATTN now. */ -enable_sensor (rmi_dev); - }
Quoted 3 lines
drivers/input/rmi4/rmi_driver.c static int rmi_driver_probe(struct device *dev) · line 961
Quoted 1 line
drivers/input/rmi4/rmi_driver.c +0
-1-if (IS_ENABLED (CONFIG_RMI4_DEV ) && pdata->attn_gpio) {Do you really need to export gpio if you do not have
RMI4_DEVoption?
Not really, but it doesn't hurt to do so. I was trying to simplify the driver logic, but I guess that went too far. I'll re-add the check.
[snip]