From: Imre Kaloz <kaloz@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
mfd@lists.linux.dev, linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 31/53] mfd: ioc3: Add support for IOC4
Date: Tue, 20 Oct 2026 23:07:47 +0200 [thread overview]
Message-ID: <20261020210749.11045-1-kaloz@kernel.org> (raw)
In-Reply-To: <179198346971.839288.6829273567060577383@kernel.org>
On Tue, 20 Oct 2026, Lee Jones wrote:
> > 5 files changed, 438 insertions(+), 46 deletions(-)
>
> Do we really need to bundle all of these changes into this commit?
>
> This is going to be a nightmare to review!
Fair point, and sorry about that. It grew in one piece while I was
bringing the hardware up, and I should have cut it up before posting.
For v3 I'll split it into five patches:
1. mfd: ioc3: Add per-variant interrupt banks
The irq_chip, domain map and chained handler move to a bank table,
and ioc3_priv_data gets a variant pointer and a generic __iomem
base. Only the IOC3 variant exists at this point.
2. MIPS: SGI-IP27: Add IOC4 register definitions
arch/mips/include/asm/sn/ioc4.h on its own.
3. serial: 8250_ioc3: Take the UART clock from platform data
include/linux/platform_data/sgi-ioc3-serial.h and the one-line
change in 8250_ioc3.c, with the MAINTAINERS entry for the header.
4. mfd: ioc3: Add support for IOC4
The IOC4 variant, its two interrupt banks, ioc4_setup() and the
non-serial cells (kbd, RTC and, from patch 46, ATA).
5. mfd: ioc3: Add IOC4 serial cells
ioc4_serial_setup(), the firmware revision check and the four
UART cells.
Each one builds on its own, and 1 and 3 leave IOC3 boards behaving
exactly as before, so they should be easy to check in isolation.
The overall shape of v3 still depends on what Thomas prefers for the
series, so it will follow once he has had a chance to look.
Thanks for taking the time to go through it,
Imre
next prev parent reply other threads:[~2026-10-20 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:16 [PATCH v2 00/53] MIPS: SGI-IP27: add support for the IP35 (Bedrock hub) machines Imre Kaloz
2026-10-13 13:16 ` [PATCH v2 31/53] mfd: ioc3: Add support for IOC4 Imre Kaloz
2026-10-20 12:02 ` Lee Jones
2026-10-20 21:07 ` Imre Kaloz [this message]
2026-10-13 13:35 ` [PATCH v2 00/53] MIPS: SGI-IP27: add support for the IP35 (Bedrock hub) machines Niklas Cassel
2026-10-13 14:25 ` Imre Kaloz
2026-10-20 18:06 ` Jakub Kicinski
2026-10-20 20:42 ` Imre Kaloz
2026-10-20 21:56 ` Jakub Kicinski
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=20261020210749.11045-1-kaloz@kernel.org \
--to=kaloz@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox