[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1b180b09-f2e6-e3dc-ba93-45b03dfcdcbb@linaro.org>
Date: Sat, 7 May 2022 17:46:45 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Gireesh.Hiremath@...bosch.com, linux-omap@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-input@...r.kernel.org, bcousson@...libre.com,
tony@...mide.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, dmitry.torokhov@...il.com,
mkorpershoek@...libre.com, davidgow@...gle.com,
m.felsch@...gutronix.de, swboyd@...omium.org,
fengping.yu@...iatek.com, y.oudjana@...tonmail.com,
rdunlap@...radead.org, colin.king@...el.com
Cc: sjoerd.simons@...labora.co.uk, VinayKumar.Shettar@...bosch.com,
Govindaraji.Sivanantham@...bosch.com, anaclaudia.dias@...bosch.com
Subject: Re: [PATCH v2 2/4] Input: mt-matrix-keypad: Add Bosch mt matrix
keypad driver
On 06/05/2022 09:27, Gireesh.Hiremath@...bosch.com wrote:
>>
>>> both matric_keypad.c and mt_matrix_kepad.c logically operate differently,
>>> my openion is not to merge both.
>>
>> IMHO from the user/system-integrator pov it is looking the same and so
>> one driver should be fine. To distinguish between both modes we could
>> add dt-property or add a new dt-compatible like "gpio-matrix-keypad-v2".
>>
>
> as mentioned above our keypad is not complete matrix keypad and it will
> not be compatible with matrix_keypad diver. that is the reason we derived
> mt matrix keypad driver.
>
> to avoid confusion, we will rename the driver as bosch_mt_keypad.c
> if you suggest.
Sending a new version while discussions are ongoing is not how we reach
consensus.
Make the driver as part of matrix-keypad driver or bring real arguments
why it cannot be merged.
Best regards,
Krzysztof
Powered by blists - more mailing lists