public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/7] tegra: Enhance funcmux to support I2C and MMC
Date: Mon, 09 Jan 2012 16:11:37 -0700	[thread overview]
Message-ID: <4F0B7429.8040800@nvidia.com> (raw)
In-Reply-To: <1326149613-7304-1-git-send-email-sjg@chromium.org>

On 01/09/2012 03:53 PM, Simon Glass wrote:
> This series expands funcmux_select() to support configs other than 0, and
> to support options associated with a config.
> 
> This permits introduction of I2C support using multiple config options.
> 
> The options parameter is used by MMC to select standard (4-bit) or 8-bit
> operation.

The unification in this series basically seems fine.

Why not consider bus width part of the "config" though, rather the
complicating things with an extra parameter? As an example, for SDMMC4,
you'd have say:

0: ATC + ATD 8 bit
1: ATB + GMA 4 bit
2: ATB + GMA + GME 8 bit

... and no option values.

Also, we should probably define names for the config values, at least in
the cases where 0 isn't the only option. Hard-coding 0 or 1 at the call
sites isn't very meaningful.

Oh, and SDMMC4's option 0 isn't correct: I think pin group ATB should be
removed, since it contains signals SDIO4_CLK and SDIO4_CMD which are
also part of pin group ATC, when those pin groups are set to function
SDIO4 at least. I didn't check to see if any other similar problems exist.

-- 
nvpublic

  parent reply	other threads:[~2012-01-09 23:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 22:53 [U-Boot] [PATCH 0/7] tegra: Enhance funcmux to support I2C and MMC Simon Glass
2012-01-09 22:53 ` [U-Boot] [PATCH 1/7] tegra: Adjust funcmux config test to permit expansion Simon Glass
2012-01-09 22:53 ` [U-Boot] [PATCH 2/7] tegra: Add I2C support to funcmux Simon Glass
2012-01-09 22:53 ` [U-Boot] [PATCH 3/7] tegra: Enhance funcmux to support options Simon Glass
2012-01-09 22:53 ` [U-Boot] [PATCH 4/7] tegra: Add SDMMC support to funcmux Simon Glass
2012-01-09 22:53 ` [U-Boot] [PATCH 5/7] tegra: Use funcmux for MMC on tamonten Simon Glass
2012-01-10  7:31   ` Thierry Reding
2012-01-11 21:54     ` Simon Glass
2012-01-09 22:53 ` [U-Boot] [PATCH 6/7] tegra: Use funcmux for MMC on harmony Simon Glass
2012-01-09 22:53 ` [U-Boot] [PATCH 7/7] tegra: Use funcmux for MMC on seaboard Simon Glass
2012-01-09 23:11 ` Stephen Warren [this message]
2012-01-09 23:36   ` [U-Boot] [PATCH 0/7] tegra: Enhance funcmux to support I2C and MMC Simon Glass
2012-01-09 23:46     ` Stephen Warren
2012-01-11 22:41       ` Simon Glass

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=4F0B7429.8040800@nvidia.com \
    --to=swarren@nvidia.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