linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mike@compulab.co.il (mike at compulab.co.il)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 2/4] omap: igep0020: minor refactoring
Date: Sun, 15 May 2011 21:50:43 +0300	[thread overview]
Message-ID: <20110515185043.GA24785@gentoodev.compulab.local> (raw)
In-Reply-To: <201105132044.39163.arnd@arndb.de>

On Fri, May 13, 2011 at 08:44:38PM +0200, Arnd Bergmann wrote:
> On Thursday 12 May 2011, Mike Rapoport wrote:
> > @@ -299,17 +299,14 @@ static struct omap2_hsmmc_info mmc[] = {
> >  static struct gpio_led igep_gpio_leds[] = {
> >         [0] = {
> >                 .name                   = "gpio-led:red:d0",
> > -               .gpio                   = IGEP2_GPIO_LED0_RED,
> >                 .default_trigger        = "default-off"
> >         },
> >         [1] = {
> >                 .name                   = "gpio-led:green:d0",
> > -               .gpio                   = IGEP2_GPIO_LED0_GREEN,
> >                 .default_trigger        = "default-off",
> >         },
> >         [2] = {
> >                 .name                   = "gpio-led:red:d1",
> > -               .gpio                   = IGEP2_GPIO_LED1_RED,
> >                 .default_trigger        = "default-off",
> >         },
> >         [3] = {
> > @@ -335,6 +332,10 @@ static struct platform_device igep_led_device = {
> >  
> >  static void __init igep_leds_init(void)
> >  {
> > +       igep_gpio_leds[0].gpio = IGEP2_GPIO_LED0_RED;
> > +       igep_gpio_leds[1].gpio = IGEP2_GPIO_LED0_GREEN;
> > +       igep_gpio_leds[2].gpio = IGEP2_GPIO_LED1_RED;
> > +
> >         platform_device_register(&igep_led_device);
> >  }
> 
> Hi Mike,
> 
> Overall, the series looks great, but I'm somewhat worried by the fact that you
> have to replace data structures with code in order to get there. Are there any
> other options to do this?
 
We can keep all the data structures that differ between IGEP2 and IGEP3.
However, this significantly reduces the benifit of the series.
There's already code in the IGEP2 that differentiates between HW
revisions, so anyway the board support will require some work for
devicetree transition. Eventually, when devicetree will be usable on
OMAPs, most of the code currently found in arch/arm/mach-omap2/board*
will require some work and I hardly believe that the transition can be
automated...

> 	Arnd
> 
--
Sincerely yours,
Mike.

  reply	other threads:[~2011-05-15 18:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 21:40 [RESEND PATCH 0/4] omap: merge IGEP v2 and v3 Mike Rapoport
2011-05-12 21:40 ` [RESEND PATCH 1/4] omap: igep0020: name refactoring for future merge with IGEP3 Mike Rapoport
2011-05-16  7:15   ` Enric Balletbò i Serra
2011-05-17  7:53     ` Tony Lindgren
2011-05-17  7:57       ` Enric Balletbò i Serra
2011-05-17 10:33         ` Tony Lindgren
2011-05-18  9:05           ` Igor Grinberg
2011-05-12 21:40 ` [RESEND PATCH 2/4] omap: igep0020: minor refactoring Mike Rapoport
2011-05-13 18:44   ` Arnd Bergmann
2011-05-15 18:50     ` mike at compulab.co.il [this message]
2011-05-15 20:27       ` Arnd Bergmann
2011-05-16  7:17         ` Enric Balletbò i Serra
2011-05-12 21:40 ` [RESEND PATCH 3/4] omap: igep0020: add support for IGEP3 Mike Rapoport
2011-05-12 21:40 ` [RESEND PATCH 4/4] omap: drop board-igep0030.c Mike Rapoport
2011-05-16  7:18   ` Enric Balletbò i Serra
2011-05-13  7:27 ` [RESEND PATCH 0/4] omap: merge IGEP v2 and v3 Enric Balletbò i Serra
2011-05-13  8:42   ` mike at compulab.co.il

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=20110515185043.GA24785@gentoodev.compulab.local \
    --to=mike@compulab.co.il \
    --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).