Received: by 2002:a05:7412:b130:b0:e2:908c:2ebd with SMTP id az48csp680101rdb; Fri, 17 Nov 2023 09:33:04 -0800 (PST) X-Google-Smtp-Source: AGHT+IGn+HuKc85MShmLNDyt9ldSEV6ju6k1B62rStz9dqAVOQBJhKUPrFHAek8/fnRQMKnqyTDa X-Received: by 2002:a05:6a21:187:b0:17e:2afd:407b with SMTP id le7-20020a056a21018700b0017e2afd407bmr27183401pzb.9.1700242384504; Fri, 17 Nov 2023 09:33:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700242384; cv=none; d=google.com; s=arc-20160816; b=K42xasM/+HFjCxlpYVTLvj8jajorKWoAlfGt/PM7ZO3Hdp2P6mBMEogWt8izKkPMxq ZZGgCiy7LeauvYZgxh45lmWHyj28Xe/QUlmaTb5r9vtXOyX6VCDd7+51Si9/u4bdVv4e PPrPvc2vjUYhbCLoqgUHXyeNah39DOqF60Tdc46DtRZ8j6aDf+ZBYsvV9xab2hS6j4m0 HS0vqXBO/TvE61b0K9qsIH0QbnPZfM+9bdPhqqVaYuO7mrQjGfMrPTBwWcKNX272ip/f xpNTLealQe4+J6CccsLv1XhTbnXZh7UfagqHsndQbH8JXB4D/nnsrO7kNW+ZUE4bGHTd CbXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:date:subject:message-id:references:in-reply-to :cc:to:from:mime-version:content-transfer-encoding; bh=4S/ec2GwXMEDgodu8Dp1Lk3HdoFb4k1XivOumHh1GgI=; fh=3zocvSl4oB0JGITx+dKSdSfgdtDLyxbOAZj6muSZfxM=; b=GbdlEB3m45Cj0eDrcHnbCpDjOUDtKn1OP+R/Gx6y1HACGOvAiVfhhXWRo8Znmef+K3 wof/LqmMfh5lX1ABeXhgQIc+RMjVHyYIs4qaTZRy3G8O1TC1WtUAgLWagi66jC2YZeQP dXSNWwqMvHpiP3iZiBGMvbcW+VgLE4CCfRw4S4gnjyPGn+2iy3Lju9RVPdqn2W6QHnvS u/ki/DwyC3xFnhATkfzrc/XUrK7YbVCvpt+5ZeD+IJyjKMbXsMyk7QT3eZ8wZEGI4PHG 8e+6a/fTZ1bXRdyPTZ7e8i/4cjbUVOzvLxHxaJT3nF7diAVKZV67tPofpGZd286j+5N/ p/iw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 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 fry.vger.email (fry.vger.email. [2620:137:e000::3:8]) by mx.google.com with ESMTPS id b5-20020a63eb45000000b005b3b8896199si2132450pgk.591.2023.11.17.09.32.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 Nov 2023 09:33:04 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id E46D1802193C; Fri, 17 Nov 2023 09:32:53 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232105AbjKQRcn (ORCPT + 99 others); Fri, 17 Nov 2023 12:32:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38026 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230186AbjKQRcm (ORCPT ); Fri, 17 Nov 2023 12:32:42 -0500 Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com [209.85.210.49]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 31150A5; Fri, 17 Nov 2023 09:32:39 -0800 (PST) Received: by mail-ot1-f49.google.com with SMTP id 46e09a7af769-6d261cb07dcso1321573a34.3; Fri, 17 Nov 2023 09:32:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700242358; x=1700847158; h=date:subject:message-id:references:in-reply-to:cc:to:from :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=4S/ec2GwXMEDgodu8Dp1Lk3HdoFb4k1XivOumHh1GgI=; b=gdgDqxoCfr/SowEUZC+Vkbzn+lDlac5zw1OA1/i9JRFuBLAnaySAYCKjLxyKiZ36Ws M7F3/jUXfj3OmJSlU6q7TOXELPxDjzhiRjfT4F2VxZXMwExBrdtZSzgt/FXYCxCjll7u 8dW77SdiV0Oks91uVdEFA6WMYiruJs1wHHkd/cPggF/v7kT3HU2J37NCMvpLf4K4I7l4 R9aJRqMmaLfcJ1Eje8ysvED/c4hD6jrAs/cBVXA/dY1kbvArOs8DWe9mYcCKn8JPYakl AkOaiaKcLajPlMTyHfovZsKaU3gmGURDCRszPZd1PpyRcwc2DAKTM+x21ZESVVkNg9R1 MC8g== X-Gm-Message-State: AOJu0YzLuhY5LipgKLCkkkf9/scLkUZnegg13JkPCOrPPEympgZEkVia 0zT/ipsgmw/cqTY4rHVr0h3RpINTFQ== X-Received: by 2002:a05:6830:20b:b0:6d6:4c54:72e4 with SMTP id em11-20020a056830020b00b006d64c5472e4mr12715956otb.36.1700242358397; Fri, 17 Nov 2023 09:32:38 -0800 (PST) Received: from herring.priv (66-90-144-107.dyn.grandenetworks.net. [66.90.144.107]) by smtp.gmail.com with ESMTPSA id b26-20020a9d755a000000b006ce2c31dd9bsm303819otl.20.2023.11.17.09.32.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 Nov 2023 09:32:36 -0800 (PST) Received: (nullmailer pid 1869910 invoked by uid 1000); Fri, 17 Nov 2023 17:32:33 -0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Rob Herring To: James Tai Cc: linux-kernel@vger.kernel.org, Rob Herring , Thomas Gleixner , Marc Zyngier , Krzysztof Kozlowski , devicetree@vger.kernel.org, Conor Dooley In-Reply-To: <20231117162709.1096585-2-james.tai@realtek.com> References: <20231117162709.1096585-1-james.tai@realtek.com> <20231117162709.1096585-2-james.tai@realtek.com> Message-Id: <170024235327.1869893.15173077111056096496.robh@kernel.org> Subject: Re: [PATCH v2 1/6] dt-bindings: interrupt-controller: Add support for Realtek DHC SoCs Date: Fri, 17 Nov 2023 11:32:33 -0600 X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Fri, 17 Nov 2023 09:32:54 -0800 (PST) On Sat, 18 Nov 2023 00:27:04 +0800, James Tai wrote: > Add the YAML documentation for Realtek DHC SoCs. > > CC: Thomas Gleixner > CC: Marc Zyngier > CC: Rob Herring > CC: Krzysztof Kozlowski > CC: Conor Dooley > CC: linux-kernel@vger.kernel.org > CC: devicetree@vger.kernel.org > Signed-off-by: James Tai > --- > v1 to v2 change: > - Tested the bindings using 'make dt_binding_check' > - Fixed code style issues > > .../realtek,rtd1319-intc.yaml | 79 +++++++++++++++++++ > .../realtek,rtd1319d-intc.yaml | 79 +++++++++++++++++++ > .../realtek,rtd1325-intc.yaml | 79 +++++++++++++++++++ > .../realtek,rtd1619b-intc.yaml | 78 ++++++++++++++++++ > 4 files changed, 315 insertions(+) > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/realtek,rtd1319-intc.yaml > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/realtek,rtd1319d-intc.yaml > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/realtek,rtd1325-intc.yaml > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/realtek,rtd1619b-intc.yaml > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' on your patch (DT_CHECKER_FLAGS is new in v5.13): yamllint warnings/errors: dtschema/dtc warnings/errors: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd1319d-intc.yaml: title: 'Realtek DHC RTD1319D Interrupt Controller Device Tree Bindings' should not be valid under {'pattern': '([Bb]inding| [Ss]chema)'} hint: Everything is a binding/schema, no need to say it. Describe what hardware the binding is for. from schema $id: http://devicetree.org/meta-schemas/base.yaml# /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd1325-intc.yaml: title: 'Realtek DHC RTD1325 Interrupt Controller Device Tree Bindings' should not be valid under {'pattern': '([Bb]inding| [Ss]chema)'} hint: Everything is a binding/schema, no need to say it. Describe what hardware the binding is for. from schema $id: http://devicetree.org/meta-schemas/base.yaml# /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd1619b-intc.yaml: title: 'Realtek DHC RTD1619B Interrupt Controller Device Tree Bindings' should not be valid under {'pattern': '([Bb]inding| [Ss]chema)'} hint: Everything is a binding/schema, no need to say it. Describe what hardware the binding is for. from schema $id: http://devicetree.org/meta-schemas/base.yaml# /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd1319-intc.yaml: title: 'Realtek DHC RTD1319 Interrupt Controller Device Tree Bindings' should not be valid under {'pattern': '([Bb]inding| [Ss]chema)'} hint: Everything is a binding/schema, no need to say it. Describe what hardware the binding is for. from schema $id: http://devicetree.org/meta-schemas/base.yaml# doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20231117162709.1096585-2-james.tai@realtek.com The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.