From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ulf Hansson <ulf.hansson@stericsson.com>
Cc: Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Linus Walleij <linus.walleij@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Ola Lilja <ola.o.lilja@stericsson.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH 2/2] ASoC: Ux500: Control apb clock
Date: Mon, 22 Oct 2012 14:32:00 +0100 [thread overview]
Message-ID: <20121022133200.GG4477@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1350909125-20189-2-git-send-email-ulf.hansson@stericsson.com>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
On Mon, Oct 22, 2012 at 02:32:05PM +0200, Ulf Hansson wrote:
> From: Ulf Hansson <ulf.hansson@linaro.org>
>
> When switching to common clock driver for ux500 this clock needs to
> be handled as well. Before this clock was internally managed by the
> clock driver itself.
Applied but why isn't this a deficiency in the common clock
implementation for the platform?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ASoC: Ux500: Control apb clock
Date: Mon, 22 Oct 2012 14:32:00 +0100 [thread overview]
Message-ID: <20121022133200.GG4477@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1350909125-20189-2-git-send-email-ulf.hansson@stericsson.com>
On Mon, Oct 22, 2012 at 02:32:05PM +0200, Ulf Hansson wrote:
> From: Ulf Hansson <ulf.hansson@linaro.org>
>
> When switching to common clock driver for ux500 this clock needs to
> be handled as well. Before this clock was internally managed by the
> clock driver itself.
Applied but why isn't this a deficiency in the common clock
implementation for the platform?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121022/fe94e73f/attachment-0001.sig>
next prev parent reply other threads:[~2012-10-22 13:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 12:32 [PATCH 1/2] ASoC: Ux500: Fixup use of clocks Ulf Hansson
2012-10-22 12:32 ` Ulf Hansson
2012-10-22 12:32 ` Ulf Hansson
2012-10-22 12:32 ` [PATCH 2/2] ASoC: Ux500: Control apb clock Ulf Hansson
2012-10-22 12:32 ` Ulf Hansson
2012-10-22 12:32 ` Ulf Hansson
2012-10-22 13:20 ` Linus Walleij
2012-10-22 13:20 ` Linus Walleij
2012-10-22 13:32 ` Mark Brown [this message]
2012-10-22 13:32 ` Mark Brown
2012-10-22 14:07 ` Ulf Hansson
2012-10-22 14:07 ` Ulf Hansson
2012-10-22 13:19 ` [PATCH 1/2] ASoC: Ux500: Fixup use of clocks Linus Walleij
2012-10-22 13:19 ` Linus Walleij
2012-10-22 13:30 ` Mark Brown
2012-10-22 13:30 ` Mark Brown
2012-11-05 14:27 ` Ulf Hansson
2012-11-05 14:27 ` Ulf Hansson
2012-11-06 8:26 ` Mark Brown
2012-11-06 8:26 ` Mark Brown
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=20121022133200.GG4477@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=ola.o.lilja@stericsson.com \
--cc=ulf.hansson@linaro.org \
--cc=ulf.hansson@stericsson.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.