From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: "open list:TEGRA SUPPORT" <linux-tegra@vger.kernel.org>,
"open list:ARM PORT" <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] Tegra30 clockframework
Date: Mon, 9 Jan 2012 17:26:03 +0200 [thread overview]
Message-ID: <20120109152603.GV32619@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <1326121937-32054-1-git-send-email-pdeschrijver@nvidia.com>
On Mon, Jan 09, 2012 at 04:12:10PM +0100, Peter De Schrijver wrote:
> This patchset introduces the tegra30 clockframework. Clocks which require
> voltage scaling are not included in this version. The implementation doesn't
> use the generic clock code yet. It's the intention to move to it, once the
> semantics are fully clarified.
>
> ---
>
> Changes in v2:
> * Fix parent clocks for TWD. This makes the SMP configuration booting again.
>
> Peter De Schrijver (3):
> ARM: tegra: add support for new clock framework features
> ARM: tegra: implement basic tegra30 clock framework
> ARM: tegra: enable tegra30 clock framework
Oops. Now I sent everything twice... Will send it again with the correct
topic etc.
Cheers,
Peter.
prev parent reply other threads:[~2012-01-09 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 15:12 Peter De Schrijver
2012-01-09 15:12 ` [PATCH v2 1/3] arm/tegra: add support for new clock framework features Peter De Schrijver
2012-01-09 15:12 ` [PATCH v2 1/3] ARM: tegra: " Peter De Schrijver
2012-01-09 15:12 ` [PATCH v2 2/3] ARM: tegra: implement basic tegra30 clock framework Peter De Schrijver
2012-01-09 15:12 ` [PATCH v2 3/3] arm/tegra: enable " Peter De Schrijver
2012-01-09 15:12 ` [PATCH v2 3/3] ARM: tegra: " Peter De Schrijver
2012-01-09 15:26 ` Peter De Schrijver [this message]
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=20120109152603.GV32619@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®