From: vikram186@gmail.com (Vikram Narayanan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/9] mtd: gpmi: simplify the setting DLL code
Date: Tue, 11 Sep 2012 23:38:16 +0530 [thread overview]
Message-ID: <504F7E10.8030406@gmail.com> (raw)
In-Reply-To: <1347344231-10295-7-git-send-email-b32955@freescale.com>
Hello Huang Shijie,
On 9/11/2012 11:47 AM, Huang Shijie wrote:
> The setting DLL code is a little mess.
> Just simplify the code and the comments.
>
> Signed-off-by: Huang Shijie<b32955@freescale.com>
> ---
> drivers/mtd/nand/gpmi-nand/gpmi-lib.c | 22 +++++++++-------------
> 1 files changed, 9 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-lib.c b/drivers/mtd/nand/gpmi-nand/gpmi-lib.c
> index 037438a..83c5573 100644
> --- a/drivers/mtd/nand/gpmi-nand/gpmi-lib.c
> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-lib.c
> @@ -779,30 +779,26 @@ void gpmi_begin(struct gpmi_nand_data *this)
> writel(BM_GPMI_CTRL1_DLL_ENABLE, gpmi_regs + HW_GPMI_CTRL1_CLR);
>
> /* Clear out the DLL control fields. */
> - writel(BM_GPMI_CTRL1_RDN_DELAY, gpmi_regs + HW_GPMI_CTRL1_CLR);
> - writel(BM_GPMI_CTRL1_HALF_PERIOD, gpmi_regs + HW_GPMI_CTRL1_CLR);
> + reg = BM_GPMI_CTRL1_RDN_DELAY | BM_GPMI_CTRL1_HALF_PERIOD;
> + writel(reg, gpmi_regs + HW_GPMI_CTRL1_CLR);
>
> /* If no sample delay is called for, return immediately. */
> if (!hw.sample_delay_factor)
> return;
>
> - /* Configure the HALF_PERIOD flag. */
> - if (hw.use_half_periods)
> - writel(BM_GPMI_CTRL1_HALF_PERIOD,
> - gpmi_regs + HW_GPMI_CTRL1_SET);
> + /* Set RDN_DELAY or HALF_PERIOD. */
> + reg = ((hw.use_half_periods) ? BM_GPMI_CTRL1_HALF_PERIOD : 0)
> + | BF_GPMI_CTRL1_RDN_DELAY(hw.sample_delay_factor);
>
> - /* Set the delay factor. */
> - writel(BF_GPMI_CTRL1_RDN_DELAY(hw.sample_delay_factor),
> - gpmi_regs + HW_GPMI_CTRL1_SET);
> + writel(reg, gpmi_regs + HW_GPMI_CTRL1_SET);
>
> - /* Enable the DLL. */
> + /* At last, we enable the DLL. */
> writel(BM_GPMI_CTRL1_DLL_ENABLE, gpmi_regs + HW_GPMI_CTRL1_SET);
>
> /*
> * After we enable the GPMI DLL, we have to wait 64 clock cycles before
> - * we can use the GPMI.
> - *
> - * Calculate the amount of time we need to wait, in microseconds.
> + * we can use the GPMI. Calculate the amount of time we need to wait,
> + * in microseconds.
> */
> clock_period_in_ns = 1000000000 / clk_get_rate(r->clock[0]);
NSEC_PER_SEC macro in the above statement?
Don't curse me for commenting about the code that you've not written. As
this patch does some cleanups, I'm suggesting this.
> dll_wait_time_in_us = (clock_period_in_ns * 64) / 1000;
Regards,
Vikram
next prev parent reply other threads:[~2012-09-11 18:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 6:17 [PATCH 0/9] add EDO feature for gpmi-nand driver Huang Shijie
2012-09-11 6:17 ` [PATCH 1/9] mtd: add helpers to set/get features for ONFI nand Huang Shijie
2012-09-11 6:17 ` [PATCH 2/9] mtd: add helpers to get the supportted ONFI timing mode Huang Shijie
2012-09-11 6:17 ` [PATCH 3/9] mtd: gpmi: add a new field for HW_GPMI_TIMING1 Huang Shijie
2012-09-11 18:00 ` Vikram Narayanan
2012-09-12 2:15 ` Huang Shijie
2012-09-11 6:17 ` [PATCH 4/9] mtd: gpmi: do not get the clock frequency in gpmi_begin() Huang Shijie
2012-09-11 6:17 ` [PATCH 5/9] mtd: gpmi: add a new field for HW_GPMI_CTRL1 Huang Shijie
2012-09-11 18:04 ` Vikram Narayanan
2012-09-12 2:18 ` Huang Shijie
2012-09-11 6:17 ` [PATCH 6/9] mtd: gpmi: simplify the setting DLL code Huang Shijie
2012-09-11 18:08 ` Vikram Narayanan [this message]
2012-09-12 2:28 ` Huang Shijie
2012-09-12 7:00 ` Huang Shijie
2012-09-11 6:17 ` [PATCH 7/9] mtd: gpmi: do not set the default values for the extra clocks Huang Shijie
2012-09-11 6:17 ` [PATCH 8/9] mtd: gpmi: add EDO feature for imx6q Huang Shijie
2012-09-11 6:17 ` [PATCH 9/9] mtd: gpmi: initialize the timing registers only one time Huang Shijie
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=504F7E10.8030406@gmail.com \
--to=vikram186@gmail.com \
--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).