From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra114: Dalmore: Add pad config tables/code based on pinmux code
Date: Tue, 12 Mar 2013 11:41:19 -0600 [thread overview]
Message-ID: <513F68BF.9020206@wwwdotorg.org> (raw)
In-Reply-To: <1363104552-30065-1-git-send-email-twarren@nvidia.com>
On 03/12/2013 10:09 AM, Tom Warren wrote:
> Pad config registers exist in APB_MISC_GP space, and control slew
> rate, drive strengh, schmidt, high-speed, and low-power modes for
> all of the pingroups in Tegra30. This builds off of the pinmux
> way of constructing init tables to configure select pads (SDIOCFG,
> for instance) during pinmux_init().
>
> Currently, no padcfg entries exist. SDIO3CFG will be added when the
> MMC driver is added as per the TRM to work with the SD-card slot on
> Dalmore E1611.
Much of the pinmux driver code here is common with Tegra30. We should at
least file a bug to move it to a common file at some point.
> diff --git a/arch/arm/include/asm/arch-tegra114/pinmux.h b/arch/arm/include/asm/arch-tegra114/pinmux.h
> +#define PGRP_SLWF_NONE -1
> +#define PGRP_SLWF_MAX 3
> +#define PGRP_SLWR_NONE PGRP_SLWF_NONE
> +#define PGRP_SLWR_MAX PGRP_SLWF_MAX
> +
> +#define PGRP_DRVUP_NONE -1
> +#define PGRP_DRVUP_MAX 127
> +#define PGRP_DRVDN_NONE PGRP_DRVUP_NONE
> +#define PGRP_DRVDN_MAX PGRP_DRVUP_MAX
There seems to be some mixed use of TABs/spaces there. Feel free to fix
up when you apply it.
Aside from that,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-03-12 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 16:09 [U-Boot] [PATCH] Tegra114: Dalmore: Add pad config tables/code based on pinmux code Tom Warren
2013-03-12 17:41 ` Stephen Warren [this message]
2013-03-12 17:47 ` Tom Warren
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=513F68BF.9020206@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.