public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Valek - 2N <jiriv@axis.com>
Cc: krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, u.kleine-koenig@pengutronix.de
Subject: Re: [PATCH v4 2/2] Input: cap11xx - add advanced sensitivity settings
Date: Wed, 28 Jun 2023 12:06:14 -0700	[thread overview]
Message-ID: <ZJyEpuat1A8Z+Ft4@google.com> (raw)
In-Reply-To: <20230627065316.1065911-3-jiriv@axis.com>

Hi Jiri,

On Tue, Jun 27, 2023 at 08:53:16AM +0200, Jiri Valek - 2N wrote:
> @@ -439,7 +589,7 @@ static int cap11xx_i2c_probe(struct i2c_client *i2c_client)
>  	priv->idev->id.bustype = BUS_I2C;
>  	priv->idev->evbit[0] = BIT_MASK(EV_KEY);
>  
> -	if (of_property_read_bool(node, "autorepeat"))
> +	if (of_property_read_bool(dev->of_node, "autorepeat"))

It would be good to have this driver switched from of_property_*() to
device_property_() API.

>  		__set_bit(EV_REP, priv->idev->evbit);
>  
>  	for (i = 0; i < cap->num_channels; i++)
> @@ -474,14 +624,8 @@ static int cap11xx_i2c_probe(struct i2c_client *i2c_client)
>  	if (error)
>  		return error;
>  
> -	irq = irq_of_parse_and_map(node, 0);
> -	if (!irq) {
> -		dev_err(dev, "Unable to parse or map IRQ\n");
> -		return -ENXIO;
> -	}
> -
> -	error = devm_request_threaded_irq(dev, irq, NULL, cap11xx_thread_func,
> -					  IRQF_ONESHOT, dev_name(dev), priv);
> +	error = devm_request_threaded_irq(dev, i2c_client->irq, NULL,
> +					cap11xx_thread_func, IRQF_ONESHOT, dev_name(dev), priv);

I would prefer this change be a separate patch.

Thanks.

-- 
Dmitry

  reply	other threads:[~2023-06-28 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  6:53 [PATCH v4 0/2] Input: cap11xx add advanced sensitivity settings Jiri Valek - 2N
2023-06-27  6:53 ` [PATCH v4 1/2] dt-bindings: input: microchip,cap11xx: " Jiri Valek - 2N
2023-06-29 15:16   ` Rob Herring
2023-07-11 13:22     ` Jiri Valek - 2N
2023-06-27  6:53 ` [PATCH v4 2/2] Input: cap11xx - " Jiri Valek - 2N
2023-06-28 19:06   ` Dmitry Torokhov [this message]
2023-07-11 13:05     ` Jiri Valek - 2N

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=ZJyEpuat1A8Z+Ft4@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jiriv@axis.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox