From: k.kozlowski@samsung•com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/6] mfd: devicetree: bindings: 88pm800: Add DT property for 32KHz output enable
Date: Sat, 11 Jul 2015 16:11:52 +0900 [thread overview]
Message-ID: <55A0C1B8.4030402@samsung.com> (raw)
In-Reply-To: <1436442431-3471-4-git-send-email-vaibhav.hiremath@linaro.org>
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@linaro•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
>
next prev parent reply other threads:[~2015-07-11 7:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 11:47 [PATCH 0/6] mfd: 88pm800: Add 88pm860 device support Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 1/6] mfd: 88pm80x: Add 88pm860 chip type support Vaibhav Hiremath
2015-07-11 6:54 ` Krzysztof Kozlowski
2015-07-09 11:47 ` [PATCH 2/6] mfd: 88pm800: Add init time initial configuration support Vaibhav Hiremath
2015-07-11 6:53 ` Krzysztof Kozlowski
2015-07-13 7:10 ` Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 3/6] mfd: devicetree: bindings: 88pm800: Add DT property for 32KHz output enable Vaibhav Hiremath
2015-07-11 7:11 ` Krzysztof Kozlowski [this message]
2015-07-13 7:24 ` Vaibhav Hiremath
2015-07-13 7:31 ` Krzysztof Kozlowski
2015-07-13 7:38 ` Vaibhav Hiremath
2015-07-13 7:44 ` Krzysztof Kozlowski
2015-07-09 11:47 ` [PATCH 4/6] mfd: 88pm800: Enable 32KHZ XO low jitter clock out Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 5/6] mfd: devicetree: bindings: 88pm800: Add DT property for dual phase enable Vaibhav Hiremath
2015-07-11 7:16 ` Krzysztof Kozlowski
2015-07-13 7:50 ` Vaibhav Hiremath
2015-07-13 8:10 ` Krzysztof Kozlowski
2015-07-13 14:27 ` Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 6/6] mfd: 88pm800: Add support for configuration of dual phase on BUCK1 Vaibhav Hiremath
2015-07-09 12:04 ` [PATCH 0/6] mfd: 88pm800: Add 88pm860 device support Krzysztof Kozlowski
2015-07-09 12:44 ` Vaibhav Hiremath
2015-07-09 12:53 ` Vaibhav Hiremath
2015-07-09 13:28 ` Krzysztof Kozlowski
2015-07-10 12:03 ` Vaibhav Hiremath
2015-07-11 6:46 ` Krzysztof Kozlowski
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=55A0C1B8.4030402@samsung.com \
--to=k.kozlowski@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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