From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH REPOST v2] clk: add table lookup to mux Date: Fri, 22 Mar 2013 14:42:06 -0600 Message-ID: <514CC21E.40206@wwwdotorg.org> References: <1363954078-29952-1-git-send-email-pdeschrijver@nvidia.com> <514C813E.1070603@wwwdotorg.org> <20130322202522.834.24639@quantum> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130322202522.834.24639@quantum> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Mike Turquette Cc: Peter De Schrijver , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Prashant Gaikwad , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-tegra@vger.kernel.org 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 >> >> Tested-by: Stephen Warren > > 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.