All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 2/6] i.MX6: consolidate pad names for multi-CPU boards
Date: Thu, 28 Feb 2013 13:45:36 -0700	[thread overview]
Message-ID: <512FC1F0.30008@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5Diu4rEDLC4+qEdSo_SF37jyn9rTUPDWvpe=65En462pg@mail.gmail.com>

On 02/28/2013 01:26 PM, Fabio Estevam wrote:
> Hi Eric,
>
> On Sat, Feb 23, 2013 at 1:31 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>
>> It's probably going to be a week or so before I can re-work the
>> HDMI detection code per Wolfgang's request and re-submit Nitrogen6X.
>
> I work on a patch that will add an hdmi structure, so that we can
> remove the base + offset register access.
>
> Will send it later today.
>

Thanks Fabio.

  reply	other threads:[~2013-02-28 20:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 20:06 [U-Boot] V2: i.MX6: updates to support boards with multiple CPU options Eric Nelson
2013-02-19 20:07 ` [U-Boot] [PATCH V2 1/6] i.MX6: mx6qsabrelite: indent with tabs Eric Nelson
2013-02-23  9:57   ` Stefano Babic
2013-02-19 20:07 ` [U-Boot] [PATCH V2 2/6] i.MX6: consolidate pad names for multi-CPU boards Eric Nelson
2013-02-23  9:57   ` Stefano Babic
2013-02-23 10:22   ` Stefano Babic
2013-02-23 16:31     ` Eric Nelson
2013-02-28 20:26       ` Fabio Estevam
2013-02-28 20:45         ` Eric Nelson [this message]
2013-02-19 20:07 ` [U-Boot] [PATCH V2 3/6] i.MX6: crm_regs: define CCM_CCGRx for use in board config files Eric Nelson
2013-02-23  9:57   ` Stefano Babic
2013-02-19 20:07 ` [U-Boot] [PATCH V2 4/6] i.MX6: crm_regs: define IOMUXC_GPR4/6/7 Eric Nelson
2013-02-23  9:57   ` Stefano Babic
2013-02-19 20:07 ` [U-Boot] [PATCH V2 5/6] i.MX6DL: define IOMUX pads NANDF_CS1-3 for use as GPIO Eric Nelson
2013-02-23  9:57   ` Stefano Babic
2013-02-19 20:07 ` [U-Boot] [PATCH V2 6/6] i.MX6: Add DDR controller registers Eric Nelson
2013-02-23  9:57   ` Stefano Babic

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=512FC1F0.30008@boundarydevices.com \
    --to=eric.nelson@boundarydevices.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 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.