From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2]ppc4xx/Canyonlands added USB board callbacks
Date: Wed, 7 Jul 2010 13:05:11 +0200 [thread overview]
Message-ID: <201007071305.11262.sr@denx.de> (raw)
In-Reply-To: <201007071049.o67An6AJ005053@amcc.com>
Hi Rup,
On Wednesday 07 July 2010 12:49:06 Rupjyoti Sarmah wrote:
> Functions added to support board callbacks for USB init. This
> isolates USB manipulations such that it is only touched if USB is
> used by U-Boot.
Thanks. Looks quite good now. Please find a small comment below.
<snip>
> diff --git a/include/configs/canyonlands.h b/include/configs/canyonlands.h
> index ac9b3c5..0eee522 100644
> --- a/include/configs/canyonlands.h
> +++ b/include/configs/canyonlands.h
> @@ -77,6 +77,18 @@
> #define CONFIG_SYS_PCIE0_XCFGBASE 0xc3000000
> #define CONFIG_SYS_PCIE1_XCFGBASE 0xc3001000
>
> +/*
> + * BCSR bits as defined in the Canyonlands board user manual.
> + */
> +#define BCSR_CPLDREV 0x00
> +#define BCSR_BRDSTS 0x03
> +#define BCSR_FLASHCTRL 0x05
> +#define BCSR_ETHCTRL 0x06
> +#define BCSR_USBCTRL 0x07
> +#define BCSR_USBCTRL_OTG_RST 0x32
> +#define BCSR_USBCTRL_HOST_RST 0x01
> +#define CONFIG_SYS_BCSR3_PCIE 0x10
> +
Hmmm. Which of these defines are really bits and which are offsets for
registers? You can remove the register offsets defines, since you're using the
struct now. And please use consistent naming, and don't name one bit
"CONFIG_SYS_BCSRxxx".
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
next prev parent reply other threads:[~2010-07-07 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 10:49 [U-Boot] [PATCH v2]ppc4xx/Canyonlands added USB board callbacks Rupjyoti Sarmah
2010-07-07 11:05 ` Stefan Roese [this message]
2010-07-07 12:35 ` Rupjyoti Sarmah
2010-07-07 11:13 ` Felix Radensky
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=201007071305.11262.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox