From patchwork Fri Dec 16 05:33:08 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: MD Danish Anwar X-Patchwork-Id: 33861 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:e747:0:0:0:0:0 with SMTP id c7csp783568wrn; Thu, 15 Dec 2022 21:36:09 -0800 (PST) X-Google-Smtp-Source: AA0mqf5JqPECHcOoblF+Bw9kCgcC+M97HGe/l56Wc3r8AYQSeVnStPqqTpcSMg8VqCzxcG1qKWTx X-Received: by 2002:a17:907:a604:b0:7bd:43e9:d3ab with SMTP id vt4-20020a170907a60400b007bd43e9d3abmr36002498ejc.52.1671168969686; Thu, 15 Dec 2022 21:36:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671168969; cv=none; d=google.com; s=arc-20160816; b=P9Pg83OE6Q5idE/4SYRaAhU8nwGqcwbqbUrDTYq4eM3NB2l4kiiJ6SRPsM0p3Rs4Zm REHDMZDDpQVANHq+TWCqHLK7A6CZKHwygfoJpxKZiGa/zmEiefZ5SGApnDAy5iS9sR9j cFIVvW/7C83xz1Iwcr5+2vrkwDLQjoVugh0NOul2alzrNyE0ONE3ZMk8xpEl5iisFKf8 aY86XeRBVq1dvKQwJjDtug+TsBLNPWqYXqKsw0F1oRWTDkJYVzxeyOLYXYtcvOeSLDDk I3S9b3MEKZJ4uH1aaU5SsGjObSJb39SljjYX0WTW+e7x0INidpclrT7DTHBxCKDv1LXy pMBg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=mkPjwEGogI62uJtihkwiClxeDM8LlzG5SN3BLcVtk3o=; b=xONIVY9F26ESzQmZpJ3YqjEUYoIzZgUIbg1TsP5AQ1qednu8QrHxE+v4hyZgpgXVfJ y0puZs3vsN9AEds1nYsuCoyGNO/IbBGR59I93ON6/KW2aflHEoZzCmcAtJ8f2FIs+Q9w LclJ0GuzzmEGu6AHr+MGVJpL2iyrxzRRS9QjK0EBXW+zAF1Upj7NaOpp8gQQzgc+xOJd MQYcE4DMhTWiAdARVMXbOuoY5IftJwUYYIolEP20qCzkP1X8nEa7NEWh0Piid2RrhDGK xd48olnxi0KREBbJC28KmeLdfG08SHra6goZj3hcH2UK2AEfD4m/ZaYTYhOfbnsHlRjO +xbA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=iBtu+HfU; 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: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cs18-20020a170906dc9200b007c172bd367fsi1701504ejc.193.2022.12.15.21.35.46; Thu, 15 Dec 2022 21:36:09 -0800 (PST) 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=iBtu+HfU; 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 S229885AbiLPFdl (ORCPT + 99 others); Fri, 16 Dec 2022 00:33:41 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59708 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229480AbiLPFdi (ORCPT ); Fri, 16 Dec 2022 00:33:38 -0500 Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A9591175A6; Thu, 15 Dec 2022 21:33:34 -0800 (PST) Received: from lelv0265.itg.ti.com ([10.180.67.224]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 2BG5XHBs010032; Thu, 15 Dec 2022 23:33:17 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1671168797; bh=mkPjwEGogI62uJtihkwiClxeDM8LlzG5SN3BLcVtk3o=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=iBtu+HfURctYHK94uQ63HeJ0rbwgLvUToCIs1IVCx8GbNNo5Oe4iAYWO36hBZoFjo sU2zDYFcfnwtHinFgX9D1zlLWD64jOpSiR87ucoYvCps5wb8aF8eKJUmhnmxZaGOxl BgoF0Ll3FoRPJRZ6cUTresudfiy+NdnwWqNHrST0= Received: from DLEE115.ent.ti.com (dlee115.ent.ti.com [157.170.170.26]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 2BG5XHdk022676 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 15 Dec 2022 23:33:17 -0600 Received: from DLEE108.ent.ti.com (157.170.170.38) by DLEE115.ent.ti.com (157.170.170.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16; Thu, 15 Dec 2022 23:33:17 -0600 Received: from lelv0327.itg.ti.com (10.180.67.183) by DLEE108.ent.ti.com (157.170.170.38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16 via Frontend Transport; Thu, 15 Dec 2022 23:33:17 -0600 Received: from lelv0854.itg.ti.com (lelv0854.itg.ti.com [10.181.64.140]) by lelv0327.itg.ti.com (8.15.2/8.15.2) with ESMTP id 2BG5XHQE013174; Thu, 15 Dec 2022 23:33:17 -0600 Received: from localhost (a0501179-pc.dhcp.ti.com [10.24.69.114]) by lelv0854.itg.ti.com (8.14.7/8.14.7) with ESMTP id 2BG5XGfo008916; Thu, 15 Dec 2022 23:33:16 -0600 From: MD Danish Anwar To: Mathieu Poirier , Krzysztof Kozlowski , Rob Herring CC: Suman Anna , Roger Quadros , "Andrew F . Davis" , , , , , , , , MD Danish Anwar Subject: [PATCH v12 1/6] dt-bindings: remoteproc: Add PRU consumer bindings Date: Fri, 16 Dec 2022 11:03:08 +0530 Message-ID: <20221216053313.2974826-2-danishanwar@ti.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20221216053313.2974826-1-danishanwar@ti.com> References: <20221216053313.2974826-1-danishanwar@ti.com> MIME-Version: 1.0 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 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 X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1752347673471833812?= X-GMAIL-MSGID: =?utf-8?q?1752347673471833812?= From: Suman Anna Add DT schema binding 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. Signed-off-by: Tero Kristo Signed-off-by: Suman Anna Signed-off-by: Grzegorz Jaszczyk Signed-off-by: MD Danish Anwar Reviewed-by: Rob Herring --- .../bindings/remoteproc/ti,pru-consumer.yaml | 60 +++++++++++++++++++ 1 file changed, 60 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..c6d86964b72a --- /dev/null +++ b/Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml @@ -0,0 +1,60 @@ +# 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 + minItems: 1 + maxItems: 6 + items: + maxItems: 1 + + firmware-name: + $ref: /schemas/types.yaml#/definitions/string-array + minItems: 1 + maxItems: 6 + 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 + minItems: 1 + 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 + +additionalProperties: true