linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Barry Song <song.bao.hua@hisilicon.com>
To: <dmitry.torokhov@gmail.com>, <tglx@linutronix.de>,
	<maz@kernel.org>, <gregkh@linuxfoundation.org>,
	<linux-input@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <linuxarm@openeuler.org>, Barry Song <song.bao.hua@hisilicon.com>
Subject: [PATCH v3 07/12] Input: zinitix - request_irq by IRQF_NO_AUTOEN and remove irq_set_status_flags
Date: Fri, 8 Jan 2021 11:39:21 +1300	[thread overview]
Message-ID: <20210107223926.35284-8-song.bao.hua@hisilicon.com> (raw)
In-Reply-To: <20210107223926.35284-1-song.bao.hua@hisilicon.com>

Right now, irq core supports requesting irq with IRQF_NO_AUTOEN, this means
the driver doesn't need to call irq_set_status_flags any more.

Signed-off-by: Barry Song <song.bao.hua@hisilicon.com>
---
 drivers/input/touchscreen/zinitix.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/input/touchscreen/zinitix.c b/drivers/input/touchscreen/zinitix.c
index a3e3adbabc67..0d3c93e4bbb7 100644
--- a/drivers/input/touchscreen/zinitix.c
+++ b/drivers/input/touchscreen/zinitix.c
@@ -513,10 +513,10 @@ static int zinitix_ts_probe(struct i2c_client *client)
 		return -EINVAL;
 	}
 
-	irq_set_status_flags(client->irq, IRQ_NOAUTOEN);
 	error = devm_request_threaded_irq(&client->dev, client->irq,
 					  NULL, zinitix_ts_irq_handler,
-					  IRQF_ONESHOT, client->name, bt541);
+					  IRQF_ONESHOT | IRQF_NO_AUTOEN,
+					  client->name, bt541);
 	if (error) {
 		dev_err(&client->dev, "Failed to request IRQ: %d\n", error);
 		return error;
-- 
2.25.1


  parent reply	other threads:[~2021-01-07 22:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 22:39 [PATCH v3 00/12] add IRQF_NO_AUTOEN for request_irq Barry Song
2021-01-07 22:39 ` [PATCH v3 01/12] genirq: " Barry Song
2021-01-28 19:54   ` Thomas Gleixner
2021-02-01  4:08     ` Song Bao Hua (Barry Song)
2021-01-07 22:39 ` [PATCH v3 02/12] Input: ar1021 - request_irq by IRQF_NO_AUTOEN and remove disable_irq Barry Song
2021-01-07 22:39 ` [PATCH v3 03/12] Input: atmel_mxt_ts " Barry Song
2021-01-07 22:39 ` [PATCH v3 04/12] Input: melfas_mip4 " Barry Song
2021-01-07 22:39 ` [PATCH v3 05/12] Input: bu21029_ts - request_irq by IRQF_NO_AUTOEN and remove irq_set_status_flags Barry Song
2021-01-07 22:39 ` [PATCH v3 06/12] Input: stmfts " Barry Song
2021-01-07 22:39 ` Barry Song [this message]
2021-01-07 22:39 ` [PATCH v3 08/12] Input: mms114 - request_irq by IRQF_NO_AUTOEN and remove disable_irq Barry Song
2021-01-07 22:39 ` [PATCH v3 09/12] Input: wm831x-ts " Barry Song
2021-01-07 22:39 ` [PATCH v3 10/12] Input: cyttsp " Barry Song
2021-01-07 22:39 ` [PATCH v3 11/12] Input: tegra-kbc " Barry Song
2021-01-07 22:39 ` [PATCH v3 12/12] Input: tca6416-keypad " Barry Song
2021-01-21 21:38 ` [PATCH v3 00/12] add IRQF_NO_AUTOEN for request_irq Song Bao Hua (Barry Song)
2021-01-27 13:49   ` gregkh
2021-01-27 19:45     ` dmitry.torokhov
2021-01-28 11:08       ` [Linuxarm] " Jonathan Cameron

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=20210107223926.35284-8-song.bao.hua@hisilicon.com \
    --to=song.bao.hua@hisilicon.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).