From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] mfd: 88pm800: Update the header file with 32K clk related macros
Date: Thu, 23 Jul 2015 16:52:33 +0100 [thread overview]
Message-ID: <20150723155233.GT3436@x1> (raw)
In-Reply-To: <1437476823-3358-2-git-send-email-vaibhav.hiremath@linaro.org>
On Tue, 21 Jul 2015, Vaibhav Hiremath wrote:
> Update header file with required macros for 32KHz buffered clock
> output of 88PM800 family of device.
> These macros will be used in clk provider driver.
>
> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
> ---
> include/linux/mfd/88pm80x.h | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/include/linux/mfd/88pm80x.h b/include/linux/mfd/88pm80x.h
> index 05d9bad..680e4eb 100644
> --- a/include/linux/mfd/88pm80x.h
> +++ b/include/linux/mfd/88pm80x.h
> @@ -91,6 +91,7 @@ enum {
> /* Referance and low power registers */
> #define PM800_LOW_POWER1 (0x20)
> #define PM800_LOW_POWER2 (0x21)
> +#define PM800_LOW_POWER2_XO_LJ_EN BIT(5)
>
> #define PM800_LOW_POWER_CONFIG3 (0x22)
> #define PM800_LDOBK_FREEZE BIT(7)
> @@ -138,6 +139,13 @@ enum {
> #define PM800_ALARM BIT(5)
> #define PM800_RTC1_USE_XO BIT(7)
>
> +#define PM800_32K_OUTX_SEL_MASK (0x3)
> +/* 32KHz clk output sel mode */
> +#define PM800_32K_OUTX_SEL_ZERO (0x0)
> +#define PM800_32K_OUTX_SEL_INT_32KHZ (0x1)
> +#define PM800_32K_OUTX_SEL_XO_32KHZ (0x2)
> +#define PM800_32K_OUTX_SEL_HIZ (0x3)
Why do these need to be in brackets?
> /* Regulator Control Registers: BUCK1,BUCK5,LDO1 have DVC */
>
> /* buck registers */
> @@ -208,6 +216,10 @@ enum {
> #define PM800_PMOD_MEAS1 0x52
> #define PM800_PMOD_MEAS2 0x53
>
> +/* Oscillator control */
> +#define PM800_OSC_CNTRL1 (0x50)
> +#define PM800_OSC_CNTRL1_OSC_FREERUN_EN BIT(1)
> +
> #define PM800_GPADC0_MEAS1 0x54
> #define PM800_GPADC0_MEAS2 0x55
> #define PM800_GPADC1_MEAS1 0x56
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-07-23 15:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 11:06 [PATCH 0/4] clk: 88pm800: Add new clk provider driver for 88PM800 MFD Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 1/4] mfd: 88pm800: Update the header file with 32K clk related macros Vaibhav Hiremath
2015-07-23 15:52 ` Lee Jones [this message]
2015-08-05 8:53 ` Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 2/4] mfd: devicetree: bindings: Add clock subdevice node information Vaibhav Hiremath
2015-07-23 5:08 ` Krzysztof Kozlowski
2015-07-30 22:13 ` Stephen Boyd
2015-07-30 22:21 ` Rob Herring
2015-08-05 6:39 ` Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 3/4] clk: 88pm800: Add clk provider driver for 88pm800 family of devices Vaibhav Hiremath
2015-07-21 19:10 ` Stephen Boyd
2015-07-21 19:36 ` Vaibhav Hiremath
2015-07-21 20:52 ` Stephen Boyd
2015-07-22 6:27 ` Vaibhav Hiremath
2015-07-22 6:46 ` Krzysztof Kozlowski
2015-07-22 8:16 ` Vaibhav Hiremath
2015-07-22 22:03 ` Stephen Boyd
2015-07-21 11:07 ` [PATCH 4/4] mfd: 88pm800: Add support for clk subdevice Vaibhav Hiremath
2015-07-23 4:58 ` Krzysztof Kozlowski
2015-07-23 15:50 ` Lee Jones
2015-08-05 9:07 ` Vaibhav Hiremath
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=20150723155233.GT3436@x1 \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).