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:55:54 +0200 [thread overview]
Message-ID: <20090627215554.GP8587@game.jcrosoft.org> (raw)
In-Reply-To: <6ed0b2680906260143x5e103a25s6c55d7005c3db634@mail.gmail.com>
On 11:43 Fri 26 Jun , Grazvydas Ignotas wrote:
> On Fri, Jun 26, 2009 at 12:59 AM, 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
>
> There are only several old prototypes some developers have, there is
> really no need to complicate code to support those boards. The old
> boards will be replaced anyway as they don't fit into the case.
If only one active user have the board we need to support it
>
> > this kind of huge update is non bisectable
>
> Yes but current boards don't even work with what is in mainline, so it
> doesn't make much sense to bisect anyway.
>
> > so we do need to use a true mux api
> > as the kernel lot's of other arch in u-boot
>
> You could be right, but I don't think I can contribute this at the
> moment. Current mux api is good enough for single configuration we
> need.
no it's a mess to use and manage and duplicate code
Best Regards,
J.
prev parent reply other threads:[~2009-06-27 21:55 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
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 [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=20090627215554.GP8587@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