Received: by 2002:a05:6358:4e97:b0:b3:742d:4702 with SMTP id ce23csp1562421rwb; Fri, 12 Aug 2022 03:10:11 -0700 (PDT) X-Google-Smtp-Source: AA6agR6VfAbIpaufNjKVTHhtMhSJFVyhNOapG+oO54Rljy/d5uKy5GrG+eWvHaYlB9/ZdPDWyfc7 X-Received: by 2002:a05:6402:280f:b0:43d:f946:a895 with SMTP id h15-20020a056402280f00b0043df946a895mr2962630ede.229.1660299011503; Fri, 12 Aug 2022 03:10:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1660299011; cv=none; d=google.com; s=arc-20160816; b=J5qlPnJUVAzADczWY1Nh2Zljbrfkskt5rchXcPj0Z3tSdDEd3RGDO/b/2FG/CMkgtu ++Q2pLx6fMZwUcDvsTqvg4vyySKwph89DOtkvwEKBSA7nHFgKGQ/UAholPiTGBR74jB4 6qMb9/n16o2v6Nl3Zid9mxDdpXZAgTWV4jg1LWz4GMbV3v1dKPeOf0P+X4YsxWTsw6df +jcdkUzZGP4aHldUaHsIXy4ShABZwsVwNedjq5u5q6xIczl47kFYnZUJHYLxknXHrTF4 xWxrjxbapSGX8ipYvSTPaWAfQM/yDk/v6T9q4BnMF+jC0N7XH6nNZCE76kPW6DQDNii2 ps8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=pGicgmrkVGpAXVpWBOOwVqoHRpuAuKtD+Wqhn/gpirk=; b=MMmHdzgRWBPZ7zeOUV+EeDH+BwACAmQboThbrd/8cBwG4OwFO2iujgVenc8M9TDDxp +som5kb2JhzX7TxsaQ+5dYpNJGwim0LbJG3lhrKaDBjGj/vhbEiL1xsaC7g0ja0bWDFV iKx7rK9H25G2K6G8U4Xe75l+HE5St5J01B7CSUmkpoA6dwWpCpA2kHmx6+FLb5ja9VqI 9rQ16kat4gSdkX3yhs3J8CVt78UR0tfJSnARebuTLu0uaxALuIBqhbbWVNVTEYjlUeEw sR3ZUpSMbNSIUUvVkqnlGzZbvD5zJleH5dd/ygdX/xb/zwHX7ni4L7I7zi0ciJQtX2cd dy2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=MN1hOu0M; 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=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k5-20020a17090666c500b0072b6e6512e5si1319657ejp.490.2022.08.12.03.09.45; Fri, 12 Aug 2022 03:10:11 -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=@linaro.org header.s=google header.b=MN1hOu0M; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237787AbiHLKH2 (ORCPT + 99 others); Fri, 12 Aug 2022 06:07:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56732 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237460AbiHLKH0 (ORCPT ); Fri, 12 Aug 2022 06:07:26 -0400 Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 01963832CD for ; Fri, 12 Aug 2022 03:07:25 -0700 (PDT) Received: by mail-lf1-x12c.google.com with SMTP id u1so705658lfq.4 for ; Fri, 12 Aug 2022 03:07:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=pGicgmrkVGpAXVpWBOOwVqoHRpuAuKtD+Wqhn/gpirk=; b=MN1hOu0MvGFfVSNI3SZCMYZgGjhChvjodGSJYoVCvE2Vlkb/G85d1rwBzHEKFU7BoE HNrF5VHtjbtSbVBlPWmrHGCzPLPHjYt5HXG7uLbVxTyFZwP0AzOHLXjZFICp8YmJprtC gX30SbRsIPIu632N0gevqC3jhBV22xnq7p5vafKxI8sgjHiquWCcPgq61ao8BCM1ZRLy fvl11FVIenCL2nYausoYZ3BTaXnAxZX5ZEy3RgIbsRCcA6U2BI3JgqfEKFq/6OYBXH2P 5IFQbe3/FiF9ph2qjFSK3Nc7prxcUEQrUR7BsYX/1ybOnFr7KYWEB/B3O4KvuP/4zQSt qtQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=pGicgmrkVGpAXVpWBOOwVqoHRpuAuKtD+Wqhn/gpirk=; b=2zm4G2xFMktqVige1vTN2+iwCvLK8tr0YQHMlqVm0n2FootdZ9GkjEc3zDA8y8fFlS NJS9wwToRx9H3f05HJSHQ8s6KHE439NApt5q0YvfnZnJBYjZVCgpalkoDA0PWCr48bHI piVFNQzKcF34ruw0gKM3nEKru3Lvwbcadtegj7q5jmQ3s+2vGjopLapBgasqxGp9cEb1 SNIZmOYDSRw1ATDARoZimBFDFjPveg3B+IR8BTEKVbeJpWoHoER2CYaqHTRsbU7Kiwf+ GFYhQUQek2pyk7hdnwaSuWoB1biB89BzN1rK6+hshunUkHx4zEp4RvVPeRgGyTdfOGKd hXQg== X-Gm-Message-State: ACgBeo3ZEF+2m8LuE+DJeF9aS/YFkAS+H+jDOwAcWsYKB5h69irZG9yb sTmwi2X3emcX00ZP24cCUSt44w== X-Received: by 2002:ac2:44bc:0:b0:48a:eb48:6b78 with SMTP id c28-20020ac244bc000000b0048aeb486b78mr1152514lfm.326.1660298842630; Fri, 12 Aug 2022 03:07:22 -0700 (PDT) Received: from [192.168.1.39] ([83.146.140.105]) by smtp.gmail.com with ESMTPSA id u28-20020ac251dc000000b0048a7c162bbesm155510lfm.279.2022.08.12.03.07.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 12 Aug 2022 03:07:22 -0700 (PDT) Message-ID: Date: Fri, 12 Aug 2022 13:07:16 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: [PATCH 3/4] dt-bindings: PCI: microchip,pcie-host: fix incorrect child node name Content-Language: en-US To: Conor.Dooley@microchip.com, mail@conchuod.ie, Daire.McNamara@microchip.com, bhelgaas@google.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, paul.walmsley@sifive.com, greentime.hu@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, lpieralisi@kernel.org Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org References: <20220811203306.179744-1-mail@conchuod.ie> <20220811203306.179744-4-mail@conchuod.ie> <721ccb76-c162-30ee-68cc-3316a2d62554@linaro.org> <272557c5-3e30-a873-40af-16a65c3043b2@microchip.com> From: Krzysztof Kozlowski In-Reply-To: <272557c5-3e30-a873-40af-16a65c3043b2@microchip.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 12/08/2022 10:55, Conor.Dooley@microchip.com wrote: > On 12/08/2022 08:42, Krzysztof Kozlowski wrote: >> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe >> >> On 11/08/2022 23:33, Conor Dooley wrote: >>> From: Conor Dooley >>> >>> v2022.08 of dt-schema improved checking of unevaluatedProperties, and >>> exposed a previously unseen warning for the PCIe controller's interrupt >>> controller node name: >>> >>> arch/riscv/boot/dts/microchip/mpfs-icicle-kit.dtb: pcie@2000000000: Unevaluated properties are not allowed ('clock-names', 'clocks', 'legacy-interrupt-controller', 'microchip,axi-m-atr0' were unexpected) >>> From schema: Documentation/devicetree/bindings/pci/microchip,pcie-host.yaml >>> >>> Make the property in the binding match the node name actually used in >>> the dts. >>> >>> Fixes: dcd49679fb3a ("dt-bindings: PCI: Fix 'unevaluatedProperties' warnings") >>> Signed-off-by: Conor Dooley >>> --- >>> This is another one Rob where I feel like I'm doing the wrong thing. >>> The Linux driver gets the child node without using the name, but >>> another OS etc could in theory (or reality), right? >> >> Yes and we had such cases when renaming device nodes caused regression. >> My interpretation is that node name is not part of ABI, so anyone >> depending on it made a mistake and they need to fix their stuff. I think >> actually that is really poor coding and poor solution to parse device >> node names and expect specific name. >> >> Other folks interpretation is that we never break the users of kernel, >> regardless what is documented in the ABI... so it depends. :) >> >> Here however it is not a device node name, but a property name (although >> still a node). Bindings require these to be specific, thus such name is >> a part of ABI. > > Yup, pretty much aligned to my thoughts on this. > >> For your case, I wonder why it was called "legacy-interrupt-controller" >> in the first place? Node names - also for properties - should be >> generic, so generic name is just "interrupt-controller". > > I don't know. It's what we had in our internal tree prior to upstreaming. > "We" don't rely on the name for the Linux driver, so I am not really that > bothered if we change the binding or the dts. Then I propose to change the name in DTS. Best regards, Krzysztof