All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: Robert Nelson <robertcnelson@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH v6 1/3] ARM: OMAP: Beagle: revision detection
Date: Thu, 23 Sep 2010 10:26:31 -0700	[thread overview]
Message-ID: <20100923172631.GN4211@atomide.com> (raw)
In-Reply-To: <20100820150328.c18681ce.jhnikula@gmail.com>

* Jarkko Nikula <jhnikula@gmail.com> [100820 04:55]:
> On Thu, 19 Aug 2010 21:38:44 -0500
> Robert Nelson <robertcnelson@gmail.com> wrote:
> 
> > Due to the omap3530 ES3.0 Silicon being used on both the
> > B5/B6 and C1/2/3 Beagle we can't use the cpu_is_omap34xx() 
> > routines to differentiate the Beagle Boards.
> > 
> > However gpio pins 171,172,173 where setup for this prupose, so 
> > lets use them.
> > 
> > Changes:
> > for older U-Boot's, use omap_mux_init_gpio()
> > keep Beagle Rev in board-omap3beagle.c
> > gpio_free on gpio request failure
> > 
> > Tested on Beagle Revisions: B5, C2, C4, and xMA
> > 
> > Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
> > Cc: Jarkko Nikula <jhnikula@gmail.com>
> > ---
> 
> To this set:
> 
> Acked-by: Jarkko Nikula <jhnikula@gmail.com>

Adding all three.

Tony

      reply	other threads:[~2010-09-23 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20  2:38 [PATCH v6 1/3] ARM: OMAP: Beagle: revision detection Robert Nelson
2010-08-20  2:38 ` [PATCH v6 2/3] ARM: OMAP: Beagle: only Cx boards use pin 23 for write protect Robert Nelson
2010-08-20  2:38 ` [PATCH v6 3/3] ARM: OMAP: Beagle: no gpio_wp pin connection on xM Robert Nelson
2010-08-20 12:03 ` [PATCH v6 1/3] ARM: OMAP: Beagle: revision detection Jarkko Nikula
2010-09-23 17:26   ` Tony Lindgren [this message]

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=20100923172631.GN4211@atomide.com \
    --to=tony@atomide.com \
    --cc=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=robertcnelson@gmail.com \
    /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.