[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <537DD1D2.9010107@samsung.com>
Date: Thu, 22 May 2014 12:30:42 +0200
From: Tomasz Figa <t.figa@...sung.com>
To: Tushar Behera <tushar.behera@...aro.org>,
linux-samsung-soc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Mike Turquette <mturquette@...aro.org>,
Kukjin Kim <kgene.kim@...sung.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Pankaj Dubey <pankaj.dubey@...sung.com>,
Rahul Sharma <rahul.sharma@...sung.com>,
Mark Brown <broonie@...nel.org>,
Tomasz Figa <tomasz.figa@...il.com>
Subject: Re: [PATCH 3/4] clk: samsung: Add driver to control CLKOUT line on
Exynos SoCs
On 22.05.2014 06:28, Tushar Behera wrote:
> On 05/20/2014 10:13 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 <t.figa@...sung.com>
>> ---
>> .../devicetree/bindings/arm/samsung/pmu.txt | 30 ++++
>> drivers/clk/samsung/Makefile | 1 +
>> drivers/clk/samsung/clk-exynos-clkout.c | 153 +++++++++++++++++++++
>> 3 files changed, 184 insertions(+)
>> create mode 100644 drivers/clk/samsung/clk-exynos-clkout.c
>>
>> diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
>> index b562634..5ed94a9 100644
>> --- a/Documentation/devicetree/bindings/arm/samsung/pmu.txt
>> +++ b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
>> @@ -11,8 +11,38 @@ Properties:
>>
>> - reg : offset and length of the register set.
>>
>> + - #clock-cells : must be <1>, since PMU requires once cell as clock specifier.
>
> s/once/one
>
>> + The single specifier cell is used as index to list of clocks
>> + provided by PMU, which is currently:
>> + 0 : SoC clock output (CLKOUT pin)
>
> Will it make more sense if we add a macro for this clock number that
> would be referred in the device tree files?
Right now, with just one clock, it doesn't make sense, but if further
clocks show up with newer SoCs, then macros will have to be added.
Best regards,
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists