public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] sunxi: Yones Toptech BD1078 support
Date: Mon, 23 Mar 2015 17:26:22 +0100	[thread overview]
Message-ID: <55103EAE.4080304@redhat.com> (raw)
In-Reply-To: <1427044344-32135-1-git-send-email-contact@paulk.fr>

Hi,

p.s.


On 22-03-15 18:12, Paul Kocialkowski wrote:
> This series goes on top of my previous series that concludes with Ainol AW1
> support.
>
> Also, if you're interested by the idea of using sunxi_name_to_gpio_bank, this
> could be extended for UART as well, where *many* different pin mux setups are
> possible. We are just lucky that hardware designers usually use the ports that
> U-Boot selects, but there is no fundamental reason for that.

I'm not really interested in making the #ifdeffery for the uart setup even
more complicated, eventually we should get all this info, including all the
pinmux stuff from a dtb (shared with the kernel) appended to the u-boot binary,
and then this will use standard devicetree pinmux stuff, until we get there
I would like to keep this as simple as possible.

Regards,

Hans

  parent reply	other threads:[~2015-03-23 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 17:12 [U-Boot] [PATCH 0/3] sunxi: Yones Toptech BD1078 support Paul Kocialkowski
2015-03-22 17:12 ` [U-Boot] [PATCH 1/3] sunxi: GPIO pin mux hardware-feature-specific function index defines Paul Kocialkowski
2015-03-22 17:12 ` [U-Boot] [PATCH 2/3] sunxi: Complete mmc pin mux for each supported platform, configured with Kconfig Paul Kocialkowski
2015-03-22 17:12 ` [U-Boot] [PATCH 3/3] sunxi: Yones Toptech BD1078 support Paul Kocialkowski
2015-03-23 16:24 ` [U-Boot] [PATCH 0/3] " Hans de Goede
2015-03-23 16:26 ` Hans de Goede [this message]
2015-03-23 16:28   ` Paul Kocialkowski

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=55103EAE.4080304@redhat.com \
    --to=hdegoede@redhat.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