From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sangwon Jee <jeesw@melfas.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: Removal of MSC-5000/5080 touchscreen/touchkey drivers?
Date: Fri, 12 Jul 2024 11:52:08 +0200 [thread overview]
Message-ID: <cf02eb9b-2304-4db5-96f9-cfe89037faad@kernel.org> (raw)
In-Reply-To: <ZpC7G0AVMB98og6H@google.com>
On 12/07/2024 07:11, Dmitry Torokhov wrote:
> Hi,
>
> Sorry for a somewhat wide and random distribution, but I was wondering
> if anyone knows if drivers/input/touchscreen/mcs5000_ts.c and
> drivers/input/keyboard/mcs_touchkey.c are still relevant these days?
>
> Looking at Melfas web-site it looks like these were the 1st generation
> of their chips, manufactured 2000-2007. The drivers were contributed by
> Samsung long time ago, they rely on custom platform data (no DT support)
> and as far as I can see we never had a user of them in mainline.
>
> Should I simply remove them? Does anyone know?
Digging in history, commit claims this was for S3C6410 NCP board (with
Samsung S3C6410 SoC), which had a board-file:
arch/arm/mach-s3c64xx/mach-ncp.c
But the touchscreen was never added to the board file, thus mainline
kernel never had it fully working.
The NCP board file was finally removed in v6.3 in commit:
743c8fbb90ca4c02bdf4087fa9f1885ddd85041b
I say drop the driver.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-07-12 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 5:11 Removal of MSC-5000/5080 touchscreen/touchkey drivers? Dmitry Torokhov
2024-07-12 9:52 ` Krzysztof Kozlowski [this message]
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=cf02eb9b-2304-4db5-96f9-cfe89037faad@kernel.org \
--to=krzk@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jeesw@melfas.com \
--cc=jy0922.shim@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.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.