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 v2 7/7] Tegra30: Add/enable Cardhu build (T30 reference board)
Date: Tue, 04 Dec 2012 15:41:36 -0700	[thread overview]
Message-ID: <50BE7C20.6000206@wwwdotorg.org> (raw)
In-Reply-To: <1354653614.1503.47.camel@tellur>

On 12/04/2012 01:40 PM, Lucas Stach wrote:
> Hi Tom,
> 
> Am Dienstag, den 04.12.2012, 13:22 -0700 schrieb Tom Warren:
> [...]
>>
>>>
>>>> +#define V_NS16550_CLK                        216000000       /* 216MHz (pllp_out0) */
>>>
>>> I thought PLL_P ran at 408MHz on Tegra30? The kernel certainly sets it
>>> up that way.
>>
>> See my previous reply. In the internal U-Boot repo I ported from, PLLP
>> was initially set to 216MHz, then sped up to 408MHz. When this first
>> round of patches is in, I can address going to 408MHz first thing.
>>
> Is running the PLL_P at 408MHz something which requires a lot of work?
> If not, please do this and fold it into this patchset. It doesn't look
> too nice adding things to upstream which have to be changed/removed
> immediately after going in.

Naively I'd have to agree here; it seems that programming the PLL for
the correct rate would probably "just work" right from the outset? After
all, if the code runs OK with the higher rate enabled a little later in
boot, I see no reason it shouldn't run OK with that exact same rate the
whole way through.

  parent reply	other threads:[~2012-12-04 22:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 23:45 [U-Boot] [PATCH v2 0/7] Add support for NVIDIA Tegra30 SoC Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 1/7] Tegra30: Add arch-tegra30 include files Tom Warren
2012-12-04  0:22   ` Stephen Warren
2012-12-04 17:42     ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 2/7] Tegra30: Add AVP (arm720t) files Tom Warren
2012-12-04  0:34   ` Stephen Warren
2012-12-04 17:47     ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 3/7] Tegra30: Add CPU (armv7) files Tom Warren
2012-12-04  0:36   ` Stephen Warren
2012-12-03 23:45 ` [U-Boot] [PATCH V2 4/7] Tegra30: Add common CPU (shared) files Tom Warren
2012-12-05 20:37   ` Stephen Warren
2012-12-05 21:32     ` Tom Warren
2012-12-05 21:38       ` Stephen Warren
2012-12-05 21:43         ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 5/7] Tegra30: Cardhu: Add DT files Tom Warren
2012-12-04  0:40   ` Stephen Warren
2012-12-04  0:49     ` Simon Glass
2012-12-04  0:57       ` Stephen Warren
2012-12-04  1:01         ` Simon Glass
2012-12-04 20:29           ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 6/7] Tegra30: Add generic Tegra30 build support Tom Warren
2012-12-04  0:42   ` Stephen Warren
2012-12-04 19:48     ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 7/7] Tegra30: Add/enable Cardhu build (T30 reference board) Tom Warren
2012-12-04  0:53   ` Stephen Warren
2012-12-04 20:22     ` Tom Warren
2012-12-04 20:40       ` Lucas Stach
2012-12-04 21:28         ` Tom Warren
2012-12-04 22:41         ` Stephen Warren [this message]
2012-12-08 20:00           ` Simon Glass
2012-12-10 17:05             ` Tom Warren
2012-12-10 19:04               ` Simon Glass
2012-12-04 22:43       ` Stephen Warren
2012-12-05 20:30         ` Tom Warren
2012-12-04  0:07 ` [U-Boot] [PATCH v2 0/7] Add support for NVIDIA Tegra30 SoC 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=50BE7C20.6000206@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