From: Stephen Boyd <sboyd@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] ASoC: wcd934x: use the clock provider API
Date: Mon, 12 Apr 2021 13:26:28 -0700 [thread overview]
Message-ID: <161825918879.3764895.12600274147776655755@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210410111356.467340-3-jbrunet@baylibre.com>
Quoting Jerome Brunet (2021-04-10 04:13:53)
> Clock providers should use the clk_hw API
It sort of already is :)
>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH 2/5] ASoC: wcd934x: use the clock provider API
Date: Mon, 12 Apr 2021 13:26:28 -0700 [thread overview]
Message-ID: <161825918879.3764895.12600274147776655755@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210410111356.467340-3-jbrunet@baylibre.com>
Quoting Jerome Brunet (2021-04-10 04:13:53)
> Clock providers should use the clk_hw API
It sort of already is :)
>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2021-04-12 20:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 11:13 [PATCH 0/5] ASoC: clock provider clean-up Jerome Brunet
2021-04-10 11:13 ` Jerome Brunet
2021-04-10 11:13 ` [PATCH 1/5] ASoC: stm32: properly get clk from the provider Jerome Brunet
2021-04-10 11:13 ` Jerome Brunet
2021-04-12 20:25 ` Stephen Boyd
2021-04-12 20:25 ` Stephen Boyd
2021-04-10 11:13 ` [PATCH 2/5] ASoC: wcd934x: use the clock provider API Jerome Brunet
2021-04-10 11:13 ` Jerome Brunet
2021-04-12 20:26 ` Stephen Boyd [this message]
2021-04-12 20:26 ` Stephen Boyd
2021-04-10 11:13 ` [PATCH 3/5] ASoC: rt5682: clock driver must " Jerome Brunet
2021-04-10 11:13 ` Jerome Brunet
2021-04-12 20:27 ` Stephen Boyd
2021-04-12 20:27 ` Stephen Boyd
2021-04-13 7:31 ` Jerome Brunet
2021-04-10 11:13 ` [PATCH 4/5] ASoC: lpass: " Jerome Brunet
2021-04-10 11:13 ` Jerome Brunet
2021-04-12 9:38 ` Srinivas Kandagatla
2021-04-12 12:17 ` Jerome Brunet
2021-04-12 13:55 ` Srinivas Kandagatla
2021-04-10 11:13 ` [PATCH 5/5] ASoC: da7219: properly get clk from the provider Jerome Brunet
2021-04-10 11:13 ` Jerome Brunet
2021-04-12 20:27 ` Stephen Boyd
2021-04-12 20:27 ` Stephen Boyd
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=161825918879.3764895.12600274147776655755@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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.