From: Shawn Guo <shawnguo@kernel.org>
To: Sanchayan Maity <maitysanchayan@gmail.com>
Cc: srinivas.kandagatla@linaro.org, gregkh@linuxfoundation.org,
maxime.ripard@free-electrons.com, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stefan@agner.ch,
kernel@pengutronix.de
Subject: Re: [PATCH v10 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller
Date: Tue, 22 Sep 2015 17:31:14 -0700 [thread overview]
Message-ID: <20150923003114.GB3529@tiger> (raw)
In-Reply-To: <ca85ab571ba312ea75a4d33543e5dbb8745e7190.1441609625.git.maitysanchayan@gmail.com>
On Mon, Sep 07, 2015 at 01:51:35PM +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>
Applied this one, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller
Date: Tue, 22 Sep 2015 17:31:14 -0700 [thread overview]
Message-ID: <20150923003114.GB3529@tiger> (raw)
In-Reply-To: <ca85ab571ba312ea75a4d33543e5dbb8745e7190.1441609625.git.maitysanchayan@gmail.com>
On Mon, Sep 07, 2015 at 01:51:35PM +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>
Applied this one, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Sanchayan Maity <maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stefan-XLVq0VzYD2Y@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org
Subject: Re: [PATCH v10 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller
Date: Tue, 22 Sep 2015 17:31:14 -0700 [thread overview]
Message-ID: <20150923003114.GB3529@tiger> (raw)
In-Reply-To: <ca85ab571ba312ea75a4d33543e5dbb8745e7190.1441609625.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Mon, Sep 07, 2015 at 01:51:35PM +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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Applied this one, thanks.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-09-23 0:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 8:21 [PATCH v10 0/4] Implement OCOTP driver for Vybrid using NVMEM Sanchayan Maity
2015-09-07 8:21 ` Sanchayan Maity
2015-09-07 8:21 ` [PATCH v10 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller Sanchayan Maity
2015-09-07 8:21 ` Sanchayan Maity
2015-09-23 0:31 ` Shawn Guo [this message]
2015-09-23 0:31 ` Shawn Guo
2015-09-23 0:31 ` Shawn Guo
2015-09-07 8:21 ` [PATCH v10 2/4] ARM: dts: vfxxx: Add OCOTP node Sanchayan Maity
2015-09-07 8:21 ` Sanchayan Maity
2015-09-07 8:21 ` Sanchayan Maity
2015-09-07 8:21 ` [PATCH v10 3/4] drivers: nvmem: Add Vybrid OCOTP support Sanchayan Maity
2015-09-07 8:21 ` Sanchayan Maity
2015-09-07 8:21 ` [PATCH v10 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver Sanchayan Maity
2015-09-07 8:21 ` Sanchayan Maity
2015-09-07 8:21 ` Sanchayan Maity
2015-09-21 6:19 ` [PATCH v10 0/4] Implement OCOTP driver for Vybrid using NVMEM maitysanchayan
2015-09-21 6:19 ` maitysanchayan at gmail.com
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=20150923003114.GB3529@tiger \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=maxime.ripard@free-electrons.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stefan@agner.ch \
/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.