From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Lee Jones <lee@kernel.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: broonie@kernel.org, vkoul@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linus.walleij@linaro.org, lgirdwood@gmail.com,
yung-chuan.liao@linux.intel.com, sanyog.r.kale@intel.com,
alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/6] soundwire: bus: Allow SoundWire peripherals to register IRQ handlers
Date: Fri, 28 Jul 2023 18:44:45 +0200 [thread overview]
Message-ID: <db5f1478-8aca-fb57-c3fc-aa09071a0829@linux.intel.com> (raw)
In-Reply-To: <20230728151818.GL8175@google.com>
On 7/28/23 17:18, Lee Jones wrote:
> Vinod, Bard, Pierre-Louis, Sanyog,
>
> This has been on the list for some time now.
>
> Would one of you please review this, so we can get it merged?
Sorry, I thought I provided my tag on an earlier version, but apparently
that never reached the ML. All my earlier feedback was taken into
account so no objections from me - just one typo below...
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> On Tue, 25 Jul 2023, Charles Keepax wrote:
>
>> From: Lucas Tanure <tanureal@opensource.cirrus.com>
>>
>> Currently the in-band alerts for SoundWire peripherals can only
>> be communicated to the driver through the interrupt_callback
>> function. This however is slightly inconvient for devices that wish to
inconvenient
>> share IRQ handling code between SoundWire and I2C/SPI, the later would
>> normally register an IRQ handler with the IRQ subsystem. However there
>> is no reason the SoundWire in-band IRQs can not also be communicated
>> as an actual IRQ to the driver.
next prev parent reply other threads:[~2023-07-28 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 10:25 [PATCH v6 0/6] Add cs42l43 PC focused SoundWire CODEC Charles Keepax
2023-07-25 10:25 ` [PATCH v6 1/6] soundwire: bus: Allow SoundWire peripherals to register IRQ handlers Charles Keepax
2023-07-28 15:18 ` Lee Jones
2023-07-28 16:44 ` Pierre-Louis Bossart [this message]
2023-07-31 1:03 ` Liao, Bard
2023-07-31 11:29 ` Vinod Koul
2023-07-25 10:25 ` [PATCH v6 2/6] dt-bindings: mfd: cirrus,cs42l43: Add initial DT binding Charles Keepax
2023-07-25 10:25 ` [PATCH v6 3/6] mfd: cs42l43: Add support for cs42l43 core driver Charles Keepax
2023-07-25 10:25 ` [PATCH v6 4/6] pinctrl: cs42l43: Add support for the cs42l43 Charles Keepax
2023-07-25 10:25 ` [PATCH v6 5/6] spi: cs42l43: Add SPI controller support Charles Keepax
2023-07-25 10:25 ` [PATCH v6 6/6] ASoC: cs42l43: Add support for the cs42l43 Charles Keepax
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=db5f1478-8aca-fb57-c3fc-aa09071a0829@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
--cc=sanyog.r.kale@intel.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 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.