[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55A0C1B8.4030402@samsung.com>
Date: Sat, 11 Jul 2015 16:11:52 +0900
From: Krzysztof Kozlowski <k.kozlowski@...sung.com>
To: Vaibhav Hiremath <vaibhav.hiremath@...aro.org>,
linux-arm-kernel@...ts.infradead.org
CC: devicetree@...r.kernel.org, sameo@...ux.intel.com,
linux-kernel@...r.kernel.org, robh+dt@...nel.org,
lee.jones@...aro.org
Subject: Re: [PATCH 3/6] mfd: devicetree: bindings: 88pm800: Add DT property
for 32KHz output enable
W dniu 09.07.2015 o 20:47, Vaibhav Hiremath pisze:
> 88PM800 family of device supports output of 32KHz clock (low jitter)
> on CLK32K2/3 pin which can be supplied to other peripherals on the board.
>
> This patch adds the devicetree binding to enable this feature.
>
> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@...aro.org>
> ---
> Documentation/devicetree/bindings/mfd/88pm800.txt | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/88pm800.txt b/Documentation/devicetree/bindings/mfd/88pm800.txt
> index dec842f..ae1311c 100644
> --- a/Documentation/devicetree/bindings/mfd/88pm800.txt
> +++ b/Documentation/devicetree/bindings/mfd/88pm800.txt
> @@ -9,6 +9,12 @@ Required parent device properties:
> - #interrupt-cells : should be 1.
> The cell is the 88pm80x local IRQ number
>
> +Optional properties :
> + - marvell,88pm800-32khz-xolj-out-en : If set, driver will enable low jitter
> + version of 32Khz clock output on
I am not sure if I understand it correctly. The hardware always has such
clocks and you only want to enable/disable it in DT? Any reasons why
these should not be enabled always?
Enabling it in DT does not look like a job for DT. Maybe you there
should be just a clock driver (clock provider)?
Best regards,
Krzysztof
> + CLK32K3 - for 88pm800
> + CLK32K2 - for 88pm860
> +
> 88pm80x family of devices consists of varied group of sub-devices:
>
> Device Supply Names Description
>
--
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