public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] ARM: Tegra210: Add SoC code/include files for T210
Date: Tue, 16 Jun 2015 14:26:30 -0600	[thread overview]
Message-ID: <55808676.10007@wwwdotorg.org> (raw)
In-Reply-To: <b7662898ad86481ca1df41cab9ca342e@DRHQMAIL103.nvidia.com>

On 06/15/2015 02:04 PM, Tom Warren wrote:
>
>
>> -----Original Message-----
>> From: Stephen Warren [mailto:swarren at wwwdotorg.org]
>> Sent: Monday, June 15, 2015 10:11 AM
>> To: Tom Warren
>> Cc: u-boot at lists.denx.de; Stephen Warren; Tom Warren
>> Subject: Re: [U-Boot] [PATCH 1/4] ARM: Tegra210: Add SoC code/include files
>> for T210
>>
>> On 06/03/2015 02:35 PM, Tom Warren wrote:
>>> All based off of Tegra124. As a Tegra210 board is brought up, these
>>> may change a bit to match the HW more closely, but probably 90% of
>>> this is identical to T124.
>>
>> Rather than duplicating lots of headers and code, can we share the content
>> with other chips?
 >
> Sure, but I wasn't looking at this patchset as a reworking of all Tegra common headers, but an inclusion of T210 support. We can then move to common/shared content after this is in, or someone (you?) can do it now before I add T210 support, but that'll delay it.

The problem here is that the same excuse against cleanup is made every 
time a new SoC comes along, and the cleanup never happens.

>>> diff --git a/arch/arm/include/asm/arch-tegra210/funcmux.h
>>> b/arch/arm/include/asm/arch-tegra210/funcmux.h
>>
>> We should be able to drop funcmux support completely now that we're
>> programming entire board pinmux tables.
 >
> I'll look into it, but I believe funcmux is only used to get early UART muxes set, which is done before the pinmux table is parsed/written.

There's no guarantee funcmux will work in general for the UARTs. The 
best solution would be to apply the pinmux table before doing anything. 
That way, we wouldn't need anything custom to try and get the UART working.

  reply	other threads:[~2015-06-16 20:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 20:35 [U-Boot] [PATCH 0/4] Tegra210 support for P2571 Tom Warren
2015-06-03 20:35 ` [U-Boot] [PATCH 1/4] ARM: Tegra210: Add SoC code/include files for T210 Tom Warren
2015-06-15 17:11   ` Stephen Warren
2015-06-15 20:04     ` Tom Warren
2015-06-16 20:26       ` Stephen Warren [this message]
2015-06-15 22:18     ` Tom Warren
2015-06-16 20:29       ` Stephen Warren
2015-06-16 21:30         ` Tom Warren
2015-06-03 20:35 ` [U-Boot] [PATCH 2/4] ARM: Tegra210: Add support to common Tegra source/config files Tom Warren
2015-06-15 17:18   ` Stephen Warren
2015-06-03 20:35 ` [U-Boot] [PATCH 3/4] P2571: dts: Add DT files for Tegra210/P2571 board Tom Warren
2015-06-15 17:23   ` Stephen Warren
2015-06-15 17:57     ` Tom Warren
2015-06-03 20:35 ` [U-Boot] [PATCH 4/4] T210: Add support for T210-based P2571 board Tom Warren
2015-06-15 17:58   ` Stephen Warren
2015-06-15 18:08     ` Tom Warren
2015-06-15 18:22     ` Stephen Warren
2015-06-15 19:41       ` Tom Warren
2015-06-17 20:07 ` [U-Boot] [PATCH 0/4] Tegra210 support for P2571 Stephen Warren
2015-06-17 22:44   ` Tom Warren
2015-06-19 22:25     ` 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=55808676.10007@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