From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Dmitry Mastykin <mastichi@gmail.com>
Cc: job@noorman.info, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, felix@kaechele.ca
Subject: Re: [PATCH] Input: himax_hx83112b - fix event stack size to clear irq correctly
Date: Wed, 22 Jan 2025 10:37:17 -0800 [thread overview]
Message-ID: <Z5E63X6qnpIEvWji@google.com> (raw)
In-Reply-To: <20250122121409.1374602-1-mastichi@gmail.com>
Hi Dmitry,
On Wed, Jan 22, 2025 at 03:14:09PM +0300, Dmitry Mastykin wrote:
> The datasheet suggests that the size of the event stack is 32 x 32-bit.
> Reading less bytes did not clear the interrupt output. Extra interrupts
> were called with zero himax_event_get_num_points() result.
> Only every second call to himax_handle_input() cleared the interrupt
> output.
>
> Tested on: HX83102J
>
> Signed-off-by: Dmitry Mastykin <mastichi@gmail.com>
> ---
> drivers/input/touchscreen/himax_hx83112b.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/input/touchscreen/himax_hx83112b.c b/drivers/input/touchscreen/himax_hx83112b.c
> index 31f18860dbd3..fe7bdf8cec50 100644
> --- a/drivers/input/touchscreen/himax_hx83112b.c
> +++ b/drivers/input/touchscreen/himax_hx83112b.c
> @@ -24,6 +24,7 @@
> #include <linux/regmap.h>
>
> #define HIMAX_MAX_POINTS 10
> +#define HIMAX_EVENT_STACK_SIZE 128
>
> #define HIMAX_AHB_ADDR_BYTE_0 0x00
> #define HIMAX_AHB_ADDR_RDATA_BYTE_0 0x08
> @@ -292,9 +293,9 @@ static int hx83100a_read_events(struct himax_ts_data *ts,
> static int himax_handle_input(struct himax_ts_data *ts)
> {
> int error;
> - struct himax_event event;
> + u8 event[HIMAX_EVENT_STACK_SIZE];
If you need this it should go into struct himax_event (wither padding or
making it a union).
Also if this change is needed to make HX83102J operate properly it
should be rolled into the previous patch adding compatibles to the
driver.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2025-01-22 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 12:14 [PATCH] Input: himax_hx83112b - fix event stack size to clear irq correctly Dmitry Mastykin
2025-01-22 18:37 ` Dmitry Torokhov [this message]
2025-01-25 4:29 ` Dmitry Mastykin
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=Z5E63X6qnpIEvWji@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=felix@kaechele.ca \
--cc=job@noorman.info \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mastichi@gmail.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.