From: Sean Young <sean@mess.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] Remove remaining AMD Elan drivers
Date: Wed, 6 May 2026 15:42:45 +0100 [thread overview]
Message-ID: <cover.1778071745.git.sean@mess.org> (raw)
Now that AMD Elan support has been removed[1], remove the AMD Elan specific
drivers too. I had a Technology Systems 5500 back in the early 2000's and
it was pretty slow back then - no need to support such ancient slow
device. I wrote and patched some of these drivers so nice to see them
removed at the end of their life cycle.
1. commit 8b793a92d862 ("x86/cpu: Remove M486/M486SX/ELAN support")
Sean Young (8):
x86/platform: Remove Technology Systems 5500 board
mtd: ts5500_flash: Remove mapping since board is no longer supported
mtd: netsc520: Remove mapping since board is no longer supported
mtd: sc520cdp: Remove mapping since board is no longer supported
gpio: ts5500: Remove gpio driver as board no longer supported
watchdog: sc520: Drop AMD Elan SC520 support
cpufreq: sc520_freq: Drop support for AMD Elan SC520
cpufreq: elanfreq: Drop support for AMD Elan SC4*
.../ABI/testing/sysfs-platform-ts5500 | 54 ---
.../watchdog/watchdog-parameters.rst | 9 -
MAINTAINERS | 5 -
arch/x86/Kconfig | 9 -
arch/x86/platform/Makefile | 1 -
arch/x86/platform/ts5500/Makefile | 2 -
arch/x86/platform/ts5500/ts5500.c | 341 -------------
drivers/cpufreq/Kconfig.x86 | 26 -
drivers/cpufreq/Makefile | 2 -
drivers/cpufreq/elanfreq.c | 226 ---------
drivers/cpufreq/sc520_freq.c | 136 ------
drivers/gpio/Kconfig | 9 -
drivers/gpio/Makefile | 1 -
drivers/gpio/gpio-ts5500.c | 446 ------------------
drivers/mtd/maps/Kconfig | 34 --
drivers/mtd/maps/Makefile | 3 -
drivers/mtd/maps/netsc520.c | 127 -----
drivers/mtd/maps/sc520cdp.c | 294 ------------
drivers/mtd/maps/ts5500_flash.c | 108 -----
drivers/watchdog/Kconfig | 13 -
drivers/watchdog/Makefile | 1 -
drivers/watchdog/sc520_wdt.c | 430 -----------------
22 files changed, 2277 deletions(-)
delete mode 100644 Documentation/ABI/testing/sysfs-platform-ts5500
delete mode 100644 arch/x86/platform/ts5500/Makefile
delete mode 100644 arch/x86/platform/ts5500/ts5500.c
delete mode 100644 drivers/cpufreq/elanfreq.c
delete mode 100644 drivers/cpufreq/sc520_freq.c
delete mode 100644 drivers/gpio/gpio-ts5500.c
delete mode 100644 drivers/mtd/maps/netsc520.c
delete mode 100644 drivers/mtd/maps/sc520cdp.c
delete mode 100644 drivers/mtd/maps/ts5500_flash.c
delete mode 100644 drivers/watchdog/sc520_wdt.c
--
2.54.0
next reply other threads:[~2026-05-06 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 14:42 Sean Young [this message]
2026-05-06 14:42 ` [PATCH 1/8] x86/platform: Remove Technology Systems 5500 board Sean Young
2026-05-06 14:42 ` [PATCH 2/8] mtd: ts5500_flash: Remove mapping since board is no longer supported Sean Young
2026-05-06 14:42 ` [PATCH 3/8] mtd: netsc520: " Sean Young
2026-05-06 14:42 ` [PATCH 4/8] mtd: sc520cdp: " Sean Young
2026-05-06 14:42 ` [PATCH 5/8] gpio: ts5500: Remove gpio driver as board " Sean Young
2026-05-06 14:42 ` [PATCH 6/8] watchdog: sc520: Drop AMD Elan SC520 support Sean Young
2026-05-06 14:51 ` Guenter Roeck
2026-05-06 14:42 ` [PATCH 7/8] cpufreq: sc520_freq: Drop support for AMD Elan SC520 Sean Young
2026-05-06 14:42 ` [PATCH 8/8] cpufreq: elanfreq: Drop support for AMD Elan SC4* Sean Young
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=cover.1778071745.git.sean@mess.org \
--to=sean@mess.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox