From: Mark Brown <broonie@kernel.org>
To: Sameer Pujar <spujar@nvidia.com>
Cc: oder_chiou@realtek.com, robh@kernel.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.com, lgirdwood@gmail.com, thierry.reding@gmail.com,
linux-tegra@vger.kernel.org, jonathanh@nvidia.com
Subject: Re: [RFC PATCH 2/3] ASoC: rt5659: Expose internal clock relationships
Date: Fri, 11 Mar 2022 13:35:42 +0000 [thread overview]
Message-ID: <YitQLsUAEHM7gXEG@sirena.org.uk> (raw)
In-Reply-To: <5c531e7c-58e4-2c55-57cb-85eff68b0927@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
On Thu, Mar 10, 2022 at 08:29:26PM +0530, Sameer Pujar wrote:
> Yes, it would be required and I will include it in v2. In this series, I
> wanted to get some initial feedback if the idea is right.
It looks plausible.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Sameer Pujar <spujar@nvidia.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
oder_chiou@realtek.com, robh@kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] ASoC: rt5659: Expose internal clock relationships
Date: Fri, 11 Mar 2022 13:35:42 +0000 [thread overview]
Message-ID: <YitQLsUAEHM7gXEG@sirena.org.uk> (raw)
In-Reply-To: <5c531e7c-58e4-2c55-57cb-85eff68b0927@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
On Thu, Mar 10, 2022 at 08:29:26PM +0530, Sameer Pujar wrote:
> Yes, it would be required and I will include it in v2. In this series, I
> wanted to get some initial feedback if the idea is right.
It looks plausible.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-11 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 11:41 [RFC PATCH 0/3] Flexible codec clock configuration Sameer Pujar
2022-03-10 11:41 ` Sameer Pujar
2022-03-10 11:41 ` [RFC PATCH 1/3] ASoC: soc-pcm: tweak DPCM BE hw_param() call order Sameer Pujar
2022-03-10 11:41 ` Sameer Pujar
2022-03-10 11:41 ` [RFC PATCH 2/3] ASoC: rt5659: Expose internal clock relationships Sameer Pujar
2022-03-10 11:41 ` Sameer Pujar
2022-03-10 12:14 ` Mark Brown
2022-03-10 12:14 ` Mark Brown
2022-03-10 14:59 ` Sameer Pujar
2022-03-11 13:35 ` Mark Brown [this message]
2022-03-11 13:35 ` Mark Brown
2022-03-10 11:41 ` [RFC PATCH 3/3] ASoC: tegra: Get clock rate in consumer mode Sameer Pujar
2022-03-10 11:41 ` Sameer Pujar
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=YitQLsUAEHM7gXEG@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=robh@kernel.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.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.