From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>, vkoul@kernel.org
Cc: yung-chuan.liao@linux.intel.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH v2 0/2] Fix minor issue in SoundWire slave IRQ mapping
Date: Mon, 5 May 2025 12:03:23 +0200 [thread overview]
Message-ID: <70240985-5f8f-42a9-b5a6-74fd6713f6f3@linux.dev> (raw)
In-Reply-To: <20250429101808.348462-1-ckeepax@opensource.cirrus.com>
On 4/29/25 05:18, Charles Keepax wrote:
> Currently there would be problems if multiple devices on the same bus
> attempted to use SoundWire IRQ handling rather than the IRQ callback
> mechanism. So far only cs42l43 uses this system so this hasn't caused
> any problems.
>
> Thanks,
> Charles
>
> Changes since v1:
> - Don't reuse the new IDA for the dev_num
> - Expand the number of devices allowed on a bus to 16
>
> Charles Keepax (2):
> soundwire: bus: Simplify sdw_assign_device_num()
> soundwire: bus: Add internal slave ID and use for IRQs
LGTM,
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
>
> drivers/soundwire/bus.c | 31 ++++++++++++++-----------------
> drivers/soundwire/bus_type.c | 10 ++++++++++
> drivers/soundwire/irq.c | 6 +++---
> include/linux/soundwire/sdw.h | 6 ++++++
> 4 files changed, 33 insertions(+), 20 deletions(-)
>
next prev parent reply other threads:[~2025-05-05 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 10:18 [PATCH v2 0/2] Fix minor issue in SoundWire slave IRQ mapping Charles Keepax
2025-04-29 10:18 ` [PATCH v2 1/2] soundwire: bus: Simplify sdw_assign_device_num() Charles Keepax
2025-04-29 10:18 ` [PATCH v2 2/2] soundwire: bus: Add internal slave ID and use for IRQs Charles Keepax
2025-05-05 10:03 ` Pierre-Louis Bossart [this message]
2025-05-14 11:45 ` [PATCH v2 0/2] Fix minor issue in SoundWire slave IRQ mapping Vinod Koul
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=70240985-5f8f-42a9-b5a6-74fd6713f6f3@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=vkoul@kernel.org \
--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