linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 13/15] ARM: mxs: Add initial mx23evk support
Date: Mon, 20 Dec 2010 18:17:10 +0800	[thread overview]
Message-ID: <20101220101709.GA16497@freescale.com> (raw)
In-Reply-To: <20101220094801.GU1940@pengutronix.de>

Hi Uwe,

On Mon, Dec 20, 2010 at 10:48:01AM +0100, Uwe Kleine-K?nig wrote:
> Hello Shawn,
> 
> On Sat, Dec 18, 2010 at 09:39:34PM +0800, Shawn Guo wrote:
> > Add initial mx23evk support with duart.
> > 
> > Signed-off-by: Shawn Guo <shawn.guo@freescale.com>
> > ---
> > Changes for v7:
> >  - Define mx23evk pads using naked pad "OR" mA/vol/pull configurations
> > 
> > Changes for v3:
> >  - Remove inclusion of hardware.h
> >  - Add __initconst for mx23evk_pads[]
> > 
> > Changes for v2:
> >  - Remove boot_params
> > 
> >  arch/arm/mach-mxs/mach-mx23evk.c |   59 ++++++++++++++++++++++++++++++++++++++
> >  1 files changed, 59 insertions(+), 0 deletions(-)
> >  create mode 100644 arch/arm/mach-mxs/mach-mx23evk.c
> > 
> > diff --git a/arch/arm/mach-mxs/mach-mx23evk.c b/arch/arm/mach-mxs/mach-mx23evk.c
> > new file mode 100644
> > index 0000000..2aa77cc
> > --- /dev/null
> > +++ b/arch/arm/mach-mxs/mach-mx23evk.c
> > @@ -0,0 +1,59 @@
> > [...]
> > +static const iomux_cfg_t mx23evk_pads[] __initconst = {
> > +	/* duart */
> > +	MX23_PAD_PWM0__DUART_RX |
> > +		MXS_PAD_4MA,
> > +	MX23_PAD_PWM1__DUART_TX |
> > +		MXS_PAD_4MA,
> > +};
> I would keep these on a single line.  YMMV, so for me no need for a v8.
> 
> I will test this series later on hardware, and if no show stoppers
> appear I'd say this is ready to be merged.  The (maybe) remaining issues
> can then be resolved in follow up patches.
> 
My intension was to keep the pad configuration on different line from
the naked pad.  I will keep this comment and that extra space one
in mind, and address them later.

Thanks for the review and test effort. 

-- 
Regards,
Shawn

  reply	other threads:[~2010-12-20 10:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-18 13:39 [PATCH v7 00/15] ARM: mxs: Add initial support for MX23 and MX28 Shawn Guo
2010-12-18 13:39 ` [PATCH v7 03/15] ARM: mxs: Add reset routines Shawn Guo
2010-12-18 13:39 ` [PATCH v7 04/15] ARM: mxs: Add interrupt support Shawn Guo
2010-12-18 13:39 ` [PATCH v7 05/15] ARM: mxs: Add low-level debug UART support Shawn Guo
2010-12-20 11:50   ` Wolfram Sang
2010-12-20 13:22     ` Shawn Guo
2010-12-20 13:55       ` Wolfram Sang
2010-12-20 14:25         ` Shawn Guo
2010-12-20 14:35           ` Wolfram Sang
2010-12-18 13:39 ` [PATCH v7 06/15] ARM: mxs: Add timer support Shawn Guo
2010-12-18 13:39 ` [PATCH v7 07/15] ARM: mxs: Add gpio support Shawn Guo
2010-12-18 13:39 ` [PATCH v7 08/15] ARM: mxs: Add iomux support Shawn Guo
2010-12-20  9:44   ` Uwe Kleine-König
2010-12-18 13:39 ` [PATCH v7 09/15] ARM: mxs: Add clock support Shawn Guo
2010-12-18 13:39 ` [PATCH v7 13/15] ARM: mxs: Add initial mx23evk support Shawn Guo
2010-12-20  9:48   ` Uwe Kleine-König
2010-12-20 10:17     ` Shawn Guo [this message]
2010-12-18 13:39 ` [PATCH v7 14/15] ARM: mxs: Add initial mx28evk support Shawn Guo

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=20101220101709.GA16497@freescale.com \
    --to=shawn.guo@freescale.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).