public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 04/14] ARM: dts: armada-375: Fixup bootrom DT warning
Date: Thu, 10 Nov 2016 09:22:21 +0100	[thread overview]
Message-ID: <20161110092221.0219490b@free-electrons.com> (raw)
In-Reply-To: <20161110001000.10619-5-gregory.clement@free-electrons.com>

Hello,

On Thu, 10 Nov 2016 01:09:50 +0100, Gregory CLEMENT wrote:

> -		bootrom {
> +		bootrom at 0 {
>  			compatible = "marvell,bootrom";
>  			reg = <MBUS_ID(0x01, 0x1d) 0 0x100000>;

I am still not sure whether this "0" unit address is correct compared
to the reg property being passed.

A good example of why I'm worried is the sa-sram case:

+		crypto_sram0: sa-sram0 at 0 {
 			compatible = "mmio-sram";
 			reg = <MBUS_ID(0x09, 0x09) 0 0x800>;

+		crypto_sram1: sa-sram1 at 0 {
 			compatible = "mmio-sram";
 			reg = <MBUS_ID(0x09, 0x05) 0 0x800>;

The node names should be just "sram" without a number. Indeed for UARTs
for example, you use uart at XYZ, uart at ABC and not uart0 at XYZ and
uart1 at ABC. But then, if you do that, with your scheme, you end up with
both nodes named sa-sram at 0.

Which clearly shows that the way you set this unit-address is not
correct: those two devices are mapped at completely different
locations, but you end up with an identical unit address.

I have no idea what is the rule for setting the unit address in this
case, but I'm pretty sure the rule you've chosen is not good.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-11-10  8:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10  0:09 [PATCH 00/14] Various Armada 375 DT warning fixup Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 01/14] ARM: dts: armada-375: Add node labels Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 02/14] ARM: dts: armada-375: Use the " Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 03/14] ARM: dts: armada-375: Fixup mdio DT warning Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 04/14] ARM: dts: armada-375: Fixup bootrom " Gregory CLEMENT
2016-11-10  8:22   ` Thomas Petazzoni [this message]
2016-11-10  9:36     ` Gregory CLEMENT
2016-11-10 10:15       ` Thomas Petazzoni
2016-11-10 10:43         ` Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 05/14] ARM: dts: armada-375: Fixup devbus " Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 06/14] ARM: dts: armada-375: Fixup sa-ram " Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 07/14] ARM: dts: armada-375: Fixup pcie DT warnings Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 08/14] " Gregory CLEMENT
2016-11-10  0:22   ` Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 09/14] ARM: dts: armada-375: Fixup pinctrl " Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 10/14] ARM: dts: armada-375: Fixup soc DT warning Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 11/14] ARM: dts: armada-375: Fixup internal-regs " Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 12/14] ARM: dts: armada-375: Remove skeleton.dtsi Gregory CLEMENT
2016-11-10  0:09 ` [PATCH 13/14] ARM: dts: armada-375: Fixup memory DT warning Gregory CLEMENT
2016-11-10  0:10 ` [PATCH 14/14] ARM: dts: armada-375: Fixup ethernet child " Gregory CLEMENT

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=20161110092221.0219490b@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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