From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B8A88C4345F for ; Wed, 24 Apr 2024 20:36:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Subject:Message-Id:References: In-Reply-To:Cc:To:From:MIME-Version:Date:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Owner; bh=zce4/fLcnSnB1djOGUi+Zvm0ZIbDHRgIHnji6oSrdq4=; b=R6xR6LIcw5J45hc7oR3hDpBghY 0PobgP6WqG/iNkbdHhQPhm+Vo/eblRVuGPCA2JwYHtu5qYEKZZTYMDk9gx0GIMXb9QU3Bd9Zuzlqw 4NuZRs7n2EpWUW39jRQGViXkjebxPXLwQz3vlXud1GKQhPPci23Uny3H+1CKJr3dqSIWZKBBD65Rq 13YMtp/allUI5oCAFYTCTg065rgrlv3fgYv+4X7N9jcCeYTsAe6RqP1afMD0y/dgbTV5ZgHBrdNAb hoG/vG+/M+YBE8JwxnEv/wJLKAk55yp5FBkiQsdDtyyM87XTlWoX4ratIx6TwdHmcdZ/90xLJTBzD oFLUx9qA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rzjME-00000005x5J-3sc4; Wed, 24 Apr 2024 20:36:46 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rzjMB-00000005x2N-12nM for linux-arm-kernel@lists.infradead.org; Wed, 24 Apr 2024 20:36:45 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 9155ACE1861; Wed, 24 Apr 2024 20:36:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 79479C2BD11; Wed, 24 Apr 2024 20:36:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1713991000; bh=UEgXZYAvAoXydEPAsKWLpvLdEps8+VNW/bTxW6GL48Q=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=VmnTXxNbqN8kryduvL4VwlkwONiI33c3dkmk3fq69bO/O4Wo6P3yC8OwE6d+lcA/r UHz8wdD8gvoIk2EefN5xKUtZERsYZr03gutChcHXVRIE3YznyepTqY7bhT2Bmvr/xB xdh2cU7+xGMiIep3JrOrvWABxaLmeaZZPrKtNfRfqQmqZCmjkfFkTEt1CZLYrSenT2 sZr5RfS3uKdTLD5lxekFbIhNoGm2aQPmj7LeR1Z8+s1IHTto8k+lgSgAJVZHZnN5Mu kxDZC+Qi+70sN2x5exaHfQnmFPkPzu8frFTGaq75d01E+pMetSgSo2ehK1MfMT2TVT 9+Vt1zYmkD3xA== Date: Wed, 24 Apr 2024 15:36:39 -0500 MIME-Version: 1.0 From: Rob Herring To: Andrew Davis Cc: Nishanth Menon , Bjorn Andersson , Philipp Zabel , devicetree@vger.kernel.org, Conor Dooley , Hari Nagalla , linux-kernel@vger.kernel.org, Tero Kristo , Krzysztof Kozlowski , linux-remoteproc@vger.kernel.org, Vignesh Raghavendra , linux-arm-kernel@lists.infradead.org, Mathieu Poirier In-Reply-To: <20240424190612.17349-2-afd@ti.com> References: <20240424190612.17349-1-afd@ti.com> <20240424190612.17349-2-afd@ti.com> Message-Id: <171399099843.670532.4326365049493230346.robh@kernel.org> Subject: Re: [PATCH v8 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240424_133643_532858_73D4AF34 X-CRM114-Status: GOOD ( 13.09 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, 24 Apr 2024 14:06:09 -0500, Andrew Davis wrote: > From: Hari Nagalla > > K3 AM64x SoC has a Cortex M4F subsystem in the MCU voltage domain. > The remote processor's life cycle management and IPC mechanisms are > similar across the R5F and M4F cores from remote processor driver > point of view. However, there are subtle differences in image loading > and starting the M4F subsystems. > > The YAML binding document provides the various node properties to be > configured by the consumers of the M4F subsystem. > > Signed-off-by: Martyn Welch > Signed-off-by: Hari Nagalla > Signed-off-by: Andrew Davis > --- > .../bindings/remoteproc/ti,k3-m4f-rproc.yaml | 126 ++++++++++++++++++ > 1 file changed, 126 insertions(+) > create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml > My bot found errors running 'make dt_binding_check' on your patch: yamllint warnings/errors: dtschema/dtc warnings/errors: doc reference errors (make refcheckdocs): Warning: Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml references a file that doesn't exist: Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml: Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240424190612.17349-2-afd@ti.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. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel