From: Fabio Estevam <fabio.estevam@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] MX5: Make the weim structure complete
Date: Tue, 17 May 2011 09:58:28 -0300 [thread overview]
Message-ID: <4DD270F4.90204@freescale.com> (raw)
In-Reply-To: <4DD26DCA.606@denx.de>
Hi Stefano,
On 5/17/2011 9:44 AM, Stefano Babic wrote:
> On 05/17/2011 07:06 AM, Jason Liu wrote:
>> Hi, Fabio,
>>
>> 2011/5/17 Fabio Estevam <fabio.estevam@freescale.com>:
>>> Make the weim register set complete for MX51/MX53.
>>>
>>> While at it also add the weim chip select 1 address definition.
>>>
>>
>> From the code, you just add the cs for mx53 not for mx51, so,
>> Had better specify you add the cs1 address definition for mx53,
>> otherwise, it will make confusion.
>
> Sure ? The structure is not protected by any CONFIG_MX5x switch, and at
> least one mx51 board uses it. The registers have the same layout for
> both processor. Why do you think is only for MX53 ?
I think what Jason mentions is the fact that I added:
#define CS1_BASE_ADDR 0xF4000000 and this was only for MX53 because it is protected by
"elif defined(CONFIG_MX53)"
I can add the CS1_BASE_ADDR for MX51 as well on my v3 series.
The weim layout registers are the same for MX51 and MX53.
Regards,
Fabi Estevam
next prev parent reply other threads:[~2011-05-17 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 22:29 [U-Boot] [PATCH v2 1/3] MX5: Make the weim structure complete Fabio Estevam
2011-05-16 22:29 ` [U-Boot] [PATCH v2 2/3] MX5: Add iomux structure Fabio Estevam
2011-05-16 22:29 ` [U-Boot] [PATCH v2 3/3] MX53: Add initial support for MX53ARD board Fabio Estevam
2011-05-17 4:43 ` Jason Liu
2011-05-17 13:10 ` Stefano Babic
2011-05-17 4:55 ` [U-Boot] [PATCH v2 2/3] MX5: Add iomux structure Jason Liu
2011-05-17 12:53 ` Stefano Babic
2011-05-17 5:06 ` [U-Boot] [PATCH v2 1/3] MX5: Make the weim structure complete Jason Liu
2011-05-17 12:44 ` Stefano Babic
2011-05-17 12:58 ` Fabio Estevam [this message]
2011-05-17 13:12 ` Stefano Babic
2011-05-17 12:42 ` 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=4DD270F4.90204@freescale.com \
--to=fabio.estevam@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