Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp17718289rwd; Tue, 27 Jun 2023 06:50:58 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7Tk/3beciiuE4VCgeVF2F6izzzwzWmOEm+6xJZLBPshYsEICN8Wp2FP+oPHxwJmUUgissk X-Received: by 2002:a05:6e02:4c3:b0:345:a757:a4a0 with SMTP id f3-20020a056e0204c300b00345a757a4a0mr6741149ils.27.1687873858661; Tue, 27 Jun 2023 06:50:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687873858; cv=none; d=google.com; s=arc-20160816; b=jOPvCBac5R5QEzrSs60zBJxSraX3vuOjlhU1vYiVBwJ+QuxQCy0Mo7quSifoGr3Kh+ +SJSNYnZeYGep40rxrenzmvOdx4tLj3vUg8ZmhlCD3kqZfv2RynzzV/92VwIfjhoL834 SRvY9Oint5830JItmNZwTB3LZEgzc6tHFymgmYXb7w2VCouURP9Vbem6iYH4/HbZ1FqT luRlpBNqx9kovsAtfKfL9XkcGjSed/Ccoj+sIw9L5NQGdeGsZrDQaAREv+vYkSmJBKWm oDBBz2RNjcUM/o8l3aV3of5kXnUS33QoecvS4wqUWDn0chEf1gPA3D1XQZDLBr6R2Rg2 56KQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=xa4JHpiDvQHEdCvXMSDLdrdz2MSIS66TffASO01NTCg=; fh=jBn7C8u6Y+UxLs3vO0cWK2nEmgEJmtBdTSr3k3uvtv4=; b=yUrvaRdxaF/R8oQDRJAaU0YQk0HwbILokBAAMLn8ITgJ0BMApMs7gW77Dy740QUS2B x0uteC6jDCcPJXmePOZs7rLHctCl5BqliloVL9KX7TNVcQWgr1Q4EYaG4apvNsu5GQCR 3R9Paunb+htHsyipzEXypwhcPz11LaPYaL2CXu+ojSG5NAIfehFOVk6gTZON1Eyj9Q6T BQE8rdH6V0o0R0d580hDwMvf30WVZN5NAvnuFAaJmfZFLeq+4JTbVkdefHCUi5Ql2AGx QNmnSaVei56CA3FJy3osj7TwlHFHbS4X8poGsgGw3bbpudMbwyLTVzpnXBi5kVDtwC7g UTJg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=L51bvRo3; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 201-20020a6302d2000000b0055adfd71daesi4352682pgc.663.2023.06.27.06.50.45; Tue, 27 Jun 2023 06:50:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=L51bvRo3; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231218AbjF0Ns4 (ORCPT + 99 others); Tue, 27 Jun 2023 09:48:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44962 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231183AbjF0Nsv (ORCPT ); Tue, 27 Jun 2023 09:48:51 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9477A296B; Tue, 27 Jun 2023 06:48:47 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 230DA611AB; Tue, 27 Jun 2023 13:48:47 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7BE2AC433CA; Tue, 27 Jun 2023 13:48:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1687873726; bh=mObELhIa7cwUVV/oIDNa5An5fXRPEinl+dDJGvds3Nc=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=L51bvRo3oGBkGU3bYcUoxBi7qn+NBS181faXZyiA+mjcHOLWAVCr3vgHqTrqbzGBQ 30OTwDS0JSOAiLcEqhE4pFGIsNHahwmRQmJPtUewXfu/gR9wKpeIfXiyPraZG7Z60J zgf00meR3swepOPrA3FOV8I0GsUgmhpFuxJZBv2+BoNuiH4I61qnrDjmjrcKIA/JZB ow66V3Jogu1L9blAYv3JNW41bMhfWTVYCVmk1s2hlP8DYAH6YPqsZVIb3yHd5RIvkv WAvGB74OXpKMUifH2ZLpFkzPcrMrYLVBSK/iRwFRPkARZsPzEg1SpyjRevjogb2YKB IiiYpcBwJkMag== Received: by mail-lj1-f181.google.com with SMTP id 38308e7fff4ca-2b698371937so46831491fa.3; Tue, 27 Jun 2023 06:48:46 -0700 (PDT) X-Gm-Message-State: AC+VfDwgYLbMSOsduqnnP6w+mzQwyG08fmo7GhROgTZIqHk9VDUW14rO T4JYQwHNRGRPZBvtSxLm2hdDsTH8O/pDWrtJ/Q== X-Received: by 2002:a2e:7a06:0:b0:2b6:97e6:93f5 with SMTP id v6-20020a2e7a06000000b002b697e693f5mr4452783ljc.11.1687873724458; Tue, 27 Jun 2023 06:48:44 -0700 (PDT) MIME-Version: 1.0 References: <20230616170022.76107-1-sebastian.reichel@collabora.com> <20230616170022.76107-2-sebastian.reichel@collabora.com> In-Reply-To: From: Rob Herring Date: Tue, 27 Jun 2023 07:48:29 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v1 1/4] dt-bindings: PCI: dwc: rockchip: Fix interrupt-names issue To: Serge Semin , Sebastian Reichel Cc: Krzysztof Kozlowski , =?UTF-8?Q?Krzysztof_Wilczy=C5=84ski?= , linux-pci@vger.kernel.org, linux-rockchip@lists.infradead.org, Jingoo Han , Gustavo Pimentel , Bjorn Helgaas , Lorenzo Pieralisi , Conor Dooley , Heiko Stuebner , Shawn Lin , Simon Xue , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel@collabora.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 27, 2023 at 6:27=E2=80=AFAM Serge Semin wrote: > > On Fri, Jun 16, 2023 at 07:00:19PM +0200, Sebastian Reichel wrote: > > The RK356x (and RK3588) have 5 ganged interrupts. For example the > > "legacy" interrupt combines "inta/intb/intc/intd" with a register > > providing the details. > > > > Currently the binding is not specifying these interrupts resulting > > in a bunch of errors for all rk356x boards using PCIe. > > > > Fix this by specifying the interrupts and add them to the example > > to prevent regressions. > > > > Signed-off-by: Sebastian Reichel > > --- > > .../bindings/pci/rockchip-dw-pcie.yaml | 18 ++++++++++++++++++ > > .../devicetree/bindings/pci/snps,dw-pcie.yaml | 15 ++++++++++++++- > > 2 files changed, 32 insertions(+), 1 deletion(-) > > > > diff --git a/Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yam= l b/Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml > > index 24c88942e59e..98e45d2d8dfe 100644 > > --- a/Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml > > +++ b/Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml > > @@ -56,6 +56,17 @@ properties: > > - const: pclk > > - const: aux > > > > + interrupts: > > + maxItems: 5 > > + > > + interrupt-names: > > + items: > > + - const: sys > > + - const: pmc > > + - const: msg > > + - const: legacy > > + - const: err > > + > > msi-map: true > > > > num-lanes: true > > @@ -98,6 +109,7 @@ unevaluatedProperties: false > > > > examples: > > - | > > + #include > > > > bus { > > #address-cells =3D <2>; > > @@ -117,6 +129,12 @@ examples: > > "aclk_dbi", "pclk", > > "aux"; > > device_type =3D "pci"; > > + interrupts =3D , > > + , > > + , > > + , > > + ; > > + interrupt-names =3D "sys", "pmc", "msg", "legacy", "err"; > > linux,pci-domain =3D <2>; > > max-link-speed =3D <2>; > > msi-map =3D <0x2000 &its 0x2000 0x1000>; > > diff --git a/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml b/= Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml > > index 1a83f0f65f19..9f605eb297f5 100644 > > --- a/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml > > +++ b/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml > > @@ -193,9 +193,22 @@ properties: > > oneOf: > > - description: See native "app" IRQ for details > > enum: [ intr ] > > The IRQs below are either combined version of the already defined IRQs > or just the generic DW PCIe IRQs but named differently. Moreover I > don't see kernel using any of them except the "legacy" interrupt. What > about converting the dts files to using the already defined names instead > of extending the already over-diverged DT-bindings? > Rob, Krzysztof? If there's not a dependency on the names, then we can get away with changing them. Otherwise, it's an ABI issue to change them. Supporting both names in the driver partially mitigates that, but isn't worth carrying that IMO. Will drop this one from my tree. Seems patches 2 and 3 aren't dependent on this one. Rob