From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
igor <igor@compulab.co.il>,
Boris Brezillon <boris.brezillon@collabora.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Mike Rapoport <mike@compulab.co.il>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] ARM: pxa: remove Compulab pxa2xx boards
Date: Wed, 20 May 2020 12:21:52 +0200 [thread overview]
Message-ID: <87h7waoqin.fsf@belgarion.home> (raw)
In-Reply-To: <CAK8P3a3E=Fq6ZXLkeQgufeJCP0gZiN1uXA2J=HzpH3D49GOMXQ@mail.gmail.com> (Arnd Bergmann's message of "Wed, 13 May 2020 22:39:59 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Wed, May 13, 2020 at 7:01 PM Robert Jarzmik <robert.jarzmik@free.fr> wrote:
>> CONFIG_MACH_EXEDA=y
>
> CONFIG_MACH_EXEDA should be removed here as well, it refers
> to part of em-x270.c
>
> Similarly, the whole em_x270_defconfig can be removed.
Certainly.
> Now arch/arm/mach-pxa/include/mach/io.h is unused and
> can be removed.
Yes.
> With MACH_ARMCORE gone, the MTD_NAND_CM_X270 and
> PCI_HOST_ITE8152 become impossible to select, and
> a part of PCMCIA_PXA2XX (pxa2xx_cm_x2xx_cs.c) becomes
> unused.
>
> FB_MBX can still be selected, but there are no boards defining
> the platform data any more, so I'd like to remove that as well.
That should be dealt with another time, sorry.
> MACH_EXEDA here is also obsolete, and I'd probably want to
> update the SND_PXA2XX_SOC_EM_X270 dependencies in the
> same patch.
Yes.
>
>> -static struct spi_board_info spi_board_info[] __initdata = {
>> - [0] = {
>> - .modalias = "rtc-max6902",
>> - .max_speed_hz = 1000000,
>> - .bus_num = 1,
>> - .chip_select = 0,
>
> Another last reference, so we can remove that the corresponding driver.
Another patch serie for this as well.
> Same here, there is still one more user left (MACH_ZIPIT2), though
> at some point that might get removed if we decide to drop the handhelds
> with 32MB RAM or less. That is probably something to be left for
> another time, but I see that pxa_defconfig produces a 9.5MB kernel
> image, so this is getting rather tight, and 32MB wasn't much when this
> got added in 2010.
Yeah, but no PXA user would ever use the pxa_defconfig kernel :)
A typical kernel for a PXA board is right now around 4MB, which is very tight
for 32MB platforms, and just enough for 64MB ones.
Cheers.
--
Robert
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-05-20 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 17:01 [PATCH 1/2] ARM: pxa: remove Compulab pxa2xx boards Robert Jarzmik
2020-05-13 17:01 ` [PATCH 2/2] MAINTAINERS: pxa: remove Compulab arm/pxa support Robert Jarzmik
2020-05-13 17:05 ` [PATCH 1/2] ARM: pxa: remove Compulab pxa2xx boards Boris Brezillon
2020-05-13 20:39 ` Arnd Bergmann
2020-05-20 10:21 ` Robert Jarzmik [this message]
2020-05-20 13:49 ` 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=87h7waoqin.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=arnd@arndb.de \
--cc=boris.brezillon@collabora.com \
--cc=igor@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mike@compulab.co.il \
--cc=miquel.raynal@bootlin.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).