From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] clk: tegra: adapt tegra periph clk to mux table/mask
Date: Mon, 28 Jan 2013 09:49:53 -0700 [thread overview]
Message-ID: <5106AC31.1040207@wwwdotorg.org> (raw)
In-Reply-To: <1359388467-32386-3-git-send-email-pdeschrijver@nvidia.com>
On 01/28/2013 08:54 AM, Peter De Schrijver wrote:
> The tegra peripheral clock type uses struct clk_mux directly, so it needs to
> be updated to handle the new mask and table fields. Also the macros need
> to be updated
Just a quick note on patch dependencies here:
Patch 1/2 can presumably be taken through the clk tree whenever Mike is
OK with it.
Patch 2/2 depends on patches in the Tegra tree for 3.9. Since patch 2/2
is useful mostly for the Tegra114 clock driver, and I don't imagine that
will get posted/merged in time for 3.9, it's probably easiest to just
take patch 2/2 for 3.10 along with the Tegra114 clock driver. Also, I
imagine there won't be any more clk/Tegra tree dependencies in 3.10, so
patch 2/2 and the Tegra114 clk driver patches can likely go through the
clk tree itself for 3.10.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Mike Turquette <mturquette@linaro.org>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: tegra: adapt tegra periph clk to mux table/mask
Date: Mon, 28 Jan 2013 09:49:53 -0700 [thread overview]
Message-ID: <5106AC31.1040207@wwwdotorg.org> (raw)
In-Reply-To: <1359388467-32386-3-git-send-email-pdeschrijver@nvidia.com>
On 01/28/2013 08:54 AM, Peter De Schrijver wrote:
> The tegra peripheral clock type uses struct clk_mux directly, so it needs to
> be updated to handle the new mask and table fields. Also the macros need
> to be updated
Just a quick note on patch dependencies here:
Patch 1/2 can presumably be taken through the clk tree whenever Mike is
OK with it.
Patch 2/2 depends on patches in the Tegra tree for 3.9. Since patch 2/2
is useful mostly for the Tegra114 clock driver, and I don't imagine that
will get posted/merged in time for 3.9, it's probably easiest to just
take patch 2/2 for 3.10 along with the Tegra114 clock driver. Also, I
imagine there won't be any more clk/Tegra tree dependencies in 3.10, so
patch 2/2 and the Tegra114 clk driver patches can likely go through the
clk tree itself for 3.10.
next prev parent reply other threads:[~2013-01-28 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 15:54 [PATCH 0/2] Table lookup for mux clock type Peter De Schrijver
2013-01-28 15:54 ` Peter De Schrijver
2013-01-28 15:54 ` [PATCH 1/2] clk: add table lookup to mux Peter De Schrijver
2013-01-28 15:54 ` Peter De Schrijver
2013-01-28 15:54 ` [PATCH 2/2] clk: tegra: adapt tegra periph clk to mux table/mask Peter De Schrijver
2013-01-28 15:54 ` Peter De Schrijver
2013-01-28 16:49 ` Stephen Warren [this message]
2013-01-28 16:49 ` Stephen Warren
2013-01-29 9:51 ` Peter De Schrijver
2013-01-29 9:51 ` Peter De Schrijver
2013-01-29 16:38 ` Stephen Warren
2013-01-29 16:38 ` Stephen Warren
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=5106AC31.1040207@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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.