From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Philipp Zabel <p.zabel@pengutronix.de>,
richard.leitner@skidata.com, srinivas.kandagatla@linaro.org,
axel.lin@ingics.com, ping.bai@nxp.com, d.schultz@phytec.de,
peng.fan@nxp.com, van.freenix@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 5/7] nvmem: imx-ocotp: Add i.MX7D timing write clock setup support
Date: Wed, 11 Oct 2017 17:22:51 +0100 [thread overview]
Message-ID: <308e3067-cc2c-d9a3-33e2-912a3302ceb7@nexus-software.ie> (raw)
In-Reply-To: <1507737805.22082.11.camel@pengutronix.de>
On 11/10/17 17:03, Philipp Zabel wrote:
> Would
>
> fsource = DIV_ROUND_UP_ULL((u64)clk_rate * DEF_FSOURCE,
> NSEC_PER_SEC) + 1;
> strobe_prog = DIV_ROUND_CLOSEST_ULL((u64)clk_rate * DEF_STROBE_PROG,
> NSEC_PER_SEC) + 1;
>
> work instead?
Might do, I'll see and change it if it works
next prev parent reply other threads:[~2017-10-11 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 14:11 [PATCH v3 0/7] Fix i.MX7D OCOTP write support Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 1/7] nvmem: imx-ocotp: Restrict OTP write to IMX6 processors Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 2/7] nvmem: imx-ocotp: Pass parameters via a struct Bryan O'Donoghue
2017-10-11 15:28 ` Philipp Zabel
2017-10-09 14:11 ` [PATCH v3 3/7] nvmem: imx-ocotp: Add support for banked OTP addressing Bryan O'Donoghue
2017-10-11 15:32 ` Philipp Zabel
2017-10-11 15:54 ` Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 4/7] nvmem: imx-ocotp: Move i.MX6 write clock setup to dedicated function Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 5/7] nvmem: imx-ocotp: Add i.MX7D timing write clock setup support Bryan O'Donoghue
2017-10-11 16:03 ` Philipp Zabel
2017-10-11 16:22 ` Bryan O'Donoghue [this message]
2017-10-09 14:11 ` [PATCH v3 6/7] nvmem: imx-ocotp: Enable i.MX7D OTP write support Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 7/7] nvmem: imx-ocotp: Update module description Bryan O'Donoghue
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=308e3067-cc2c-d9a3-33e2-912a3302ceb7@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=axel.lin@ingics.com \
--cc=d.schultz@phytec.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=peng.fan@nxp.com \
--cc=ping.bai@nxp.com \
--cc=richard.leitner@skidata.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=van.freenix@gmail.com \
/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
all inboxes | Powered by JetHome®