From: Krzysztof Kozlowski <krzk@kernel.org>
To: Claudiu <claudiu.beznea@tuxon.dev>,
bhelgaas@google.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, geert+renesas@glider.be,
magnus.damm@gmail.com, p.zabel@pengutronix.de
Cc: linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH v4 1/6] dt-bindings: PCI: renesas,r9a08g045s33-pcie: Add documentation for the PCIe IP on Renesas RZ/G3S
Date: Fri, 12 Sep 2025 15:41:04 +0200 [thread overview]
Message-ID: <d40011bb-8e03-402e-b343-7331d51e2427@kernel.org> (raw)
In-Reply-To: <20250912122444.3870284-2-claudiu.beznea.uj@bp.renesas.com>
On 12/09/2025 14:24, Claudiu wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> The PCIe IP available on the Renesas RZ/G3S complies with the PCI Express
> Base Specification 4.0. It is designed for root complex applications and
> features a single-lane (x1) implementation. Add documentation for it.
>
> Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
You cannot really test bindings in that meaning and build tools don't
count as testing, just like building C code is not testing, running
sparse is not testing, checking with coccinelle is not testing.
And it cannot be tested even in the meaning of building, because:
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> ---
...
> + interrupt-controller;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0 0 0 1 &pcie 0 0 0 0>, /* INTA */
> + <0 0 0 2 &pcie 0 0 0 1>, /* INTB */
> + <0 0 0 3 &pcie 0 0 0 2>, /* INTC */
> + <0 0 0 4 &pcie 0 0 0 3>; /* INTD */
> + clocks = <&cpg CPG_MOD R9A08G045_PCI_ACLK>,
> + <&cpg CPG_MOD R9A08G045_PCI_CLKL1PM>;
> + clock-names = "aclk", "pm";
> + resets = <&cpg R9A08G045_PCI_ARESETN>,
> + <&cpg R9A08G045_PCI_RST_B>,
> + <&cpg R9A08G045_PCI_RST_GP_B>,
> + <&cpg R9A08G045_PCI_RST_PS_B>,
> + <&cpg R9A08G045_PCI_RST_RSM_B>,
> + <&cpg R9A08G045_PCI_RST_CFG_B>,
> + <&cpg R9A08G045_PCI_RST_LOAD_B>;
> + reset-names = "aresetn", "rst_b", "rst_gp_b", "rst_ps_b",
> + "rst_rsm_b", "rst_cfg_b", "rst_load_b";
> + power-domains = <&cpg>;
> + device_type = "pci";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + max-link-speed = <2>;
> + renesas,sysc = <&sysc>;
> + status = "disabled";
...you disabled the example.
I don't understand what happened here - why this got now disabled.
Code was correct before, but you made so many changes including this one.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-12 13:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 12:24 [PATCH v4 0/6] PCI: rzg3s-host: Add PCIe driver for Renesas RZ/G3S SoC Claudiu
2025-09-12 12:24 ` [PATCH v4 1/6] dt-bindings: PCI: renesas,r9a08g045s33-pcie: Add documentation for the PCIe IP on Renesas RZ/G3S Claudiu
2025-09-12 13:41 ` Krzysztof Kozlowski [this message]
2025-09-12 13:45 ` Claudiu Beznea
2025-09-12 12:24 ` [PATCH v4 2/6] PCI: rzg3s-host: Add Renesas RZ/G3S SoC host driver Claudiu
2025-09-19 8:45 ` Manivannan Sadhasivam
2025-09-19 9:28 ` Claudiu Beznea
2025-09-29 17:35 ` Manivannan Sadhasivam
2025-09-12 12:24 ` [PATCH v4 3/6] arm64: dts: renesas: r9a08g045: Add PCIe node Claudiu
2025-09-26 9:45 ` Geert Uytterhoeven
2025-09-12 12:24 ` [PATCH v4 4/6] arm64: dts: renesas: rzg3s-smarc-som: Update dma-ranges for PCIe Claudiu
2025-09-18 9:09 ` Geert Uytterhoeven
2025-09-18 9:47 ` Claudiu Beznea
2025-09-18 10:00 ` Geert Uytterhoeven
2025-09-19 7:38 ` Claudiu Beznea
2025-09-19 7:53 ` Biju Das
2025-09-19 8:25 ` Manivannan Sadhasivam
2025-09-19 8:48 ` Claudiu Beznea
2025-09-12 12:24 ` [PATCH v4 5/6] arm64: dts: renesas: rzg3s-smarc: Enable PCIe Claudiu
2025-09-26 9:49 ` Geert Uytterhoeven
2025-09-12 12:24 ` [PATCH v4 6/6] arm64: defconfig: Enable PCIe for the Renesas RZ/G3S SoC Claudiu
2025-09-12 13:41 ` Krzysztof Kozlowski
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=d40011bb-8e03-402e-b343-7331d51e2427@kernel.org \
--to=krzk@kernel.org \
--cc=bhelgaas@google.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mani@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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