From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra114: Fix/update GP padcfg register struct
Date: Wed, 13 Mar 2013 17:30:15 -0600 [thread overview]
Message-ID: <51410C07.5080408@wwwdotorg.org> (raw)
In-Reply-To: <1363214098-30952-1-git-send-email-twarren@nvidia.com>
On 03/13/2013 04:34 PM, Tom Warren wrote:
> Differences in padcfg registers (some removed, some added) between
> Tegra30 and Tegra114 weren't picked up when I ported this file.
> Also removed the HSM setting for SDIOCFG - not called out in TRM.
The actual diff would be a lot easier to see if the register offsets
hadn't all had 0x800 added to them as well in the same patch. MODEREG
and HIDREV are at the same absolute address in Tegra20/30/114 for example.
I didn't check the content of this patch due to that, but it seems fine
if it matches the TRM.
next prev parent reply other threads:[~2013-03-13 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 22:34 [U-Boot] [PATCH] Tegra114: Fix/update GP padcfg register struct Tom Warren
2013-03-13 23:30 ` Stephen Warren [this message]
2013-03-14 2:13 ` Tom Warren
2013-03-14 4:38 ` Stephen 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=51410C07.5080408@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox