public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 8/8] mxs: prefix register acessor macros with 'mxs' prefix
Date: Sun, 13 May 2012 20:46:04 +0200	[thread overview]
Message-ID: <201205132046.04795.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKqD8+hFa+SbWYcDSAtB256ta6SJ_aWcsbtveUYH8jKJKw@mail.gmail.com>

Dear Otavio Salvador,

> On Sun, May 13, 2012 at 2:15 PM, Marek Vasut <marex@denx.de> wrote:
> >> As the register accessing mode is the same for all i.MXS SoCs we ought
> >> to use 'mxs' prefix intead of 'mx28'.
> > 
> > Are you _SURE_ the register offsets are the same on mx233 and mx28? For
> > example for DMA?
> 
> From what I read from mx23 datasheet it is.

From what I saw two days ago in the LAKML it isn't ... compare HW_APBH_CH0_SEMA 
for instance ;-) Check drivers/dma/mxs-dma.c in Linux for example.

Best regards,
Marek Vasut

  reply	other threads:[~2012-05-13 18:46 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12 23:40 [U-Boot] [PATCH 0/8] Minor fixes and start of consolidation onto mxs SoC Otavio Salvador
2012-05-12 23:40 ` [U-Boot] [PATCH 1/8] m28evk: use same notation to alloc the 128kB stack Otavio Salvador
2012-05-29 20:44   ` Wolfgang Denk
2012-06-13  9:06   ` Stefano Babic
2012-05-12 23:40 ` [U-Boot] [PATCH 2/8] m28evk: use "M28EVK U-Boot =>" as prompt Otavio Salvador
2012-05-13 17:11   ` Marek Vasut
2012-05-29 20:41   ` Wolfgang Denk
2012-05-12 23:40 ` [U-Boot] [PATCH 3/8] mx28evk: ensure command definition is in alphabetic order Otavio Salvador
2012-05-13 19:29   ` Fabio Estevam
2012-06-13  9:06   ` Stefano Babic
2012-05-12 23:40 ` [U-Boot] [PATCH 4/8] mxsboot: stop referring to i.MX28 as this ought to work for all i.MXS SoCs Otavio Salvador
2012-05-13 17:12   ` Marek Vasut
2012-05-13 18:19     ` Otavio Salvador
2012-05-29 20:44   ` Wolfgang Denk
2012-05-29 21:25     ` Otavio Salvador
2012-05-29 21:32       ` Wolfgang Denk
2012-05-29 21:53         ` Otavio Salvador
2012-05-30  5:49     ` Marek Vasut
2012-05-30 12:01       ` Otavio Salvador
2012-06-02  7:06       ` [U-Boot] mxsboot vs. imximage (was: Re: [PATCH 4/8] mxsboot: stop referring to i.MX28 as this ought to work for all i.MXS SoCs) Dirk Behme
2012-06-02  7:21         ` Marek Vasut
2012-05-12 23:40 ` [U-Boot] [PATCH 5/8] m28evk: fix board config include guardian macro name Otavio Salvador
2012-05-13 17:12   ` Marek Vasut
2012-05-13 18:46     ` Wolfgang Denk
2012-05-13 18:53       ` Marek Vasut
2012-06-13  9:07   ` Stefano Babic
2012-05-12 23:40 ` [U-Boot] [PATCH 6/8] mx28evk: " Otavio Salvador
2012-05-13 19:31   ` Fabio Estevam
2012-06-13  9:06   ` Stefano Babic
2012-05-12 23:40 ` [U-Boot] [PATCH 7/8] mxs: reorganize source directory for easy sharing of code in i.MXS SoCs Otavio Salvador
2012-05-12 23:40 ` [U-Boot] [PATCH 8/8] mxs: prefix register acessor macros with 'mxs' prefix Otavio Salvador
2012-05-13 17:15   ` Marek Vasut
2012-05-13 18:23     ` Otavio Salvador
2012-05-13 18:46       ` Marek Vasut [this message]
2012-05-14 17:09         ` Otavio Salvador
2012-05-14 18:25           ` Marek Vasut
2012-05-14 18:48   ` Otavio Salvador
2012-05-15  4:14     ` Marek Vasut
2012-05-29 20:47 ` [U-Boot] [PATCH 0/8] Minor fixes and start of consolidation onto mxs SoC Wolfgang Denk
2012-05-29 20:58   ` Otavio Salvador

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=201205132046.04795.marex@denx.de \
    --to=marex@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