Received: by 2002:a05:6a10:8395:0:0:0:0 with SMTP id n21csp359916pxh; Wed, 10 Nov 2021 03:00:58 -0800 (PST) X-Google-Smtp-Source: ABdhPJw3Prksjt1nO1InPneDw7I8wmLdNXOPhYsQy2oYQ475MJla3Gjkf9l1uzU0pZFd1ogGqwVp X-Received: by 2002:a17:906:489b:: with SMTP id v27mr18685537ejq.567.1636542058031; Wed, 10 Nov 2021 03:00:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636542058; cv=none; d=google.com; s=arc-20160816; b=mJw3R+SkHMILI2rcrkkDR3cEfMt4Ay8eujhkryd2BAD2Ovwo2dVwdYEjgCQl+GVYdK F6xx2x/np+ITLwM1lrcROFZ5OgBz/so9hSvJ70MxjsIw8a/C7SvBdyqL1DLNekOwJAMw RWJTwt6hOSzjloXfXO/ZOrBKRD7R18vanZyxrBYpOKKRlHeHFNZiAKA06eENhzwj/aMr 7btNlodtG4MVVXzIzqHUtGpA/95KcvB2k5DtKQoB58dvz8hWntiJRjPOf6JjeMuQrQkM ri2I+WjcE2xppMCTVt/iDggYoMu4TBUdNHOcRebscq5zkQskDWM0Ji1UfrjnS4XAEvQb g0MQ== 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=DQqprj5LG6fM+PnCA7QJB2prIZNlY3Ax3gSE2z4dNwU=; b=eW8zozUOp1qIX6C3A6T1fwM+cyWFPHjnj886fxAzROJIY2LKGvFdTr4oc80NDByfwW GY434D38iECbXwRGDnN596m/5Xfdt1z5uYFN0nHRgSSEDZ2gBXqjSa18+wBxgS7b1mTj 47zjZ0Dz6Mc9QSGl1oOtPYmJTShzqwi8pYeJkc014KXMuatFZZN5/sbuSksKyxIj1gFt tHeoJkv0uYYDJNGxNDFxSnq3YPKzWmS2RlHWXfjn5+RIXbTriIX3vqhFHWp+TKxPgHKQ ErqexaPl1CvLfX9V9Od03D7hTK/GFm6fh+YlGYgYcUb8csPfpbZe5pt7WZcjNAxAofss SN3g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=eiu8AHmD; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l14si43538188edb.618.2021.11.10.03.00.33; Wed, 10 Nov 2021 03:00:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=eiu8AHmD; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-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 S231441AbhKJLCo (ORCPT + 99 others); Wed, 10 Nov 2021 06:02:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50266 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231477AbhKJLCn (ORCPT ); Wed, 10 Nov 2021 06:02:43 -0500 Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B8E34C0613F5 for ; Wed, 10 Nov 2021 02:59:56 -0800 (PST) Received: by mail-pl1-x635.google.com with SMTP id u11so2710163plf.3 for ; Wed, 10 Nov 2021 02:59:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=DQqprj5LG6fM+PnCA7QJB2prIZNlY3Ax3gSE2z4dNwU=; b=eiu8AHmDAI97fZsoLR9/XsptFE0RJMPgDGXqW69j/pRQPpdajZlgHb/KZdKu4IWngq 63P0LtdCoTudc7xlCgWF+79CFFiPIJCxMXgOzkfi4boYeQfAgKqNhegPyZSu4xelYIeP RC9dXW6iStMXhu1VkyJxDBH7nc2YVCg5UGnSvF7rzpMY2FTDzo/bYTT2Eufynx2QB8EX wEv1+084riEg50HJuhp2AZaFJlyYsZjDIFUHLsnpWAWYGHB19c1IOIw4iAdGTca2CZrb 6bv/BoV1B5h4zqD9/hCuHRiSSzrwI3DXltBD+Xwz6vK8yzBEWEst4fiI6ZKTN5Vj+C2J mizg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=DQqprj5LG6fM+PnCA7QJB2prIZNlY3Ax3gSE2z4dNwU=; b=z0e/pZypEKzuyuHUN2pMfaV9BBI/xoGIG9s3d+DRccxziaEUvJebKj/TqWqgfHsdxK GW61wGFfGUmbugCZmrFCyGrzlHvDiuRS83JLCl1bXzVb83APPjqrc0u6a3gxV2Umk2qW QDlW7aHRBUZMttCUU1HWnds3NXmkwddti3MUU+mOy8dePvF7iA1Ay1yPcUIkxvbJbZmH Qn7NkudAMHqEi/VPWyIFiVoX3cxWj9z0DorZKvoVdJuiTeEVcxTg55CUgJJuDVtYhAmq JgKCGi8JI+eL20yGNPQlhX/EssY1gqIgOrtjY1ANGTezRyyLVzM8Lsu4UrLJJuYIMqKr ow2Q== X-Gm-Message-State: AOAM533Se1LH5G3rcaBydGIvq9ViDJdxMW8wintCNlmhwjzVC3wblcLa 9zpe6TgsO6XSAWNIhboz+LxA0g== X-Received: by 2002:a17:90b:4f85:: with SMTP id qe5mr15629740pjb.167.1636541996221; Wed, 10 Nov 2021 02:59:56 -0800 (PST) Received: from localhost.name ([122.161.52.143]) by smtp.gmail.com with ESMTPSA id e11sm5585282pjl.20.2021.11.10.02.59.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 10 Nov 2021 02:59:55 -0800 (PST) From: Bhupesh Sharma To: linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org Cc: bhupesh.sharma@linaro.org, bhupesh.linux@gmail.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, robh+dt@kernel.org, agross@kernel.org, herbert@gondor.apana.org.au, davem@davemloft.net, stephan@gerhold.net, Thara Gopinath , Bjorn Andersson Subject: [PATCH v5 03/22] dt-bindings: qcom-bam: Convert binding to YAML Date: Wed, 10 Nov 2021 16:29:03 +0530 Message-Id: <20211110105922.217895-4-bhupesh.sharma@linaro.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20211110105922.217895-1-bhupesh.sharma@linaro.org> References: <20211110105922.217895-1-bhupesh.sharma@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Convert Qualcomm BAM DMA devicetree binding to YAML. Cc: Thara Gopinath Cc: Bjorn Andersson Cc: Rob Herring Signed-off-by: Bhupesh Sharma --- .../devicetree/bindings/dma/qcom_bam_dma.txt | 50 ---------- .../devicetree/bindings/dma/qcom_bam_dma.yaml | 91 +++++++++++++++++++ 2 files changed, 91 insertions(+), 50 deletions(-) delete mode 100644 Documentation/devicetree/bindings/dma/qcom_bam_dma.txt create mode 100644 Documentation/devicetree/bindings/dma/qcom_bam_dma.yaml diff --git a/Documentation/devicetree/bindings/dma/qcom_bam_dma.txt b/Documentation/devicetree/bindings/dma/qcom_bam_dma.txt deleted file mode 100644 index cf5b9e44432c..000000000000 --- a/Documentation/devicetree/bindings/dma/qcom_bam_dma.txt +++ /dev/null @@ -1,50 +0,0 @@ -QCOM BAM DMA controller - -Required properties: -- compatible: must be one of the following: - * "qcom,bam-v1.4.0" for MSM8974, APQ8074 and APQ8084 - * "qcom,bam-v1.3.0" for APQ8064, IPQ8064 and MSM8960 - * "qcom,bam-v1.7.0" for MSM8916 -- reg: Address range for DMA registers -- interrupts: Should contain the one interrupt shared by all channels -- #dma-cells: must be <1>, the cell in the dmas property of the client device - represents the channel number -- clocks: required clock -- clock-names: must contain "bam_clk" entry -- qcom,ee : indicates the active Execution Environment identifier (0-7) used in - the secure world. -- qcom,controlled-remotely : optional, indicates that the bam is controlled by - remote proccessor i.e. execution environment. -- num-channels : optional, indicates supported number of DMA channels in a - remotely controlled bam. -- qcom,num-ees : optional, indicates supported number of Execution Environments - in a remotely controlled bam. - -Example: - - uart-bam: dma@f9984000 = { - compatible = "qcom,bam-v1.4.0"; - reg = <0xf9984000 0x15000>; - interrupts = <0 94 0>; - clocks = <&gcc GCC_BAM_DMA_AHB_CLK>; - clock-names = "bam_clk"; - #dma-cells = <1>; - qcom,ee = <0>; - }; - -DMA clients must use the format described in the dma.txt file, using a two cell -specifier for each channel. - -Example: - serial@f991e000 { - compatible = "qcom,msm-uart"; - reg = <0xf991e000 0x1000> - <0xf9944000 0x19000>; - interrupts = <0 108 0>; - clocks = <&gcc GCC_BLSP1_UART2_APPS_CLK>, - <&gcc GCC_BLSP1_AHB_CLK>; - clock-names = "core", "iface"; - - dmas = <&uart-bam 0>, <&uart-bam 1>; - dma-names = "rx", "tx"; - }; diff --git a/Documentation/devicetree/bindings/dma/qcom_bam_dma.yaml b/Documentation/devicetree/bindings/dma/qcom_bam_dma.yaml new file mode 100644 index 000000000000..3ca222bd10bd --- /dev/null +++ b/Documentation/devicetree/bindings/dma/qcom_bam_dma.yaml @@ -0,0 +1,91 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/dma/qcom_bam_dma.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: QCOM BAM DMA controller binding + +maintainers: + - Bhupesh Sharma + +description: | + This document defines the binding for the BAM DMA controller + found on Qualcomm parts. + +allOf: + - $ref: "dma-controller.yaml#" + +properties: + compatible: + enum: + - qcom,bam-v1.3.0 # for APQ8064, IPQ8064 and MSM8960 + - qcom,bam-v1.4.0 # for MSM8974, APQ8074 and APQ8084 + - qcom,bam-v1.7.0 # for MSM8916 + + reg: + maxItems: 1 + + clocks: + maxItems: 1 + + clock-names: + const: bam_clk + + interrupts: + minItems: 1 + maxItems: 31 + + num-channels: + maximum: 31 + description: + Indicates supported number of DMA channels in a remotely controlled bam. + + "#dma-cells": + const: 1 + description: The single cell represents the channel index. + + qcom,ee: + $ref: /schemas/types.yaml#/definitions/uint32 + minimum: 0 + maximum: 7 + description: + Indicates the active Execution Environment identifier (0-7) + used in the secure world. + + qcom,controlled-remotely: + $ref: /schemas/types.yaml#/definitions/flag + description: + Indicates that the bam is controlled by remote proccessor i.e. + execution environment. + + qcom,num-ees: + $ref: /schemas/types.yaml#/definitions/uint32 + minimum: 0 + maximum: 31 + default: 2 + description: + Indicates supported number of Execution Environments in a + remotely controlled bam. + +required: + - compatible + - reg + - interrupts + - "#dma-cells" + - qcom,ee + +additionalProperties: false + +examples: + - | + #include + dma-controller@f9984000 { + compatible = "qcom,bam-v1.4.0"; + reg = <0xf9984000 0x15000>; + interrupts = <0 94 0>; + clocks = <&gcc GCC_BAM_DMA_AHB_CLK>; + clock-names = "bam_clk"; + #dma-cells = <1>; + qcom,ee = <0>; + }; -- 2.31.1