From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3 pandora: update pin mux for rev3 boards
Date: Sat, 27 Jun 2009 23:58:37 +0200 [thread overview]
Message-ID: <20090627215837.GQ8587@game.jcrosoft.org> (raw)
In-Reply-To: <f20732e90906251712sc7b9899rb6a68c977e835d5f@mail.gmail.com>
On 19:12 Thu 25 Jun , Jason Kridner wrote:
> On Thu, Jun 25, 2009 at 4:59 PM, Jean-Christophe PLAGNIOL-VILLARD
> <plagnioj@jcrosoft.com> wrote:
>
> On 14:57 Mon 08 Jun , Grazvydas Ignotas wrote:
> > The update consists of following changes:
> > - remove configuration of not connected pins, effectively
> > leaving them in safe mode.
> > - remove unused GPIOs, setup newly added ones.
> > - setup pulls for various GPIOs. Disable pulls for game
> > buttons, as they have external pulls.
> > - SDRC CS change based on recent patch for
> > Beagle and Overo.
> >
> > Old boards are no longer supported, but there was only
> > small number of test boards made. Updated configuration
> > is expected to be used for mass production.
> If user have old version in possession NACK
>
> I believe no users who would possibly object have the old version (or any
> version) in possession. Only the core developers ever got these boards.
> Is the expectation to create #ifdef or some sort of auto-detection
> (unlikely possible)?
untill the hardware will be really not anymore use yes please
>
>
> this kind of huge update is non bisectable so we do need to use a true
> mux api
> as the kernel lot's of other arch in u-boot
>
> Why is it not bisectable?
because your mix cleanup, fixup and new board support
>
> Do you have a "true mux api" to suggest?
the same as the kernel one is the best for code sharing
Best Regards,
J.
next prev parent reply other threads:[~2009-06-27 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 11:57 [U-Boot] [PATCH] OMAP3 pandora: update pin mux for rev3 boards Grazvydas Ignotas
2009-06-25 21:59 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-26 0:12 ` Jason Kridner
2009-06-27 21:58 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-06-28 5:40 ` Dirk Behme
2009-06-28 9:13 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-28 11:11 ` Dirk Behme
2009-06-28 11:50 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-28 12:17 ` Dirk Behme
2009-06-28 20:07 ` Grazvydas Ignotas
2009-06-28 21:21 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-26 8:43 ` Grazvydas Ignotas
2009-06-27 21:55 ` Jean-Christophe PLAGNIOL-VILLARD
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=20090627215837.GQ8587@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--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