From: Caesar Wang <wxt@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
Doug Anderson <dianders@chromium.org>,
Heiko Stuebner <heiko@sntech.de>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-rockchip@lists.infradead.org,
Caesar Wang <wxt@rock-chips.com>,
Dylan Reid <dgreid@chromium.org>,
Sonny Rao <sonnyrao@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Cheng-Yi Chiang <cychiang@chromium.org>
Subject: Re: [PATCH v1 1/5] ASoC: rockchip: i2s: Support to set the divider clock API
Date: Fri, 6 Nov 2015 17:42:30 +0800 [thread overview]
Message-ID: <563C7606.7050504@rock-chips.com> (raw)
In-Reply-To: <20151105161615.GS18409@sirena.org.uk>
Hi Mark,
Very responsive, thanks your comment.
在 2015年11月06日 00:16, Mark Brown 写道:
> On Thu, Nov 05, 2015 at 01:56:39PM +0800, Caesar Wang wrote:
>> 在 2015年11月04日 22:34, Mark Brown 写道:
>>> Same thing as your other very similar patch: why does this feature
>>> require set_clkdiv()?
>> Okay, you said "
>> Why is this a requirement? The clock to use as a source should normally
>> be specified via set_sysclk() and any internal dividers calculated
>> automatically by the driver.
>> "
>> I think we should divider settings for these different sample rates.
> Sure, the question is how these things get set.
>
>> If the codec is master mode, we are *not* need this operate.
>> If the codec is slave mode, we are need to divider the MCLK to setting the different sample rates.
>> (for example, the sample rates (8k, 48k) the clock is MCLK, the clock should be divider cpu ip )
>> "dividers calculated automatically by the driver", that should be occured by codec(max98090
>> ) driver, but the divider clocks (LRCK, SCLK) should need to set for cpu internal side.
> So the CPU knows what rates it needs to set and what clocks it's getting
> in, why can't it set the dividers autonomously.
Sound resonable, fixed in next version.
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
--
caesar wang | software engineer | wxt@rock-chip.com
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-11-06 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 1:33 [PATCH v1 0/5] Support more sample rates, let the rates normal work Caesar Wang
2015-11-03 1:33 ` [PATCH v1 1/5] ASoC: rockchip: i2s: Support to set the divider clock API Caesar Wang
2015-11-04 14:34 ` Mark Brown
[not found] ` <563AEF97.1080304@gmail.com>
2015-11-05 16:16 ` Mark Brown
2015-11-06 9:42 ` Caesar Wang [this message]
2015-11-03 1:33 ` [PATCH v1 2/5] ASoC: rockchip-max98090: Allow more sample rates Caesar Wang
2015-11-03 1:33 ` [PATCH v1 3/5] ASoC: rockchip-rt5645: " Caesar Wang
2015-11-03 1:33 ` [PATCH v1 4/5] ASoC: rockchip-max98090: Add the divider clock for cpu Caesar Wang
2015-11-03 1:33 ` [PATCH v1 5/5] ASoC: rockchip-rt5645: " Caesar Wang
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=563C7606.7050504@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cychiang@chromium.org \
--cc=dgreid@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=sonnyrao@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox