devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Rob Herring" <robh@kernel.org>,
	 "Geert Uytterhoeven" <geert+renesas@glider.be>,
	 "Magnus Damm" <magnus.damm@gmail.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	 "Conor Dooley" <conor+dt@kernel.org>,
	 "Daniel Mack" <daniel@zonque.org>,
	 "Haojian Zhuang" <haojian.zhuang@gmail.com>,
	 "Andrew Lunn" <andrew@lunn.ch>,
	"Gregory Clement" <gregory.clement@bootlin.com>,
	 "Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	 Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: intel: Drop pxa2xx
Date: Sat, 03 Jan 2026 21:54:35 +0100	[thread overview]
Message-ID: <m2qzs6l8ms.fsf@free.fr> (raw)
In-Reply-To: <4e5c631e-8c7f-4f38-a60e-2db829ff9f06@app.fastmail.com> (Arnd Bergmann's message of "Wed, 31 Dec 2025 01:02:55 +0100")

"Arnd Bergmann" <arnd@arndb.de> writes:

> If you or anyone else is still using PXA27x, we can always
> bring it back later, but I'd then put the burden on them to
> submit the dts file for inclusion without introducing DT
> warnings.
Well not anymore, for RAM constraints as I said.
I can still fallback to an older kernel though if I feel like 
hacking.

>> +	docg3: flash@0 {
>> +		compatible = "m-systems,diskonchip-g3";
>> +		reg = <0x0 0x2000>;
>> +	};
>
> This currently has no upstream users I can see, so
> removing pxa27x would probably mean we should remove
> that as well.
Yep, this driver was only used on the Mitac MIO A701 (my main 
board,
pxa27x based).

>> +	panel {
>> +		compatible = "toshiba,ltm0305a776";
>> +		lcd-type = "color-tft";
>
> I don't see a driver that matches the compatible string,
> does this one actually work?
Yes it does. The compatible string doesn't really matter. What is
relevant in that part is the "timings" node, which is used by 
pxafb
driver to setup its registers to control the LCD panel.

More generally, each and every part of this DT was working 3 years 
ago.

Cheers.

--
Robert

      reply	other threads:[~2026-01-03 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12 20:32 [PATCH] ARM: dts: intel: Drop pxa2xx Rob Herring (Arm)
2025-12-12 21:58 ` Robert Jarzmik
2025-12-17 16:04   ` Arnd Bergmann
2025-12-18  8:21     ` Daniel
2025-12-22 22:04       ` Arnd Bergmann
2025-12-28 11:11     ` Robert Jarzmik
2025-12-31  0:02       ` Arnd Bergmann
2026-01-03 20:54         ` Robert Jarzmik [this message]

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=m2qzs6l8ms.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=daniel@zonque.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gregory.clement@bootlin.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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).