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 2/4] ARM: Tegra210: Add support to common Tegra source/config files
Date: Mon, 15 Jun 2015 11:18:01 -0600	[thread overview]
Message-ID: <557F08C9.5090409@wwwdotorg.org> (raw)
In-Reply-To: <1433363711-29554-3-git-send-email-twarren@nvidia.com>

On 06/03/2015 02:35 PM, Tom Warren wrote:
> Derived from Tegra124, modify as appropriate during T210
> board bringup. Cleaned up debug statements to conserve
> string space, too.
>
> Note that the 'empty' Kconfig for Tegra210 will cause
> an innocuous build warning, but it'll go away when a
> real T210 board is instantiated.

> diff --git a/arch/arm/mach-tegra/clock.c b/arch/arm/mach-tegra/clock.c
> index cdd5438..2ef8ae2 100644
> --- a/arch/arm/mach-tegra/clock.c
> +++ b/arch/arm/mach-tegra/clock.c
> @@ -1,5 +1,5 @@
>   /*
> - * Copyright (c) 2010-2014, NVIDIA CORPORATION.  All rights reserved.
> + * Copyright (c) 2010-2015, NVIDIA CORPORATION.  All rights reserved.
>    *
>    * This program is free software; you can redistribute it and/or modify it
>    * under the terms and conditions of the GNU General Public License,
> @@ -629,6 +629,7 @@ static void set_avp_clock_source(u32 src)
>   /*
>    * This function is useful on Tegra30, and any later SoCs that have compatible
>    * PLLP configuration registers.
> + * NOTE: Not used on Tegra210 - see tegra210_setup_pllp in T210 clock.c

I think we're only meant to update the copyright date for non-trivial 
changes.

> diff --git a/arch/arm/mach-tegra/cpu.c b/arch/arm/mach-tegra/cpu.c

> @@ -39,6 +40,8 @@ int get_num_cpus(void)
>   		break;
>   	case CHIPID_TEGRA30:
>   	case CHIPID_TEGRA114:
> +	case CHIPID_TEGRA124:
> +	case CHIPID_TEGRA210:

It would be nice to break out the T124 change as a separate patch, since 
it affects something other than T210.

> diff --git a/arch/arm/mach-tegra/cpu.h b/arch/arm/mach-tegra/cpu.h

> -#define CORESIGHT_UNLOCK	0xC5ACCE55;
> +#define CORESIGHT_UNLOCK	0xC5ACCE55

Do we use that anywhere? If not, perhaps just delete it, probably as a 
separate patch.

  reply	other threads:[~2015-06-15 17:18 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
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 [this message]
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=557F08C9.5090409@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