Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>, broonie@kernel.org
Cc: lgirdwood@gmail.com, yung-chuan.liao@linux.intel.com,
	peter.ujfalusi@linux.intel.com, patches@opensource.cirrus.com,
	linux-sound@vger.kernel.org
Subject: Re: [PATCH v3 0/7] Add SDCA IRQ support and some misc fixups
Date: Thu, 26 Jun 2025 14:00:17 +0200	[thread overview]
Message-ID: <f94e3e3a-7175-4d59-9ebf-12d26fd57223@linux.dev> (raw)
In-Reply-To: <20250624122844.2761627-1-ckeepax@opensource.cirrus.com>

On 6/24/25 14:28, Charles Keepax wrote:
> Add a maintainers entry for SDCA, do a couple of small fixups for
> previous chains, and then adding the beginnings of the SDCA IRQ
> handling. This is based around a regmap IRQ chip and a few helper
> functions that can be called from the client drivers to setup the
> IRQs.
> 
> Thanks,
> Charles
> 
> Changes since v2:
>  - Just a rebase to avoid a conflict with the recently merged SDCA HID
>    stuff.

For the series:

Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>

> Charles Keepax (6):
>   MAINTAINERS: Add SDCA maintainers entry
>   ASoC: SDCA: Add missing default in switch in entity_pde_event()
>   ASoC: SDCA: Fixup some kernel doc errors
>   ASoC: SDCA: Minor selected/detected mode control fixups
>   ASoC: SDCA: Add flag for unused IRQs
>   ASoC: SDCA: Add some initial IRQ handlers
> 
> Maciej Strozek (1):
>   ASoC: SDCA: Generic interrupt support
> 
>  MAINTAINERS                      |  11 +
>  include/sound/sdca_function.h    |  11 +
>  include/sound/sdca_interrupts.h  |  78 ++++++
>  sound/soc/sdca/Kconfig           |   7 +
>  sound/soc/sdca/Makefile          |   5 +-
>  sound/soc/sdca/sdca_asoc.c       |  19 +-
>  sound/soc/sdca/sdca_functions.c  |   2 +
>  sound/soc/sdca/sdca_interrupts.c | 439 +++++++++++++++++++++++++++++++
>  8 files changed, 564 insertions(+), 8 deletions(-)
>  create mode 100644 include/sound/sdca_interrupts.h
>  create mode 100644 sound/soc/sdca/sdca_interrupts.c
> 


  parent reply	other threads:[~2025-06-26 12:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 12:28 [PATCH v3 0/7] Add SDCA IRQ support and some misc fixups Charles Keepax
2025-06-24 12:28 ` [PATCH v3 1/7] MAINTAINERS: Add SDCA maintainers entry Charles Keepax
2025-06-24 12:28 ` [PATCH v3 2/7] ASoC: SDCA: Add missing default in switch in entity_pde_event() Charles Keepax
2025-06-24 12:28 ` [PATCH v3 3/7] ASoC: SDCA: Fixup some kernel doc errors Charles Keepax
2025-06-24 12:28 ` [PATCH v3 4/7] ASoC: SDCA: Minor selected/detected mode control fixups Charles Keepax
2025-06-24 12:28 ` [PATCH v3 5/7] ASoC: SDCA: Add flag for unused IRQs Charles Keepax
2025-06-24 12:28 ` [PATCH v3 6/7] ASoC: SDCA: Generic interrupt support Charles Keepax
2025-06-24 12:28 ` [PATCH v3 7/7] ASoC: SDCA: Add some initial IRQ handlers Charles Keepax
2025-06-26 12:00 ` Pierre-Louis Bossart [this message]
2025-07-01 23:34 ` [PATCH v3 0/7] Add SDCA IRQ support and some misc fixups Mark Brown

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=f94e3e3a-7175-4d59-9ebf-12d26fd57223@linux.dev \
    --to=pierre-louis.bossart@linux.dev \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=yung-chuan.liao@linux.intel.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