From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH REPOST v2] clk: add table lookup to mux
Date: Fri, 22 Mar 2013 15:25:39 -0700 [thread overview]
Message-ID: <20130322222539.834.66626@quantum> (raw)
In-Reply-To: <514CC21E.40206@wwwdotorg.org>
Quoting Stephen Warren (2013-03-22 13:42:06)
> On 03/22/2013 02:25 PM, Mike Turquette wrote:
> > Quoting Stephen Warren (2013-03-22 09:05:18)
> >> On 03/22/2013 06:07 AM, Peter De Schrijver wrote:
> >>> Add a table lookup feature to the mux clock. Also allow arbitrary masks
> >>> instead of the width. This will be used by some clocks on Tegra114. Also
> >>> adapt the tegra periph clk because it uses struct clk_mux directly.
> >>>
> >>> Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> >>
> >> Tested-by: Stephen Warren <swarren@nvidia.com>
> >
> > Thanks for the patch. Taken into clk-next.
>
> Great. Recall this is a dependency for the Tegra114 clock series that I
> was planning on taking through the Tegra tree. Should I just merge your
> whole clk-next into the Tegra tree as a basis for the Tegra114 clock
> branch, or should this one patch be put into a separate topic branch so
> I don't pick up everything? The latter would reduce the
> inter-dependencies, and allow the merge to happen earlier. Obviously,
> I'll wait until you let me know the appropriate branch is stable before
> doing the merge. Thanks.
I want to get a little more exposure in linux-next before I create a
branch named clk-for-3.10 will never be rebased. Assuming there are no
issues then probably the middle of next week I will push commit ce4f3313
and it will be considered immutable.
As always the tip of clk-next might be rebased, but never past the top
commit in the clk-for-x.y commit, which is frozen.
Regards,
Mike
prev parent reply other threads:[~2013-03-22 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 12:07 [PATCH REPOST v2] clk: add table lookup to mux Peter De Schrijver
2013-03-22 12:15 ` Peter De Schrijver
2013-03-22 16:05 ` Stephen Warren
2013-03-22 20:25 ` Mike Turquette
2013-03-22 20:42 ` Stephen Warren
2013-03-22 22:25 ` Mike Turquette [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=20130322222539.834.66626@quantum \
--to=mturquette@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).