From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: 최찬우 <cw00.choi@samsung.com>,
alsa-devel@alsa-project.org,
"Jassi Brar" <jassisinghbrar@gmail.com>,
"Jassi Brar" <jassi.brar@samsung.com>,
"Liam Girdwood" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: Add Jassi Brar as Samsung maintainer
Date: Sun, 26 Sep 2010 22:41:50 -0700 [thread overview]
Message-ID: <20100927054149.GA13056@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTi=JOwQD9sJG603NEQuqJU_N9fAA6nPAtq3YuAvF@mail.gmail.com>
On Mon, Sep 27, 2010 at 11:01:54AM +0900, Kyungmin Park wrote:
> Yes, recent Samsung SoC supports the clock & block gating. As the
> word, clock gating means enable/disable the clock and block gating
> means turn on/off some peripherals blocks to reduce the power. e..g,
> In case of audio, AUDIO block including I2S, AC97 and so on.
It's very straightforward, yes (though in the case of AC'97 the split
between CODEC and CPU is more tricky than you might at first think since
by default the CPU is clock master for everything).
> However codec is different. even though it can turn on/off codec, I
> think it have to re-initialize to use it and it takes some times.
The same is true for CPU IPs, of course. With modern CODECs this is
becoming less and less of an issue - with VMID referenced CODECs there
was always a lengthy delay to bring up VMID but with ground referenced,
PDM and class D outputs it's becoming less and less of an issue to just
power things down.
next prev parent reply other threads:[~2010-09-27 5:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 8:16 [PATCH] ASoC: Add Jassi Brar as Samsung maintainer Mark Brown
2010-09-25 12:15 ` Jassi Brar
2010-09-26 10:38 ` Kyungmin Park
2010-09-26 10:41 ` Jassi Brar
2010-09-26 10:49 ` Kyungmin Park
2010-09-27 0:20 ` Mark Brown
2010-09-27 2:01 ` Kyungmin Park
2010-09-27 5:41 ` Mark Brown [this message]
2010-09-27 2:23 ` Jassi Brar
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=20100927054149.GA13056@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=cw00.choi@samsung.com \
--cc=jassi.brar@samsung.com \
--cc=jassisinghbrar@gmail.com \
--cc=kmpark@infradead.org \
--cc=lrg@slimlogic.co.uk \
/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.