From: Robert Jarzmik <jarzmik.robert@orange.fr>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
stern@rowland.harvard.edu, alexandre.belloni@bootlin.com,
brgl@bgdev.pl, damien.lemoal@opensource.wdc.com,
dmitry.torokhov@gmail.com, linux@dominikbrodowski.net,
balbi@kernel.org, gregkh@linuxfoundation.org, deller@gmx.de,
perex@perex.cz, jingoohan1@gmail.com, lee@kernel.org,
kernel@wantstofly.org, lgirdwood@gmail.com,
linus.walleij@linaro.org, marek.vasut@gmail.com,
broonie@kernel.org, mkpetch@internode.on.net,
miquel.raynal@bootlin.com, lost.distance@yahoo.com,
philipp.zabel@gmail.com, linux@armlinux.org.uk, sre@kernel.org,
slapin@ossfans.org, s.shtylyov@omp.ru,
sudipm.mukherjee@gmail.com, tiwai@suse.com,
ulf.hansson@linaro.org, vigneshr@ti.com, viresh.kumar@linaro.org,
wsa+renesas@sang-engineering.com, linux-pm@vger.kernel.org,
linux-ide@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-input@vger.kernel.org, patches@opensource.cirrus.com,
linux-leds@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-rtc@vger.kernel.org, linux-usb@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 00/30] ARM: pxa: remove all unused boards&drivers
Date: Wed, 19 Oct 2022 23:13:48 +0200 [thread overview]
Message-ID: <m2r0z3h5yr.fsf@sopl295.home> (raw)
In-Reply-To: <20221019161831.3864786-1-arnd@kernel.org> (Arnd Bergmann's message of "Wed, 19 Oct 2022 18:17:53 +0200")
Arnd Bergmann <arnd@kernel.org> writes:
> From: Arnd Bergmann <arnd@arndb.de>
...zip...
> A good number of drivers become impossible to select after this, so
> each of these also get dropped. I'm including the driver patches in the
> series here and can either merge them through the soc tree, or they
> can get picked up by the individual subsystem maintainers. Since both
> the platform and the drivers get removed, the order should not matter.
This part is a bit ... bothering.
I at least identified these :
> delete mode 100644 drivers/input/touchscreen/wm9705.c
> delete mode 100644 drivers/input/touchscreen/wm9712.c
> delete mode 100644 drivers/input/touchscreen/wm9713.c
> delete mode 100644 drivers/input/touchscreen/wm97xx-core.c
> delete mode 100644 drivers/mfd/wm97xx-core.c
> delete mode 100644 sound/ac97/bus.c
> delete mode 100644 sound/ac97/codec.c
> delete mode 100644 sound/ac97/snd_ac97_compat.c
For the existing platforms working with devicetree support (mioa701 for
example), the wm9713 was properly used, providing both sound support and input
touchscreen.
So was the a97 part, providing a framework to make the wm9713 work.
So I'm wondering how the choice to chop these drivers was done, and it is
necessary to remove them. If so, maybe pxa support in the kernel should be
removed all together, as people playing with it loose part of the working DT
platforms they had.
As for the removal of defconfigs and arch-pxa, sure, this was PXA's destiny.
Cheers.
--
Robert
PS: If this mail is sent twice, sorry in advance, my mailer is a bad mood
lately.
next prev parent reply other threads:[~2022-10-19 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 16:17 [PATCH 00/30] ARM: pxa: remove all unused boards&drivers Arnd Bergmann
2022-10-19 21:13 ` Robert Jarzmik
2022-10-19 21:13 ` Robert Jarzmik [this message]
2022-10-20 7:30 ` Arnd Bergmann
[not found] ` <803778517.2279639.1667493436959.JavaMail.open-xchange@opme11oxm02aub.pom.fr.intraorange>
2022-11-04 9:20 ` Arnd Bergmann
2022-10-20 7:12 ` Lee Jones
2022-10-20 7:32 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2022-10-19 15:50 Arnd Bergmann
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=m2r0z3h5yr.fsf@sopl295.home \
--to=jarzmik.robert@orange.fr \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=balbi@kernel.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel@zonque.org \
--cc=deller@gmx.de \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=haojian.zhuang@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=kernel@wantstofly.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@dominikbrodowski.net \
--cc=lost.distance@yahoo.com \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=mkpetch@internode.on.net \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=philipp.zabel@gmail.com \
--cc=s.shtylyov@omp.ru \
--cc=slapin@ossfans.org \
--cc=sre@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=sudipm.mukherjee@gmail.com \
--cc=tiwai@suse.com \
--cc=ulf.hansson@linaro.org \
--cc=vigneshr@ti.com \
--cc=viresh.kumar@linaro.org \
--cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).