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 22:38:59 -0600 [thread overview]
Message-ID: <51415463.5090406@wwwdotorg.org> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F37A7474711@HQMAIL04.nvidia.com>
On 03/13/2013 08:13 PM, Tom Warren wrote:
> Stephen,
>
>> -----Original Message-----
>> From: Stephen Warren [mailto:swarren at wwwdotorg.org]
>> Sent: Wednesday, March 13, 2013 4:30 PM
>> To: Tom Warren
>> Cc: u-boot at lists.denx.de; Stephen Warren; Tom Warren
>> Subject: Re: [U-Boot] [PATCH] Tegra114: Fix/update GP padcfg register struct
>>
>> 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 felt it prudent to add 0x800 since the register addresses spilled over into the 0x900 range, and it would have looked weird to have 0xFC, then 0x900, 0x904, etc.
> I could revert the old offset, and then make the change to the new regs go 0xFC, then 0x100, 0x104, etc. i.e. offset based off of the absolute address of the GP base of 0x70000800. Let me know.
I think it'd make sense to either list the offsets as relative to the
start of the struct (as they are now), or have 2 separate patches the
first adding 0x800 to everything as a simple/obvious patch, and the
second fixing the struct to match Tegra114 HW.
prev parent reply other threads:[~2013-03-14 4:38 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
2013-03-14 2:13 ` Tom Warren
2013-03-14 4:38 ` Stephen Warren [this message]
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=51415463.5090406@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