Re: [PATCH v6 6/8] input: touchscreen: imx25 tcq driver
From: Markus Pargmann <hidden>
Date: 2015-02-26 14:30:51
Also in:
linux-arm-kernel, linux-iio, linux-input
Hi, On Mon, Feb 02, 2015 at 09:51:34AM -0800, Dmitry Torokhov wrote:
On Mon, Feb 02, 2015 at 05:05:39PM +0100, Markus Pargmann wrote:quoted
Hi, On Fri, Jan 30, 2015 at 10:57:21AM -0800, Dmitry Torokhov wrote:quoted
On Thu, Jan 29, 2015 at 07:56:40PM +0530, Varka Bhadram wrote:quoted
Hi, On Thursday 29 January 2015 07:39 PM, Markus Pargmann wrote:quoted
This is a driver for the imx25 ADC/TSC module. It controls the touchscreen conversion queue and creates a touchscreen input device. The driver currently only supports 4 wire touchscreens. The driver uses a simple conversion queue of precharge, touch detection, X measurement, Y measurement, precharge and another touch detection. This driver uses the regmap from the parent to setup some touch specific settings in the core driver and setup a idle configuration with touch detection. Signed-off-by: Markus Pargmann <redacted> Signed-off-by: Denis Carikli <redacted> Acked-by: Dmitry Torokhov <redacted> Signed-off-by: Markus Pargmann <redacted> --- drivers/input/touchscreen/Kconfig | 6 + drivers/input/touchscreen/Makefile | 1 + drivers/input/touchscreen/fsl-imx25-tcq.c | 587 ++++++++++++++++++++++++++++++ 3 files changed, 594 insertions(+) create mode 100644 drivers/input/touchscreen/fsl-imx25-tcq.c(...)quoted
+ ret = request_threaded_irq(priv->irq, mx25_tcq_irq, mx25_tcq_irq_thread, + IRQF_ONESHOT, pdev->name, priv);We can use devres API for request_thread_irq()...quoted
+ if (ret) { + dev_err(dev, "Failed requesting IRQ\n"); + goto err_clk_unprepare; + } + + ret = mx25_tcq_init(priv); + if (ret) { + dev_err(dev, "Failed to init tcq\n"); + goto error_free_irq; + } + + platform_set_drvdata(pdev, priv); + + return 0; + +error_free_irq: + free_irq(priv->irq, priv);This is not required if we use devres APIYes it does - you do not really want to stop clocks in the middle of servicing interrupt.Thanks, I missed the clocks. I will not use devm here then.Actually, you still can if you move clock enabling/disabling and mx25_tcq_init() into input_dev->open() and ->close() callbacks. Close will be called during input device un-registration which happens (given your current sequence) after freeing irq by devm.
Thank you. I now moved that code into open() and close(), replaced the irq_request() with devm_irq_request. mx25_tcq_remove() is gone now.
By the way, I used my old @vmware address by accident. Can you please replace the original acked by with: Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Replaced it. Thanks, Markus -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Attachments
- signature.asc [application/pgp-signature] 819 bytes