From: Vinod Koul <vkoul@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: broonie@kernel.org, oder_chiou@realtek.com, jack.yu@realtek.com,
shumingf@realtek.com, lgirdwood@gmail.com,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
sanyog.r.kale@intel.com, pierre-louis.bossart@linux.dev,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 1/5] soundwire: SDCA: Add additional SDCA address macros
Date: Mon, 23 Dec 2024 11:43:49 +0530 [thread overview]
Message-ID: <Z2j/nQmZsU+3yqXc@vaman> (raw)
In-Reply-To: <20241217135921.3572496-2-ckeepax@opensource.cirrus.com>
On 17-12-24, 13:59, Charles Keepax wrote:
> Compliment the existing macro to construct an SDCA control address
> with macros to extract the constituent parts, and validation of such
> an address. Also update the masks for the original macro to use
> GENMASK to make mental comparisons with the included comment on the
> address format easier.
I guess this could go thru asoc/regmap trees so
Acked-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2024-12-23 6:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 13:59 [PATCH 0/5] Expand SoundWire MBQ register map support Charles Keepax
2024-12-17 13:59 ` [PATCH 1/5] soundwire: SDCA: Add additional SDCA address macros Charles Keepax
2024-12-23 6:13 ` Vinod Koul [this message]
2024-12-17 13:59 ` [PATCH 2/5] ASoC: SDCA: Update list of entity_0 controls Charles Keepax
2024-12-17 13:59 ` [PATCH 3/5] regmap: sdw-mbq: Add support for further MBQ register sizes Charles Keepax
2024-12-17 13:59 ` [PATCH 4/5] regmap: sdw-mbq: Add support for SDCA deferred controls Charles Keepax
2024-12-17 13:59 ` [PATCH 5/5] ASoC: rt722-sdca: Make use of new expanded MBQ regmap Charles Keepax
2024-12-18 7:56 ` Shuming [范書銘]
2025-01-08 13:32 ` (subset) [PATCH 0/5] Expand SoundWire MBQ register map support 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=Z2j/nQmZsU+3yqXc@vaman \
--to=vkoul@kernel.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=jack.yu@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=sanyog.r.kale@intel.com \
--cc=shumingf@realtek.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