public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kmp204x: set the ZL clk chips reset to power up only
Date: Tue, 12 Aug 2014 10:54:44 -0700	[thread overview]
Message-ID: <53EA54E4.7060403@freescale.com> (raw)
In-Reply-To: <1405599732-11273-1-git-send-email-valentin.longchamp@keymile.com>

On 07/17/2014 05:22 AM, Valentin Longchamp wrote:
> There is the requirement on the chassis's backplane that when the clocks
> are enabled, they should not disappear. Resetting theses chips at unit

I guess here "they" means the "clocks".

> reset also has the side effect that their clocks disappear.

What does "their" point to? Whose clocks?

> 
> To avoid this side effect, both the ZL chips are reset only in the event
> of a power cycle.
> 

Do you mean "power up" here?

I suggest you rephrase your commit message. It sounds twisting.

> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
> ---
> 
>  board/keymile/kmp204x/kmp204x.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/board/keymile/kmp204x/kmp204x.c b/board/keymile/kmp204x/kmp204x.c
> index 6bc8eb8..638b2a3 100644
> --- a/board/keymile/kmp204x/kmp204x.c
> +++ b/board/keymile/kmp204x/kmp204x.c
> @@ -94,7 +94,7 @@ int board_early_init_f(void)
>  	qrio_wdmask(BFTIC4_RST, true);
>  
>  	/* set the ZL30138's prstcfg to reset at power-up and unit reset only */
> -	qrio_prstcfg(ZL30158_RST, PRSTCFG_POWUP_UNIT_RST);
> +	qrio_prstcfg(ZL30158_RST, PRSTCFG_POWUP_RST);
>  	/* and take it out of reset as soon as possible (needed for Hooper) */
>  	qrio_prst(ZL30158_RST, false, false);
>  
> @@ -144,7 +144,7 @@ int misc_init_f(void)
>  	qrio_prst(ETH_FRONT_PHY_RST, false, false);
>  
>  	/* set the ZL30343 prstcfg to reset at power-up and unit reset only */
> -	qrio_prstcfg(ZL30343_RST, PRSTCFG_POWUP_UNIT_RST);
> +	qrio_prstcfg(ZL30343_RST, PRSTCFG_POWUP_RST);
>  	/* and enable the WD on it */
>  	qrio_wdmask(ZL30343_RST, true);

You changed the macros here but not the comments.

York

  reply	other threads:[~2014-08-12 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 12:22 [U-Boot] [PATCH] kmp204x: set the ZL clk chips reset to power up only Valentin Longchamp
2014-08-12 17:54 ` York Sun [this message]
2014-08-13  6:15   ` Valentin Longchamp
2014-08-13  8:17 ` [U-Boot] [PATCH v2] kmp204x: reset the Zarlink clocking chips at " Valentin Longchamp
2014-08-13 16:51   ` York Sun
2014-08-19 13:33     ` Valentin Longchamp
2014-08-19 13:40     ` [U-Boot] [PATCH v3] " Valentin Longchamp
2014-08-20 19:41       ` York Sun

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=53EA54E4.7060403@freescale.com \
    --to=yorksun@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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