devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Hawkins, Nick" <nick.hawkins@hpe.com>
Cc: "Verdun, Jean-Marie" <verdun@hpe.com>,
	"Jean Delvare" <jdelvare@suse.com>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Rob Herring" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Russell King" <linux@armlinux.org.uk>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 3/5] ARM: dts: add GXP Support for fans and SPI
Date: Thu, 12 Jan 2023 22:57:13 +0100	[thread overview]
Message-ID: <83f5fc9f-4b46-4ac4-ba65-455d0aaaed88@app.fastmail.com> (raw)
In-Reply-To: <1E4BFECB-D29A-43CE-A521-F2A81939202F@hpe.com>

On Thu, Jan 12, 2023, at 20:58, Hawkins, Nick wrote:

> The updated section of the device tree will be:
>
> ahb@80000000 {
>                         compatible = "simple-bus";
>                         #address-cells = <1>;
>                         #size-cells = <1>;
>                         ranges = <0x0 0x80000000 0xf000000>, /* 
> 0x80000000 - 0x8f000000 */
>                                  <0x40000000 0xc0000000 0x40000000>; /* 
> 0xc0000000 - 0xffffffff */
>                         dma-ranges;

Ok

>
>                       ...
>
>                        vic0: interrupt-controller@4eff0000 { /* 0xceff0000 */
>                                 compatible = "arm,pl192-vic";
>                                 reg = <0x4eff0000 0x1000>;
>                                 interrupt-controller;
>                                 #interrupt-cells = <1>;
>                         };
>
>                         vic1: interrupt-controller@f00000 { /* 0x80f00000 */
>                                 compatible = "arm,pl192-vic";
>                                 reg = <0xf00000 0x1000>;
>                                 interrupt-controller;
>                                 #interrupt-cells = <1>;
>                         };

I still don't see the value of the /* 0x80f00000 */ comments,
you should define the ranges to the most sensible mapping
based on the datasheet so you don't need the comments.

If the datasheet uses a bus-local address (0xf00000), then
just get rid of the comment, since that only adds confusion.
OTOH if the 0x80f00000 number is what is in the datasheet,
then adjust the ranges to do a 1:1 mapping of the registers
on the bus and use that address directly.

      Arnd

  reply	other threads:[~2023-01-12 22:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 20:36 [PATCH v4 0/5] ARM: Add GXP Fan and SPI controllers nick.hawkins
2023-01-03 20:36 ` [PATCH v4 1/5] hwmon: (gxp-fan-ctrl) Add GXP fan controller nick.hawkins
2023-01-03 21:34   ` Guenter Roeck
2023-01-03 20:36 ` [PATCH v4 2/5] dt-bindings: hwmon: Add hpe,gxp-fan-ctrl nick.hawkins
2023-01-03 21:35   ` Guenter Roeck
2023-01-03 20:36 ` [PATCH v4 3/5] ARM: dts: add GXP Support for fans and SPI nick.hawkins
2023-01-03 21:37   ` Guenter Roeck
2023-01-12 14:24   ` Arnd Bergmann
2023-01-12 15:40     ` Hawkins, Nick
2023-01-12 16:00       ` Arnd Bergmann
2023-01-12 19:58         ` Hawkins, Nick
2023-01-12 21:57           ` Arnd Bergmann [this message]
2023-01-03 20:36 ` [PATCH v4 4/5] ARM: multi_v7_defconfig: Add GXP Fan and SPI support nick.hawkins
2023-01-03 21:38   ` Guenter Roeck
2023-01-12 14:29     ` Arnd Bergmann
2023-01-03 20:36 ` [PATCH v4 5/5] MAINTAINERS: add gxp fan controller and documents nick.hawkins
2023-01-03 21:36   ` Guenter Roeck

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=83f5fc9f-4b46-4ac4-ba65-455d0aaaed88@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=nick.hawkins@hpe.com \
    --cc=robh+dt@kernel.org \
    --cc=verdun@hpe.com \
    /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).