From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Mike Turquette <mturquette@linaro.org>,
Stephen Warren <swarren@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
<linux-kernel@vger.kernel.org>
Subject: [REPOST PATCH 0/2] Table lookup for mux clock type
Date: Fri, 22 Feb 2013 17:02:27 +0200 [thread overview]
Message-ID: <1361545358-22721-1-git-send-email-pdeschrijver@nvidia.com> (raw)
This patchset adds a table lookup feature to the mux clock type. This will
be used by the forthcoming Tegra114 clock implementation. Also instead of
a fixed field width, a mask is used. This is because Tegra114 has some muxes
where the parent selector is spread over several bitfields. The second patch
adapts the tegra periph clock implementation which uses struct clk_mux
directly.
--
Mike,
This patch is a dependency for the Tegra114 CCF implementation. Could you
review it and merge on a topic branch so Stephen can pull it in to verify
the integration?
Thanks,
Peter.
Peter De Schrijver (2):
clk: add table lookup to mux
clk: tegra: adapt tegra periph clk to mux table/mask
drivers/clk/clk-mux.c | 51 ++++++++++++++++++++++++++++++++---------
drivers/clk/tegra/clk.h | 27 +++++++++++++++------
include/linux/clk-private.h | 3 +-
include/linux/clk-provider.h | 9 ++++++-
4 files changed, 69 insertions(+), 21 deletions(-)
--
1.7.7.rc0.72.g4b5ea.dirty
next reply other threads:[~2013-02-22 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 15:02 Peter De Schrijver [this message]
2013-02-22 15:02 ` [REPOST PATCH 1/2] clk: add table lookup to mux Peter De Schrijver
2013-02-27 6:32 ` Hiroshi Doyu
2013-02-22 15:02 ` [REPOST PATCH 2/2] clk: tegra: adapt tegra periph clk to mux table/mask Peter De Schrijver
2013-03-05 22:48 ` [REPOST PATCH 0/2] Table lookup for mux clock type Stephen Warren
2013-03-05 23:52 ` Stephen Warren
2013-03-06 7:52 ` Peter De Schrijver
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=1361545358-22721-1-git-send-email-pdeschrijver@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 \
--cc=mturquette@linaro.org \
--cc=pgaikwad@nvidia.com \
--cc=swarren@nvidia.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
all inboxes | Powered by JetHome®