From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc4xx: Add CONFIG_DDR_RFDC_FIXED to allow board specific RFDC values
Date: Tue, 20 Jul 2010 07:01:47 +0200 [thread overview]
Message-ID: <201007200701.47949.sr@denx.de> (raw)
In-Reply-To: <20100719175408.AA138153A81@gemini.denx.de>
Hi Wolfgang,
On Monday 19 July 2010 19:54:08 Wolfgang Denk wrote:
> > @@ -767,6 +767,13 @@ static u32 DQS_calibration_methodB(struct ddrautocal
> > *cal)
> >
> > debug("\n\n");
> >
> > +#if defined(CONFIG_DDR_RFDC_FIXED)
> > + mtsdram(SDRAM_RFDC, CONFIG_DDR_RFDC_FIXED);
> > + size = 512;
> > + rffd_average = CONFIG_DDR_RFDC_FIXED & SDRAM_RFDC_RFFD_MASK;
> > + mfsdram(SDRAM_RDCC, rdcc); /* record this value */
> > + cal->rdcc = rdcc;
> > +#else
> >
> > in_window = 0;
> > rdcc = 0;
> >
> > @@ -830,6 +837,7 @@ static u32 DQS_calibration_methodB(struct ddrautocal
> > *cal)
> >
> > rffd_average = SDRAM_RFDC_RFFD_MAX;
> >
> > mtsdram(SDRAM_RFDC, rfdc_reg | SDRAM_RFDC_RFFD_ENCODE(rffd_average));
> >
> > +#endif
>
> In cases of such long blocks, where the ending #endif is many, many
> lines away, it is usually helpful to mark where the #endif belongs to:
>
> #endif /* CONFIG_DDR_RFDC_FIXED */
>
> Please do this here, too.
Yes, good idea. Thanks.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
prev parent reply other threads:[~2010-07-20 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 12:24 [U-Boot] [PATCH] ppc4xx: Add CONFIG_DDR_RFDC_FIXED to allow board specific RFDC values Stefan Roese
2010-07-19 17:54 ` Wolfgang Denk
2010-07-20 5:01 ` Stefan Roese [this message]
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=201007200701.47949.sr@denx.de \
--to=sr@denx.de \
--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 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.