From: Sergey Larin <cerg2010cerg2010@mail.ru>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-input@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: stmpe-keypad - add STMPE1801 support
Date: Wed, 23 Jun 2021 03:05:19 +0300 [thread overview]
Message-ID: <YNJ6v7DfXUFMO8YA@minibook.localdomain> (raw)
In-Reply-To: <YNAj30vl2yGxRX4e@google.com>
Hello Dmitry,
On Sun, Jun 20, 2021 at 10:30:07PM -0700, Dmitry Torokhov wrote:
> Do we really need to do this swap vs. simply arranging the keymap
> differently for 1801?
Yes I thought about it, but that will break device tree writer's
assumptions of the device so I think it's better to keep the keymap
correct and not make driver's behavior confusing.
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Larin <cerg2010cerg2010@mail.ru>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-input@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: stmpe-keypad - add STMPE1801 support
Date: Wed, 23 Jun 2021 03:05:19 +0300 [thread overview]
Message-ID: <YNJ6v7DfXUFMO8YA@minibook.localdomain> (raw)
In-Reply-To: <YNAj30vl2yGxRX4e@google.com>
Hello Dmitry,
On Sun, Jun 20, 2021 at 10:30:07PM -0700, Dmitry Torokhov wrote:
> Do we really need to do this swap vs. simply arranging the keymap
> differently for 1801?
Yes I thought about it, but that will break device tree writer's
assumptions of the device so I think it's better to keep the keymap
correct and not make driver's behavior confusing.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-23 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 14:51 [PATCH] Input: stmpe-keypad - add STMPE1801 support Sergey Larin
2021-06-18 14:51 ` Sergey Larin
2021-06-21 5:30 ` Dmitry Torokhov
2021-06-21 5:30 ` Dmitry Torokhov
2021-06-23 0:05 ` Sergey Larin [this message]
2021-06-23 0:05 ` Sergey Larin
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=YNJ6v7DfXUFMO8YA@minibook.localdomain \
--to=cerg2010cerg2010@mail.ru \
--cc=alexandre.torgue@foss.st.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@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.