From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Olof Johansson" <olof@lixom.net>,
"Masami Hiramatsu" <mhiramat@kernel.org>
Cc: soc@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: uniphier: Add NX1 SoC and boards support
Date: Thu, 27 Oct 2022 12:01:15 +0200 [thread overview]
Message-ID: <b3c4f9ec-ba8e-4af1-b347-e07b06530d6c@app.fastmail.com> (raw)
In-Reply-To: <20221027045157.23325-5-hayashi.kunihiko@socionext.com>
On Thu, Oct 27, 2022, at 06:51, Kunihiko Hayashi wrote:
> Initial version of devicetree sources for NX1 SoC and boards.
>
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Can you add more information here? When new SoCs get added, I
usually provide more than this in my own pull requests sending
the patches to Linus, so please add some background here, such as:
- is this a new SoC, or or something that has been around for a while
and only now gets upstreamed?
- What is the target market for this SoC? Are there any products
one can buy with it?
- What type of CPU cores does it use, or any other noteworthy
IP blocks that are relevant for its purpose?
> + usb_hsphy0: hs-phy@200 {
> + compatible = "socionext,uniphier-nx1-usb3-hsphy";
> + reg = <0x200 0x10>;
> + usb_ssphy0: ss-phy@300 {
> + compatible = "socionext,uniphier-nx1-usb3-ssphy";
> + reg = <0x300 0x10>;
I think these are usually just named 'phy@' instead of 'hs-phy@'
> + ranges =
> + /* downstream I/O */
> + <0x81000000 0 0x00000000 0x0ffe0000 0 0x00010000>,
> + /* non-prefetchable memory */
> + <0x82000000 0 0x20000000 0x04200000 0 0x0bde0000>;
200MB of memory space is rather small, is there no 64-bit range?
> + #interrupt-cells = <1>;
> + interrupt-names = "dma", "msi";
> + interrupts = <GIC_SPI 84 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 85 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0 0 0 1 &pcie_intc 0>, /* INTA */
> + <0 0 0 2 &pcie_intc 1>, /* INTB */
> + <0 0 0 3 &pcie_intc 2>, /* INTC */
> + <0 0 0 4 &pcie_intc 3>; /* INTD */
> + phy-names = "pcie-phy";
> + phys = <&pcie_phy>;
> +
> + pcie_intc: legacy-interrupt-controller {
> + interrupt-controller;
> + #interrupt-cells = <1>;
> + interrupt-parent = <&gic>;
> + interrupts = <GIC_SPI 86 IRQ_TYPE_LEVEL_HIGH>;
> + };
> + };
Shouldn't there be an "msi-map" or "msi-parent" property pointing at
the GIC?
Arnd
next prev parent reply other threads:[~2022-10-27 10:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 4:51 [PATCH 0/4] Add UniPhier " Kunihiko Hayashi
2022-10-27 4:51 ` [PATCH 1/4] dt-bindings: arm: uniphier: Add Pro5 boards Kunihiko Hayashi
2022-10-27 13:28 ` Krzysztof Kozlowski
2022-10-27 4:51 ` [PATCH 2/4] ARM: dts: uniphier: Add Pro5 board support Kunihiko Hayashi
2022-10-27 4:51 ` [PATCH 3/4] dt-bindings: arm: uniphier: Add NX1 boards Kunihiko Hayashi
2022-10-27 13:29 ` Krzysztof Kozlowski
2022-10-27 4:51 ` [PATCH 4/4] arm64: dts: uniphier: Add NX1 SoC and boards support Kunihiko Hayashi
2022-10-27 10:01 ` Arnd Bergmann [this message]
2022-10-27 11:19 ` Kunihiko Hayashi
2022-10-27 11:28 ` Arnd Bergmann
2022-10-27 11:58 ` Kunihiko Hayashi
2022-10-27 12:19 ` Arnd Bergmann
2022-10-27 13:36 ` Krzysztof Kozlowski
2022-11-01 9:02 ` Kunihiko Hayashi
2022-11-02 16:48 ` Krzysztof Kozlowski
2022-11-04 5:57 ` Kunihiko Hayashi
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=b3c4f9ec-ba8e-4af1-b347-e07b06530d6c@app.fastmail.com \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.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
all inboxes | Powered by JetHome®