[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2z2JwQaYS9N5A8x@sirena.org.uk>
Date: Thu, 10 Nov 2022 13:01:27 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: Marc Zyngier <maz@...nel.org>, lee@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, linus.walleij@...aro.org,
tglx@...utronix.de, alsa-devel@...a-project.org,
devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH 09/12] irqchip: cirrus: Add driver for Cirrus Logic
CS48L31/32/33 codecs
On Thu, Nov 10, 2022 at 11:22:26AM +0000, Richard Fitzgerald wrote:
> On 10/11/2022 08:02, Marc Zyngier wrote:
> > belongs IMO to the MFD code.
> We did once put interrupt support in MFD for an older product line but
> the MFD maintainer doesn't like the MFD being a dumping-ground for
> random other functionality that have their own subsystems.
There's bits of this like logging the top level error interrupts that
seem like they clearly fit in the driver for the top level chip (SYSCLK
possibly in the audio driver, dunno if it gets used by other functions),
they're users of the interrupt controller rather than part of the
interrupt controller.
> > It is also a direct copy of the existing
> > irq-madera.c code, duplicated for no obvious reason.
> It's not a duplicate. The register map of this device is different
> (different addressing, 32-bit registers not 16-bit)
Isn't that just a data difference which could be parameterised?
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists