From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753845AbaESKZO (ORCPT ); Mon, 19 May 2014 06:25:14 -0400 Received: from mail-ee0-f44.google.com ([74.125.83.44]:37274 "EHLO mail-ee0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751621AbaESKZM (ORCPT ); Mon, 19 May 2014 06:25:12 -0400 Message-ID: <5379DBFE.4010000@gmail.com> Date: Mon, 19 May 2014 12:25:02 +0200 From: Tomasz Figa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Tushar Behera , Tomasz Figa , linux-samsung-soc@vger.kernel.org CC: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Mike Turquette , Kukjin Kim , Rob Herring , Mark Rutland , Marek Szyprowski , Pankaj Dubey , Rahul Sharma , Mark Brown Subject: Re: [PATCH RFC 3/4] clk: samsung: Add driver to control CLKOUT line on Exynos SoCs References: <1400175151-27779-1-git-send-email-t.figa@samsung.com> <1400175151-27779-4-git-send-email-t.figa@samsung.com> <5379AFB9.9030608@linaro.org> In-Reply-To: <5379AFB9.9030608@linaro.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tushar, On 19.05.2014 09:16, Tushar Behera wrote: > On 05/15/2014 11:02 PM, Tomasz Figa wrote: >> This patch introduces a driver that handles configuration of CLKOUT pin >> of Exynos SoCs that can be used to output certain clocks from inside of >> the SoC to a dedicated output pin. >> >> Signed-off-by: Tomasz Figa >> --- > > Tested the series on Exynos5420-based peach-pit board for audio playback > (with an internal patch to set CLK_FIN_PLL as the parent of clkout). > > Tested-by: Tushar Behera > Thank you for testing. >> Example : >> pmu_system_controller: system-controller@10040000 { >> compatible = "samsung,exynos5250-pmu", "syscon"; >> reg = <0x10040000 0x5000>; >> + #clock-cells = <0>; >> + clock-names = "clkout0", "clkout1", "clkout2", "clkout3", >> + "clkout4", "clkout8", "clkout9"; >> + clocks = <&clock CLK_OUT_DMC>, <&clock CLK_OUT_TOP>, >> + <&clock CLK_OUT_LEFTBUS>, <&clock CLK_OUT_RIGHTBUS>, >> + <&clock CLK_OUT_CPU>, <&clock CLK_XXTI>, >> + <&clock CLK_XUSBXTI>; >> }; > > Adding an usage example in the documentation would be helpful. Right, that's usually a good idea, I don't know why I haven't added one. Thanks. Best regards, Tomasz