linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: tegra: Add cpu node in device tree
Date: Fri, 11 Jan 2013 14:44:49 +0000	[thread overview]
Message-ID: <20130111144449.GF30538@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <1357909914-28994-1-git-send-email-hdoyu@nvidia.com>

On Fri, Jan 11, 2013 at 01:11:52PM +0000, Hiroshi Doyu wrote:
> Hi,
> 
> From the discussion(*1) of CPU core# detection, DT cpu node will be
> the only way to do it right. So we need to add cpu nodes on the
> existing Tegra SoCs(T20/T30) first in order to remove the existing A9
> SCU detection later, where DT cpu# detection fails, we would consider
> a single cpu core avalable.
> 
> Tested only with T30.
> 
> Hiroshi Doyu (2):
>   ARM: tegra20: Add cpu node
>   ARM: tegra30: Add cpu node
> 
>  arch/arm/boot/dts/tegra20.dtsi |   29 +++++++++++++++++++++++++++++
>  arch/arm/boot/dts/tegra30.dtsi |   29 +++++++++++++++++++++++++++++
>  2 files changed, 58 insertions(+)
> 
> *1:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/140209.html
Looks ok, but you should copy devicetree-discuss at lists.ozlabs.org for
any set DT related.

FWIW on the series:

Reviewed-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>

      parent reply	other threads:[~2013-01-11 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 13:11 [PATCH 0/2] ARM: tegra: Add cpu node in device tree Hiroshi Doyu
2013-01-11 13:11 ` [PATCH 1/2] ARM: tegra20: Add cpu node Hiroshi Doyu
2013-01-11 13:26   ` [PATCH 1'/2] " Hiroshi Doyu
2013-01-11 18:13     ` Stephen Warren
2013-01-11 13:11 ` [PATCH 2/2] ARM: tegra30: " Hiroshi Doyu
2013-01-11 14:44 ` Lorenzo Pieralisi [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=20130111144449.GF30538@e102568-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).