From: Rob Herring <robh@kernel.org>
To: Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Udaya Kiran Challa <challauday369@gmail.com>,
krzk+dt@kernel.org, conor+dt@kernel.org,
skhan@linuxfoundation.org, me@brighamcampbell.com,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v4] spi: dt-bindings: microchip,pic32mzda-spi: Convert to DT schema
Date: Fri, 14 Aug 2026 14:07:59 -0500 [thread overview]
Message-ID: <20260814190759.GA2496807-robh@kernel.org> (raw)
In-Reply-To: <e7efc91b-9d8f-4344-982b-c2b5014985b6@sirena.org.uk>
On Fri, Aug 14, 2026 at 03:54:55PM +0100, Mark Brown wrote:
> On Fri, Aug 14, 2026 at 02:02:21PM +0530, Udaya Kiran Challa wrote:
> > Convert Microchip PIC32 SPI controller devicetree binding
> > from legacy text format to DT schema.
>
> > +maintainers:
> > + - Mark Brown <broonie@kernel.org>
>
> Try again! :P I think the DT people had some default they used for
> cases like this, but ICBW?
I'm the default, but really I wonder if pic32 could just be dropped. No
commits from a Microchip person since 2016 on arch/mips/pic32 or
arch/mips/boot/dts/pic32. Almost all generic cleanups otherwise. These
chips appear to max out at 32MB (SiP) or 128MB DDR2.
Perhaps I should send some AI patches against it...
There's this[1], but no updates in 5 years.
Arnd, Thomas, any thoughts on this platform?
Rob
[1] https://github.com/jjr-simiatec/Linux-LTS-for-PIC32
prev parent reply other threads:[~2026-08-14 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 8:32 [PATCH v4] spi: dt-bindings: microchip,pic32mzda-spi: Convert to DT schema Udaya Kiran Challa
2026-08-14 9:21 ` sashiko-bot
2026-08-14 14:54 ` Mark Brown
2026-08-14 19:07 ` Rob Herring [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=20260814190759.GA2496807-robh@kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=challauday369@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=me@brighamcampbell.com \
--cc=skhan@linuxfoundation.org \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.