From: Biju Das <biju.das.jz@bp.renesas.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Support Opensource <support.opensource@diasemi.com>,
linux-input@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH v3 0/3] Add polling support for DA9063 onkey driver
Date: Thu, 25 Jan 2024 13:37:30 +0000 [thread overview]
Message-ID: <20240125133733.95081-1-biju.das.jz@bp.renesas.com> (raw)
On some platforms (eg: RZ/{G2UL,Five} SMARC EVK), there is no
onkey IRQ populated by default.
This patch series aims to add polling support.
v2->v3:
* Created patch#1 and patch#2 for removing work.
* Updated commit description as cleanup is done in patch#1
* Dropped scheduling work instead start using polling as in the polling
* case scheduling any additional works will create confused state for
* driver if we repeatedly open and close input device.
v1->v2:
* Updated commit description
* Fixed the logical mistake for optional IRQ handling.
Biju Das (3):
Input: da9063_onkey - Add da9063_onkey_report_key()
Input: da9063_onkey - Drop scheduling work
Input: da9063_onkey - Add polling support
drivers/input/misc/da9063_onkey.c | 130 +++++++++++++++++++-----------
1 file changed, 82 insertions(+), 48 deletions(-)
--
2.25.1
next reply other threads:[~2024-01-25 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 13:37 Biju Das [this message]
2024-01-25 13:37 ` [PATCH v3 1/3] Input: da9063_onkey - Add da9063_onkey_report_key() Biju Das
2024-01-25 13:37 ` [PATCH v3 2/3] Input: da9063_onkey - Drop scheduling work Biju Das
2024-01-25 13:37 ` [PATCH v3 3/3] Input: da9063_onkey - Add polling support Biju Das
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=20240125133733.95081-1-biju.das.jz@bp.renesas.com \
--to=biju.das.jz@bp.renesas.com \
--cc=biju.das.au@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-input@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=support.opensource@diasemi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.