public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-BOOT][PATCH 3/5] MX53: Add pin and multiplexer	definitions.
Date: Fri, 18 Jun 2010 11:48:09 +0200	[thread overview]
Message-ID: <4C1B40D9.90402@denx.de> (raw)
In-Reply-To: <12768745702681-git-send-email-r64343@freescale.com>

Jason Liu wrote:
> The patch add header files to support the pin multiplexer
> of the the Freescale i.MX53 processor.
> 
> Signed-off-by:Jason Liu <r64343@freescale.com>

Hi Jason,

> ---
>  arch/arm/include/asm/arch-mx53/iomux.h     |  193 +++++++++++++++
>  arch/arm/include/asm/arch-mx53/mx53_pins.h |  359 ++++++++++++++++++++++++++++
>  2 files changed, 552 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/include/asm/arch-mx53/iomux.h b/arch/arm/include/asm/arch-mx53/iomux.h

As I said for the previous patches, we must avoid to duplicate files.
This file must be merged with mx51 counterpart. As I see, the two files
have small differences.



> diff --git a/arch/arm/include/asm/arch-mx53/mx53_pins.h b/arch/arm/include/asm/arch-mx53/mx53_pins.h
> new file mode 100644

Definitions for mx53 are different as for mx51, so probably it is not
possible to merge them in a single structure. But we can have a single
file (mx5_pins.h, maybe ?), using #ifdef to set the different pins.

> +enum iomux_pins {
> +	MX53_PIN_GPIO_19  	= _MXC_BUILD_GPIO_PIN(3, 5, 1, 0x20, 0x348),
> +	MX53_PIN_KEY_COL0 	= _MXC_BUILD_GPIO_PIN(3, 6, 1, 0x24, 0x34C),

I think the best way should be to get rid of the cpu related names, and
use a more general approach. For exammple, we have MX51_PIN_KEY_COL0
defined for the MX51. It should be better to have for example
MX5_PIN_KEY_COL0,  whose value is different if our target is a MX51 or MX53.

What do you think ?

Best regards,
Stefano Babic

-- 
=====================================================================
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
=====================================================================

  reply	other threads:[~2010-06-18  9:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 15:22 [U-Boot] [U-BOOT][PATCH 1/5] MX53: Add initial support for the Freescale MX53 Jason Liu
2010-06-18  9:23 ` Stefano Babic
2010-06-18  9:50   ` Liu Hui-R64343
     [not found]   ` <AANLkTim8Xh0VrGc6lIm67lHgcS3PDTJzxB39R819j7GU@mail.gmail.com>
2010-06-23 14:03     ` Stefano Babic
2010-06-18 15:22 ` [U-Boot] [U-BOOT][PATCH 2/5] MX53: Add register definitions Jason Liu
2010-06-18  9:35   ` Stefano Babic
2010-06-18 15:22 ` [U-Boot] [U-BOOT][PATCH 3/5] MX53: Add pin and multiplexer definitions Jason Liu
2010-06-18  9:48   ` Stefano Babic [this message]
2010-06-18  9:54     ` Liu Hui-R64343
2010-06-18 15:22 ` [U-Boot] [U-BOOT][PATCH 4/5] serial_mxc: add support for MX53 processor Jason Liu
2010-06-18  9:52   ` Stefano Babic
2010-06-18  9:55     ` Liu Hui-R64343
2010-06-18 15:22 ` [U-Boot] [U-BOOT][PATCH 5/5] Add initial support for Freescale mx53evk board Jason Liu
2010-06-18  9:45   ` Wolfgang Denk
2010-06-18 10:31   ` 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=4C1B40D9.90402@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox