From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] SPI: added support for MX51 to mxc_spi
Date: Mon, 22 Mar 2010 11:25:44 +0100 [thread overview]
Message-ID: <4BA745A8.8010009@denx.de> (raw)
In-Reply-To: <4BA564F8.9070806@windriver.com>
Tom wrote:
>> +#define MXC_CSPIRXDATA 0x00
>> +#define MXC_CSPITXDATA 0x04
>> +#define MXC_CSPICTRL 0x08
>> +#define MXC_CSPIPERIOD_32KHZ (1 << 15)
>> +
>
> Pulling these out and making them common may not be the best thing to do.
> Located here, it hides the
>
> #ifdef CONFIG_MX27
> #elif defined (CONFIG_MX31)
> #elif defined (CONFIG_MX51)
> #else
> #endif
>
> I would prefer if you just kept the copies in the mx31, mx51 locations
You are right - I will move them.
>
> In 'Add SPI support to mx51evk board'
> The MAX_SPI_BYTES was defined in the config file.
> Here it is defined for mx31 generally.
> You should be consistent.
> These would be a better place for the mx51 values as you only have to do
> it once.
That is correct. And the value is not related to a particular board,
setting this define in config file is definetely wrong. I will move it.
> Be constistent with mx31
> Move the #includes to the first lines after the #elif
> The other #defines to follow.
Ok, thanks.
Stefano
--
=====================================================================
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-03-22 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 17:18 [U-Boot] [PATCH] SPI: add support for i.MX51 processor (mxc_spi) Stefano Babic
2010-03-16 16:21 ` [U-Boot] [PATCH] SPI: added support for MX51 to mxc_spi Stefano Babic
2010-03-21 0:14 ` Tom
2010-03-22 10:25 ` Stefano Babic [this message]
2010-03-23 9:01 ` Liu Hui-R64343
2010-03-24 9:56 ` Stefano Babic
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=4BA745A8.8010009@denx.de \
--to=sbabic@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.