From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller
Date: Sun, 6 Sep 2015 16:15:26 +0800 [thread overview]
Message-ID: <20150906081526.GL30746@tiger> (raw)
In-Reply-To: <e38870196e689bd4edcaf43f36df899d63a6851c.1439384645.git.maitysanchayan@gmail.com>
On Wed, Aug 12, 2015 at 06:49:18PM +0530, Sanchayan Maity wrote:
> Add clock support for Vybrid On-Chip One Time Programmable
> (OCOTP) controller.
>
> While the OCOTP block does not require explicit clock gating,
> for programming the OCOTP timing register the clock rate of
> ipg clock is required for timing calculations related to fuse
> and shadow register read sequence. We explicitly specify the
> ipg clock for OCOTP as a result.
>
> Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> ---
> drivers/clk/imx/clk-vf610.c | 1 +
> include/dt-bindings/clock/vf610-clock.h | 3 ++-
> 2 files changed, 3 insertions(+), 1 deletion(-)
Please copy linux-clk list and clock maintainers on i.MX clock patches
as well. If you run ./scripts/get_maintainer.pl on the patch, you will
get them.
Shawn
>
> diff --git a/drivers/clk/imx/clk-vf610.c b/drivers/clk/imx/clk-vf610.c
> index bff45ea..d1b1c95 100644
> --- a/drivers/clk/imx/clk-vf610.c
> +++ b/drivers/clk/imx/clk-vf610.c
> @@ -387,6 +387,7 @@ static void __init vf610_clocks_init(struct device_node *ccm_node)
>
> clk[VF610_CLK_SNVS] = imx_clk_gate2("snvs-rtc", "ipg_bus", CCM_CCGR6, CCM_CCGRx_CGn(7));
> clk[VF610_CLK_DAP] = imx_clk_gate("dap", "platform_bus", CCM_CCSR, 24);
> + clk[VF610_CLK_OCOTP] = imx_clk_gate("ocotp", "ipg_bus", CCM_CCGR6, CCM_CCGRx_CGn(5));
>
> imx_check_clocks(clk, ARRAY_SIZE(clk));
>
> diff --git a/include/dt-bindings/clock/vf610-clock.h b/include/dt-bindings/clock/vf610-clock.h
> index d197634..56c16aa 100644
> --- a/include/dt-bindings/clock/vf610-clock.h
> +++ b/include/dt-bindings/clock/vf610-clock.h
> @@ -194,6 +194,7 @@
> #define VF610_PLL7_BYPASS 181
> #define VF610_CLK_SNVS 182
> #define VF610_CLK_DAP 183
> -#define VF610_CLK_END 184
> +#define VF610_CLK_OCOTP 184
> +#define VF610_CLK_END 185
>
> #endif /* __DT_BINDINGS_CLOCK_VF610_H */
> --
> 2.5.0
>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Sanchayan Maity <maitysanchayan@gmail.com>
Cc: gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
maxime.ripard@free-electrons.com,
linux-arm-kernel@lists.infradead.org, stefan@agner.ch,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller
Date: Sun, 6 Sep 2015 16:15:26 +0800 [thread overview]
Message-ID: <20150906081526.GL30746@tiger> (raw)
In-Reply-To: <e38870196e689bd4edcaf43f36df899d63a6851c.1439384645.git.maitysanchayan@gmail.com>
On Wed, Aug 12, 2015 at 06:49:18PM +0530, Sanchayan Maity wrote:
> Add clock support for Vybrid On-Chip One Time Programmable
> (OCOTP) controller.
>
> While the OCOTP block does not require explicit clock gating,
> for programming the OCOTP timing register the clock rate of
> ipg clock is required for timing calculations related to fuse
> and shadow register read sequence. We explicitly specify the
> ipg clock for OCOTP as a result.
>
> Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> ---
> drivers/clk/imx/clk-vf610.c | 1 +
> include/dt-bindings/clock/vf610-clock.h | 3 ++-
> 2 files changed, 3 insertions(+), 1 deletion(-)
Please copy linux-clk list and clock maintainers on i.MX clock patches
as well. If you run ./scripts/get_maintainer.pl on the patch, you will
get them.
Shawn
>
> diff --git a/drivers/clk/imx/clk-vf610.c b/drivers/clk/imx/clk-vf610.c
> index bff45ea..d1b1c95 100644
> --- a/drivers/clk/imx/clk-vf610.c
> +++ b/drivers/clk/imx/clk-vf610.c
> @@ -387,6 +387,7 @@ static void __init vf610_clocks_init(struct device_node *ccm_node)
>
> clk[VF610_CLK_SNVS] = imx_clk_gate2("snvs-rtc", "ipg_bus", CCM_CCGR6, CCM_CCGRx_CGn(7));
> clk[VF610_CLK_DAP] = imx_clk_gate("dap", "platform_bus", CCM_CCSR, 24);
> + clk[VF610_CLK_OCOTP] = imx_clk_gate("ocotp", "ipg_bus", CCM_CCGR6, CCM_CCGRx_CGn(5));
>
> imx_check_clocks(clk, ARRAY_SIZE(clk));
>
> diff --git a/include/dt-bindings/clock/vf610-clock.h b/include/dt-bindings/clock/vf610-clock.h
> index d197634..56c16aa 100644
> --- a/include/dt-bindings/clock/vf610-clock.h
> +++ b/include/dt-bindings/clock/vf610-clock.h
> @@ -194,6 +194,7 @@
> #define VF610_PLL7_BYPASS 181
> #define VF610_CLK_SNVS 182
> #define VF610_CLK_DAP 183
> -#define VF610_CLK_END 184
> +#define VF610_CLK_OCOTP 184
> +#define VF610_CLK_END 185
>
> #endif /* __DT_BINDINGS_CLOCK_VF610_H */
> --
> 2.5.0
>
next prev parent reply other threads:[~2015-09-06 8:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 13:19 [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-08-12 13:19 ` [PATCH v9 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-09-06 8:15 ` Shawn Guo [this message]
2015-09-06 8:15 ` Shawn Guo
2015-09-06 10:28 ` maitysanchayan at gmail.com
2015-09-06 10:28 ` maitysanchayan
2015-08-12 13:19 ` [PATCH v9 2/4] ARM: dts: vfxxx: Add OCOTP node Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-08-12 13:19 ` [PATCH v9 3/4] drivers: nvmem: Add Vybrid OCOTP support Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-08-12 13:19 ` [PATCH v9 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-09-06 8:13 ` Shawn Guo
2015-09-06 8:13 ` Shawn Guo
2015-09-06 10:28 ` maitysanchayan at gmail.com
2015-09-06 10:28 ` maitysanchayan
2015-08-24 8:32 ` [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM maitysanchayan at gmail.com
2015-08-24 8:32 ` maitysanchayan
2015-09-04 5:50 ` maitysanchayan at gmail.com
2015-09-04 5:50 ` maitysanchayan
2015-09-04 8:21 ` Srinivas Kandagatla
2015-09-04 8:21 ` Srinivas Kandagatla
2015-09-04 8:21 ` maitysanchayan at gmail.com
2015-09-04 8:21 ` maitysanchayan
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=20150906081526.GL30746@tiger \
--to=shawnguo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.