All of lore.kernel.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3] ARM: imx: add support code for IMX50 based machines
Date: Mon, 4 Nov 2013 09:51:51 -0500	[thread overview]
Message-ID: <20131104145151.GD3060@titan.lakedaemon.net> (raw)
In-Reply-To: <1383524020-1518-1-git-send-email-gerg@uclinux.org>

Greg,

On Mon, Nov 04, 2013 at 10:13:40AM +1000, gerg at uclinux.org wrote:
> From: Greg Ungerer <gerg@uclinux.org>
> 
> Add machine support code for the Freescale IMX50 SoC.
> 
> The IMX50 is quite similar to the Freescale IMX53, and contains many of the
> same periperhal hardware modules, at the same address offsets as the IMX53.
> (Notable exceptions are that the IMX50 contains no CAN bus hardware, less
> GPIO, no VPU, it does contain an Electrophoretic display controller though).
> 
> This support code uses some of the IMX53 setup code to reduce duplication
> of what would be identical init IO setup.
> 
> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
> ---
>  arch/arm/mach-imx/Makefile     |  1 +
>  arch/arm/mach-imx/common.h     |  1 +
>  arch/arm/mach-imx/mach-imx50.c | 36 ++++++++++++++++++++++++++++++++++++
>  3 files changed, 38 insertions(+)
>  create mode 100644 arch/arm/mach-imx/mach-imx50.c

What happened to the rest of the series?  If this is a new version of
just a single patch in the V2 series (which I suspect it is), we usually
make it an in-reply-to the previous version of the patch it replaces.
Not a big deal, it just helps us keep track of things more easily.

thx,

Jason.

  parent reply	other threads:[~2013-11-04 14:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  0:13 [PATCHv3] ARM: imx: add support code for IMX50 based machines gerg at uclinux.org
2013-11-04  3:16 ` Rob Herring
2013-11-04 13:08   ` Shawn Guo
2013-11-04 14:51 ` Jason Cooper [this message]
2013-11-04 14:57   ` Jason Cooper
2013-11-05  3:02     ` Greg Ungerer
2013-11-05  3:13       ` Shawn Guo
2013-11-05 15:57       ` Jason Cooper
2013-11-06  0:50         ` Greg Ungerer
2013-11-05  1:24 ` Shawn Guo
2013-11-05  2:56   ` Greg Ungerer

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=20131104145151.GD3060@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.