From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
ranjani.sridharan@linux.intel.com, broonie@kernel.org,
peter.ujfalusi@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH v2 0/2] ASoC/soundwire: revisit support for clock registers
Date: Mon, 9 Jan 2023 21:38:09 +0530 [thread overview]
Message-ID: <Y7w76Vv12JBJAOP9@matsya> (raw)
In-Reply-To: <20221118025807.534863-1-yung-chuan.liao@linux.intel.com>
On 18-11-22, 10:58, Bard Liao wrote:
> SoundWire clock base and scale registers are only supported for SDCA
> devices. That's fine, but that leaves SoundWire 1.2 with optional
> registers not supported. This is a corner case that needs to be supported.
>
> The change is mainly on soundwire. But rt1318-sdw.c was applied to
> ASoC tree recently and not in SoundWire tree yet. @Vinod, Are you good
> if we go throutgh ASoC tree? Or @Mark can provide a tag and we can go
> through SoundWire tree?
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2023-01-09 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 2:58 [PATCH v2 0/2] ASoC/soundwire: revisit support for clock registers Bard Liao
2022-11-18 2:58 ` [PATCH v2 1/2] ASoC/soundwire: remove is_sdca boolean property Bard Liao
2022-11-18 15:39 ` Mark Brown
2022-11-23 14:52 ` Vinod Koul
2022-11-23 15:25 ` Mark Brown
2022-11-23 17:16 ` Vinod Koul
2022-11-23 9:33 ` Charles Keepax
2022-11-18 2:58 ` [PATCH v2 2/2] soundwire: enable optional clock registers for SoundWire 1.2 devices Bard Liao
2022-11-23 9:33 ` Charles Keepax
2023-01-09 16:08 ` Vinod Koul [this message]
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=Y7w76Vv12JBJAOP9@matsya \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).