Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jeremy J. Peper" <jeremy@jeremypeper.com>,
	linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
	"Russell King" <linux@armlinux.org.uk>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Richard Earnshaw" <richard.earnshaw@arm.com>,
	"Richard Sandiford" <richard.sandiford@arm.com>,
	"Ramana Radhakrishnan" <ramanara@nvidia.com>,
	"Nicolas Pitre" <nico@fluxnic.net>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Mark Brown" <broonie@kernel.org>,
	"Kristoffer Ericson" <kristoffer.ericson@gmail.com>,
	"Robert Jarzmik" <robert.jarzmik@free.fr>,
	"Aaro Koskinen" <aaro.koskinen@iki.fi>,
	"Janusz Krzysztofik" <jmkrzyszt@gmail.com>,
	"Tony Lindgren" <tony@atomide.com>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	"Nikita Shubin" <nikita.shubin@maquefel.me>,
	linux-samsung-soc@vger.kernel.org, "Andrew Lunn" <andrew@lunn.ch>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	"Gregory Clement" <gregory.clement@bootlin.com>,
	debian-arm@lists.debian.org,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@foss.st.com>
Subject: Re: [RFC} arm architecture board/feature deprecation timeline
Date: Mon, 19 Aug 2024 16:12:10 +0200	[thread overview]
Message-ID: <a8c009b5-ada0-4f78-92f7-7a6c5075ccf1@app.fastmail.com> (raw)
In-Reply-To: <790bf2c4-2ecf-429c-8e28-ad5807ffed7a@app.fastmail.com>

Two small additions:

On Mon, Aug 19, 2024, at 11:17, Arnd Bergmann wrote:
> On Thu, Aug 15, 2024, at 21:53, jeremy@jeremypeper.com wrote:
> I expect that the terastation pro2 is going to be fairly easy to
> convert to DT as there is already support for similar Orion5x
> machines. In this case I would just remove all the Orion5x board
> files and you can add a dts file later on. The bit I'm unsure
> about here is legacy PCI support. I see that the board file enables
> both PCI and PCIe, but I don't know if both are actually used,
> or if everything is on PCIe.
>
> I have some old patches for separating orion legacy PCI from
> PCIe support, as only the latter has a modern driver (shared
> with kirkwood and armadaxp). If you can confirm that the machine
> actually uses PCI, I can dig those out from my backups.

I did find this myself later, the machine does use an on-board
PCI connected SATA controller, which is obviously required to
make the machine useful.

Doing a PCI host bridge driver with DT support correctly is
a lot of work, especially if there is only a single machine
using it. Since this uses the same drivers/ata/sata-mv.c
driver as the other orion/kirkwood machines, I wonder if we
can just pretend that this is a platform device and skip
all of the PCI probing. I think this only needs a few
small changes to the sata-mv.c driver, but it does require
that the PCI bus is left in a known state by the boot loader.

> The WXL machine is going to be more work since there is currently
> no DT support for mv78xx0, but everything except the pin controller
> should at least have a driver since this SoC is somewhere between
> Kirkwood and Dove. Having a hack for the pin controller similar
> to what orion5x has is probably fine, especially if you only
> need to support one machine.

The complication here is that removing the board file would
imply that all of the mv78xx0 code immediately becomes dead
code. I guess the next best idea is to remove the orion5x
and dove board files first and then move bits of plat-orion
that are actually used by the WXL machine into the mv78xx0
directory.

      Arnd

  reply	other threads:[~2024-08-19 14:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 17:29 [RFC} arm architecture board/feature deprecation timeline Arnd Bergmann
2024-07-31 19:13 ` Aaro Koskinen
2024-08-01  8:59   ` Arnd Bergmann
2024-08-01 18:23     ` Aaro Koskinen
2024-08-02 12:53       ` Arnd Bergmann
2024-08-05  7:58     ` Arnd Bergmann
2024-08-05 12:30       ` Tony Lindgren
2024-08-05 13:37         ` Arnd Bergmann
2024-08-01  8:04 ` Krzysztof Kozlowski
2024-08-01 14:15 ` Richard Earnshaw
2024-08-02 15:12   ` Arnd Bergmann
2024-08-02 23:04     ` Linus Walleij
2024-08-20 14:58     ` Richard Earnshaw
2024-08-20 16:33       ` Arnd Bergmann
2024-08-01 19:53 ` Linus Walleij
2024-08-02 14:52   ` Arnd Bergmann
2024-08-15 18:24 ` Matt Turner
2024-08-19  7:37   ` Arnd Bergmann
2024-08-15 19:53 ` jeremy
2024-08-19  9:17   ` Arnd Bergmann
2024-08-19 14:12     ` Arnd Bergmann [this message]
2024-08-19 14:23       ` Andrew Lunn
2024-08-19 14:34         ` Arnd Bergmann
2024-08-19 17:08         ` jeremy
2024-08-21  6:15 ` Alexander Dahl
2024-08-21  7:51   ` 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=a8c009b5-ada0-4f78-92f7-7a6c5075ccf1@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=aaro.koskinen@iki.fi \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --cc=debian-arm@lists.debian.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregory.clement@bootlin.com \
    --cc=jeremy@jeremypeper.com \
    --cc=jmkrzyszt@gmail.com \
    --cc=kristoffer.ericson@gmail.com \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=nico@fluxnic.net \
    --cc=nikita.shubin@maquefel.me \
    --cc=ramanara@nvidia.com \
    --cc=richard.earnshaw@arm.com \
    --cc=richard.sandiford@arm.com \
    --cc=robert.jarzmik@free.fr \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tony@atomide.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