linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] ARM: tegra: Add initial device tree for Tegra124
Date: Mon, 07 Oct 2013 11:18:55 -0600	[thread overview]
Message-ID: <5252ECFF.404@wwwdotorg.org> (raw)
In-Reply-To: <1381131085-26116-5-git-send-email-josephl@nvidia.com>

On 10/07/2013 01:31 AM, Joseph Lo wrote:
> Initial support for Tegra 124 SoC. This is expected to be included in
> the board DTS files.

> diff --git a/arch/arm/boot/dts/tegra124.dtsi b/arch/arm/boot/dts/tegra124.dtsi

> +	rtc {
> +		compatible = "nvidia,tegra124-rtc", "nvidia,tegra20-rtc";
> +		reg = <0x7000e000 0x100>;

We recently decided that all nodes that have a reg property must have a
matching unit address in the node name. Hence, the node should be named
"rtc at 7000e000" not just "rtc". We haven't decided how to clean this up
for existing DTs, but I'd like to enforce the new rule for all new DTs.

The pmc node should also be fixed.

> +	pmc {
> +		compatible = "nvidia,tegra124-pmc", "nvidia,tegra114-pmc";
> +		reg = <0x7000e400 0x400>;
> +	};

Is the Tegra124 PMC really identical to the Tegra114 PMC in hardware?
That would be a departure from history, where the PMC has changed
significantly and incompatibly for each chip. Can you please investigate
the details of the PMC changes; I suspect this should simply be:

		compatible = "nvidia,tegra124-pmc";

  reply	other threads:[~2013-10-07 17:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07  7:31 [PATCH 0/7] ARM: tegra: basic support for Tegra124 SoC Joseph Lo
2013-10-07  7:31 ` [PATCH 1/7] ARM: tegra: add Tegra124 SoC support Joseph Lo
2013-10-07  7:31 ` [PATCH 2/7] ARM: tegra: add chip ID of Tegra124 Joseph Lo
2013-10-07  7:31 ` [PATCH 3/7] ARM: tegra: add SMP support for Tegra124 Joseph Lo
2013-10-07 17:19   ` Stephen Warren
2013-10-07  7:31 ` [PATCH 4/7] ARM: tegra: Add initial device tree " Joseph Lo
2013-10-07 17:18   ` Stephen Warren [this message]
2013-10-08  1:21     ` Joseph Lo
2013-10-07  7:31 ` [PATCH 5/7] ARM: tegra: add Venice2 board support Joseph Lo
2013-10-07 17:20   ` Stephen Warren
2013-10-07  7:31 ` [PATCH 6/7] HACK: arm: tegra: reuse the Tegra114 clock driver for Tegra124 UART-A Joseph Lo
2013-10-07  7:31 ` [PATCH 7/7] ARM: tegra: enable Tegra124 support Joseph Lo
2013-10-07 18:13 ` [PATCH 0/7] ARM: tegra: basic support for Tegra124 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=5252ECFF.404@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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).