Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp414010pxb; Thu, 7 Apr 2022 08:49:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyZl+s1D1Cs6ePxi+qdynoqEmmphWtAtkXtgvlc0WuQOMbbkrFePb/eAzUx/nZM3mW2QrrK X-Received: by 2002:a17:906:32cf:b0:6d5:83bc:e962 with SMTP id k15-20020a17090632cf00b006d583bce962mr14595995ejk.108.1649346563409; Thu, 07 Apr 2022 08:49:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649346563; cv=none; d=google.com; s=arc-20160816; b=zXZXtKqCQVVo3/PAgJ9E9DBaYhbhFr6VgznGy9ml+hQdKOGxTlBked860j5oRav0db 6HqNyUqsZPYNXXHbYpTZdi+qWQaFm7SWMPCATwDM7pglkdeMyvHcVyhASgGYENq1gHjh lf409yTkRJiO85oZ1EmFWlrElByBj1QSw1ogmuWNJwZmJI0dqGAufMmgf5QKvmJOXgzR Y07T3KVgGKbFNKJ4ldYAoleyLwcP/mW01mz44MB28rWOoYu6QZF1gmQM4pRWB7pz2N1e UW/JhlD987wyyADf0gy5C/D9kTcAVJE26aM1UiqA7OPxP/r4C51p/xYjrylykK4Pu5pB vzsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=NZajb31VTP+/s1Rr/jPY5VYbBOIIC0ip92OpWe0CpKI=; b=NECmNV2JC2AIat0N8qpGGuxG9c6oja1878Ghm8UnM02YOYf25eWXfun1Pg89m7k/g7 QipqiJdnd6GK0uIvs1ZNF2p13M0DzXTEBe4Viq7/MJS+Dp1rYBlKuq6yGp5bKXp0xzwK um8P4VY0YTKRmPY4LYt8s61AJsKCTgyY7Qzz/KeN73YD1EWNe7OZX+W5KlJdWoHSdn/R e3DGHd7kgf+VYcuCDH8n8umP1Sv9tVfIU+82pp7GQwo6y8HpZ7/JT8PridPuRIxzZ/E4 PE4yvatmHtawB2xG+BWkLywNmdMsnUSI6vmsFlaoMmmlzxoP/eBTPNznjizl646V9UbX vJtw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=rLQvQURa; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q16-20020a50cc90000000b0041cdabdaad6si8551316edi.621.2022.04.07.08.48.46; Thu, 07 Apr 2022 08:49:23 -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=@ti.com header.s=ti-com-17Q1 header.b=rLQvQURa; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244852AbiDGLlC (ORCPT + 99 others); Thu, 7 Apr 2022 07:41:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34036 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240112AbiDGLlA (ORCPT ); Thu, 7 Apr 2022 07:41:00 -0400 Received: from fllv0015.ext.ti.com (fllv0015.ext.ti.com [198.47.19.141]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CCA0A133654; Thu, 7 Apr 2022 04:38:59 -0700 (PDT) Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 2369i3Jj108698; Wed, 6 Apr 2022 04:44:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1649238243; bh=NZajb31VTP+/s1Rr/jPY5VYbBOIIC0ip92OpWe0CpKI=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=rLQvQURaHhNQczJHyY8HVhkB9iZhR4NTs96JkBqSVxWIpp03g3xc5DDCaEtxnlgUb /HRFgxGx33AmQ8YggawaAR/l7MgKhfHDQBHCU4jE8Ypmt2bgfDE9m59SgEKM+hQz2u N3T1PC+Wso0+s4wPS2FroV27pWRrx4nEmQlFc6uQ= Received: from DFLE102.ent.ti.com (dfle102.ent.ti.com [10.64.6.23]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 2369i3mH069663 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 6 Apr 2022 04:44:03 -0500 Received: from DFLE109.ent.ti.com (10.64.6.30) by DFLE102.ent.ti.com (10.64.6.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14; Wed, 6 Apr 2022 04:44:03 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DFLE109.ent.ti.com (10.64.6.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14 via Frontend Transport; Wed, 6 Apr 2022 04:44:03 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 2369i1sF089477; Wed, 6 Apr 2022 04:44:02 -0500 From: Puranjay Mohan To: CC: , , , , , , , , , , , , , , Subject: [RFC 01/13] dt-bindings: remoteproc: Add PRU consumer bindings Date: Wed, 6 Apr 2022 15:13:46 +0530 Message-ID: <20220406094358.7895-2-p-mohan@ti.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220406094358.7895-1-p-mohan@ti.com> References: <20220406094358.7895-1-p-mohan@ti.com> MIME-Version: 1.0 Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 From: Suman Anna Add a YAML binding document for PRU consumers. The binding includes all the common properties that can be used by different PRU consumer or application nodes and supported by the PRU remoteproc driver. These are used to configure the PRU hardware for specific user applications. The application nodes themselves should define their own bindings. Co-developed-by: Tero Kristo Signed-off-by: Tero Kristo Signed-off-by: Suman Anna Co-developed-by: Grzegorz Jaszczyk Signed-off-by: Grzegorz Jaszczyk Signed-off-by: Puranjay Mohan --- .../bindings/remoteproc/ti,pru-consumer.yaml | 66 +++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml diff --git a/Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml b/Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml new file mode 100644 index 000000000000..c245fe1de656 --- /dev/null +++ b/Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml @@ -0,0 +1,66 @@ +# SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/remoteproc/ti,pru-consumer.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Common TI PRU Consumer Binding + +maintainers: + - Suman Anna + +description: | + A PRU application/consumer/user node typically uses one or more PRU device + nodes to implement a PRU application/functionality. Each application/client + node would need a reference to at least a PRU node, and optionally define + some properties needed for hardware/firmware configuration. The below + properties are a list of common properties supported by the PRU remoteproc + infrastructure. + + The application nodes shall define their own bindings like regular platform + devices, so below are in addition to each node's bindings. + +properties: + ti,prus: + $ref: /schemas/types.yaml#/definitions/phandle-array + description: phandles to the PRU, RTU or Tx_PRU nodes used + + firmware-name: + $ref: /schemas/types.yaml#/definitions/string-array + description: | + firmwares for the PRU cores, the default firmware for the core from + the PRU node will be used if not provided. The firmware names should + correspond to the PRU cores listed in the 'ti,prus' property + + ti,pruss-gp-mux-sel: + $ref: /schemas/types.yaml#/definitions/uint32-array + maxItems: 6 + items: + enum: [0, 1, 2, 3, 4] + description: | + array of values for the GP_MUX_SEL under PRUSS_GPCFG register for a PRU. + This selects the internal muxing scheme for the PRU instance. Values + should correspond to the PRU cores listed in the 'ti,prus' property. The + GP_MUX_SEL setting is a per-slice setting (one setting for PRU0, RTU0, + and Tx_PRU0 on K3 SoCs). Use the same value for all cores within the + same slice in the associative array. If the array size is smaller than + the size of 'ti,prus' property, the default out-of-reset value (0) for the + PRU core is used. + +required: + - ti,prus + +dependencies: + firmware-name: [ 'ti,prus' ] + ti,pruss-gp-mux-sel: [ 'ti,prus' ] + +additionalProperties: true + +examples: + - | + /* PRU application node example */ + pru-app { + ti,prus = <&pru0>, <&pru1>; + firmware-name = "pruss-app-fw0", "pruss-app-fw1"; + ti,pruss-gp-mux-sel = <2>, <1>; + }; -- 2.17.1