From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 4/7] Tegra30: Add common CPU (shared) files
Date: Wed, 12 Dec 2012 15:06:22 -0700 [thread overview]
Message-ID: <50C8FFDE.4030506@wwwdotorg.org> (raw)
In-Reply-To: <CA+m5__J1n_md3gyBmBQBu6_gjKfqYAE7=y-XgcE_L8LhgwgFmQ@mail.gmail.com>
On 12/12/2012 09:14 AM, Tom Warren wrote:
> Allen,
>
> On Tue, Dec 11, 2012 at 5:45 PM, Allen Martin <amartin@nvidia.com> wrote:
>> On Tue, Dec 11, 2012 at 03:34:15PM -0800, Tom Warren wrote:
>>> These files are used by both SPL and main U-Boot.
>>> Also made minor changes to shared Tegra code to support
>>> T30 differences.
>>>
>>> Signed-off-by: Tom Warren <twarren@nvidia.com>
>>> ---
>>> V2:
>>> * Differentiate between T20 and T30 in ODMDATA and query_sdram_size.
>>> * Fix numerous func entries in pingroup table as per Stephen.
>>> * Added warning about LOCK bit in pinmux_set_lock.
>>> V3:
>>> * Always program PLLP to 408MHz
>>> * Use generic SoC string in print_cpuinfo
>>>
> <snip>
>>>
>>> - bct_start = readl(AP20_BASE_PA_SRAM + NVBOOTINFOTABLE_BCTPTR);
>>> + bct_start = readl(NV_PA_BASE_SRAM + NVBOOTINFOTABLE_BCTPTR);
>>> odmdata = readl(bct_start + BCT_ODMDATA_OFFSET);
>>>
>>> return odmdata;
>>> @@ -127,5 +137,5 @@ void s_init(void)
>>> "orr r0, r0, #0x41\n"
>>> "mcr p15, 0, r0, c1, c0, 1\n");
>>>
>>> - /* FIXME: should have ap20's L2 disabled too? */
>>> + /* FIXME: should have SoC's L2 disabled too? */
>>
>> We should probably just remove this README, I don't believe it applies
>> any more.
>
> By README, you mean FIXME? It can be removed, but only if I'm forced
> to do a V4 patchset for more substantive changes. Otherwise I'll put
> it in my list of 'cleanup' items.
In my opinion at least, for very minor stuff like this, you can just
implement the review feedback and apply the patches without the need to
actually repost it. Anything much more than editing a comment, removing
a stale comment or removing some added lines from the patch that
shouldn't be added would warrant a repost though.
next prev parent reply other threads:[~2012-12-12 22:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 23:34 [U-Boot] [PATCH V3 0/7] Add support for NVIDIA Tegra30 SoC Tom Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 1/7] Tegra30: Add arch-tegra30 include files Tom Warren
2012-12-12 0:36 ` Stephen Warren
2012-12-12 16:23 ` Tom Warren
2012-12-12 22:02 ` Stephen Warren
2012-12-12 23:06 ` Tom Warren
2012-12-12 14:55 ` Simon Glass
2012-12-11 23:34 ` [U-Boot] [PATCH V3 2/7] Tegra30: Add AVP (arm720t) files Tom Warren
2012-12-12 0:40 ` Stephen Warren
2012-12-12 16:24 ` Tom Warren
2012-12-12 14:58 ` Simon Glass
2012-12-11 23:34 ` [U-Boot] [PATCH V3 3/7] Tegra30: Add CPU (armv7) files Tom Warren
2012-12-12 0:41 ` Stephen Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 4/7] Tegra30: Add common CPU (shared) files Tom Warren
2012-12-12 0:45 ` Allen Martin
2012-12-12 16:14 ` Tom Warren
2012-12-12 22:06 ` Stephen Warren [this message]
2012-12-12 23:07 ` Tom Warren
2012-12-12 22:09 ` Stephen Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 5/7] Tegra30: Cardhu: Add DT files Tom Warren
2012-12-12 22:10 ` Stephen Warren
2012-12-12 23:11 ` Tom Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 6/7] Tegra30: Add generic Tegra30 build support Tom Warren
2012-12-12 22:13 ` Stephen Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 7/7] Tegra30: Add/enable Cardhu build (T30 reference board) Tom Warren
2012-12-12 22:21 ` Stephen Warren
2012-12-12 1:09 ` [U-Boot] [PATCH V3 0/7] Add support for NVIDIA Tegra30 SoC Allen Martin
2012-12-12 2:47 ` Allen Martin
2012-12-12 3:05 ` Allen Martin
2012-12-12 22:40 ` Simon Glass
2012-12-12 23:12 ` 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=50C8FFDE.4030506@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