From: Geert Uytterhoeven <geert+renesas@glider.be>
To: "Magnus Damm" <magnus.damm@gmail.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH/RFC 0/3] Remove KZM9D board staging support
Date: Fri, 9 Jun 2023 18:10:48 +0200 [thread overview]
Message-ID: <cover.1686325857.git.geert+renesas@glider.be> (raw)
Hi all,
Board staging was introduced to host temporarily legacy board support
for platforms that are under active conversion to DT. Currently it
hosts:
1. USB Gadget support for the Kyoto Microcomputer Co. KZM-A9-Dual
(KZM9D) development board,
2. Display support for the Atmark Techno Armadillo-800-EVA development
board.
During the last few years, the KZM9D development board didn't receive
much love. Also, no one really cared about the EMMA Mobile USB Gadget
driver, which is also hosted under staging.
Hence this RFC patch series removes the KZM9D board staging support,
together with the EMMA Mobile USB Gadget driver, and the legacy EMMA
Mobile EV2 clkdev registration.
Once the SH-Mobile LCDC DRM driver has been converted to atomic
modesetting and DT, the remaining parts of board staging can be removed,
together with legacy clkdev registration in the MSTP driver.
Thanks for your comments!
Geert Uytterhoeven (3):
staging: emxx_udc: Remove EMMA Mobile USB Gadget driver
staging: board: Remove KZM9D board staging code
clk: renesas: emev2: Remove obsolete clkdev registration
drivers/clk/renesas/clk-emev2.c | 3 -
drivers/staging/Kconfig | 2 -
drivers/staging/Makefile | 1 -
drivers/staging/board/Makefile | 1 -
drivers/staging/board/kzm9d.c | 26 -
drivers/staging/emxx_udc/Kconfig | 11 -
drivers/staging/emxx_udc/Makefile | 2 -
drivers/staging/emxx_udc/TODO | 6 -
drivers/staging/emxx_udc/emxx_udc.c | 3223 ---------------------------
drivers/staging/emxx_udc/emxx_udc.h | 554 -----
10 files changed, 3829 deletions(-)
delete mode 100644 drivers/staging/board/kzm9d.c
delete mode 100644 drivers/staging/emxx_udc/Kconfig
delete mode 100644 drivers/staging/emxx_udc/Makefile
delete mode 100644 drivers/staging/emxx_udc/TODO
delete mode 100644 drivers/staging/emxx_udc/emxx_udc.c
delete mode 100644 drivers/staging/emxx_udc/emxx_udc.h
--
2.34.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2023-06-09 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 16:10 Geert Uytterhoeven [this message]
2023-06-09 16:10 ` [PATCH/RFC 1/3] staging: emxx_udc: Remove EMMA Mobile USB Gadget driver Geert Uytterhoeven
2023-06-09 16:55 ` Wolfram Sang
2023-06-09 16:10 ` [PATCH/RFC 2/3] staging: board: Remove KZM9D board staging code Geert Uytterhoeven
2023-06-09 16:56 ` Wolfram Sang
2023-06-09 16:10 ` [PATCH/RFC 3/3] clk: renesas: emev2: Remove obsolete clkdev registration Geert Uytterhoeven
2023-06-09 18:10 ` Geert Uytterhoeven
2023-06-09 16:58 ` [PATCH/RFC 0/3] Remove KZM9D board staging support Wolfram Sang
2023-06-09 22:24 ` Niklas Söderlund
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.1686325857.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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