Received: by 10.213.65.68 with SMTP id h4csp2126400imn; Thu, 5 Apr 2018 09:23:10 -0700 (PDT) X-Google-Smtp-Source: AIpwx48irpmIvRP/FJdlVfy9BeEr+yzAqKs6Hl6ztCC8xUHL+80gf0wew1pv/J7NuHnP55ZHQqCh X-Received: by 2002:a17:902:a608:: with SMTP id u8-v6mr23760205plq.25.1522945390761; Thu, 05 Apr 2018 09:23:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522945390; cv=none; d=google.com; s=arc-20160816; b=burPRtsncQWUfKjrBAlBlGyl9Sn+I7QwnZuGS6K9kvXS7k0ihr1hQg+3yFG5FFYPfM fExtModNmfpH57uR2nCnd+WdQBt3YNMylmeQFDL2GcKdu5y9y2OytRJg8ZBAeSlJLVEp Qbp/dyEGMI7efjTMCaFt+6FlRLelNxGS6DKuntkPLY3MJahSdpSCEGW8XfhRmtRJaDUg OuAqklzJLlghQaxwql9uhpyLgpAv+KwoXXj+AzNualEnrliLrxhMstvx2Esz8tkSrdKH bHtSze6lSyf5jp1z5UFinf9yVWT0NT2/CR2XF6HPVhbxapYF4nxctcxcm7wWaPa0OgIJ Ubcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dmarc-filter:dkim-signature:dkim-signature :arc-authentication-results; bh=t2ynDiKvg9VLdleOMgUfHMgUEZ1fTc/aAk1Pu+NXAxw=; b=f9fJBWwhBJD5z8VAboHu06Ppfyh+pMTL3hsLwrspP1UbzUmfiKajbEyzLVn14/Z2D3 l04fD5AhxOSRXvkpqzlY6B/oQzQqG+Kd4BuRTiLzvzEuP8IxRtdA+D5x8e43I+K51Kje yhQjV9Zsurz6VoAuhbAfkgsVVq/VNpthnSzoy7rieJmKufTrtykzEWwOZH5HpplT6EFB In/eK9RBzgAB+65PQKvcLtAedqMZ2SD/LALpGofLgqdIfbK4Hp7tdU0ZJKCiWdOGKH22 2F4Zodbr3rnPnyz15OXy7qSNn7if1WzrfCyAyhuaBDAGbHzUEYbUF1MFlqZ6ImgUwqe4 mi2Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=EwGrKFJc; dkim=pass header.i=@codeaurora.org header.s=default header.b=EwGrKFJc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g61-v6si6087546plb.686.2018.04.05.09.22.56; Thu, 05 Apr 2018 09:23:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=EwGrKFJc; dkim=pass header.i=@codeaurora.org header.s=default header.b=EwGrKFJc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751935AbeDEQVX (ORCPT + 99 others); Thu, 5 Apr 2018 12:21:23 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:41478 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751363AbeDEQSn (ORCPT ); Thu, 5 Apr 2018 12:18:43 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id E886860364; Thu, 5 Apr 2018 16:18:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1522945122; bh=EH20J53qhdgrj/tME3tUCQnRxpesVPNAiJlsl/Lca28=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=EwGrKFJcmEkOS5o/V0mbO15m0riiIbsHqbl0PmjdkLNfCTcQ4nTrTJpdy4QjY4NvV t+KUXRCl5P1/xe0iU0um1Qf7y/GXrEi7kbMsEhT3WKw//f3+seNw/h+ccVLE8gUEp9 GWb5wht1i3Gk1vfbF0bYTCwraQtCPJo2HItnkeoQ= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from codeaurora.org (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ilina@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 5AD2C6081B; Thu, 5 Apr 2018 16:18:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1522945122; bh=EH20J53qhdgrj/tME3tUCQnRxpesVPNAiJlsl/Lca28=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=EwGrKFJcmEkOS5o/V0mbO15m0riiIbsHqbl0PmjdkLNfCTcQ4nTrTJpdy4QjY4NvV t+KUXRCl5P1/xe0iU0um1Qf7y/GXrEi7kbMsEhT3WKw//f3+seNw/h+ccVLE8gUEp9 GWb5wht1i3Gk1vfbF0bYTCwraQtCPJo2HItnkeoQ= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 5AD2C6081B Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=ilina@codeaurora.org From: Lina Iyer To: andy.gross@linaro.org, david.brown@linaro.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org Cc: rnayak@codeaurora.org, bjorn.andersson@linaro.org, linux-kernel@vger.kernel.org, sboyd@kernel.org, evgreen@chromium.org, dianders@chromium.org, Lina Iyer , devicetree@vger.kernel.org Subject: [PATCH v5 02/10] dt-bindings: introduce RPMH RSC bindings for Qualcomm SoCs Date: Thu, 5 Apr 2018 10:18:26 -0600 Message-Id: <20180405161834.3850-3-ilina@codeaurora.org> X-Mailer: git-send-email 2.16.3 In-Reply-To: <20180405161834.3850-1-ilina@codeaurora.org> References: <20180405161834.3850-1-ilina@codeaurora.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add device binding documentation for Qualcomm Technology Inc's RPMH RSC driver. The driver is used for communicating resource state requests for shared resources. Cc: devicetree@vger.kernel.org Signed-off-by: Lina Iyer Reviewed-by: Rob Herring --- Changes in v3: - Move to soc/qcom - Amend text per Stephen's suggestions Changes in v2: - Amend text to describe the registers in reg property - Add reg-names for the registers - Update examples to use GIC_SPI in interrupts instead of 0 - Rephrase incorrect description Changes in v3: - Fix unwanted capitalization - Remove clients from the examples, this doc does not describe them - Rephrase introductory paragraph - Remove hardware specifics from DT bindings --- .../devicetree/bindings/soc/qcom/rpmh-rsc.txt | 127 +++++++++++++++++++++ 1 file changed, 127 insertions(+) create mode 100644 Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt diff --git a/Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt b/Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt new file mode 100644 index 000000000000..dcf71a5b302f --- /dev/null +++ b/Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt @@ -0,0 +1,127 @@ +RPMH RSC: +------------ + +Resource Power Manager Hardened (RPMH) is the mechanism for communicating with +the hardened resource accelerators on Qualcomm SoCs. Requests to the resources +can be written to the Trigger Command Set (TCS) registers and using a (addr, +val) pair and triggered. Messages in the TCS are then sent in sequence over an +internal bus. + +The hardware block (Direct Resource Voter or DRV) is a part of the h/w entity +(Resource State Coordinator a.k.a RSC) that can handle a multiple sleep and +active/wake resource requests. Multiple such DRVs can exist in a SoC and can +be written to from Linux. The structure of each DRV follows the same template +with a few variations that are captured by the properties here. + +A TCS may be triggered from Linux or triggered by the F/W after all the CPUs +have powered off to facilitate idle power saving. TCS could be classified as - + + SLEEP, /* Triggered by F/W */ + WAKE, /* Triggered by F/W */ + ACTIVE, /* Triggered by Linux */ + CONTROL /* Triggered by F/W */ + +The order in which they are described in the DT, should match the hardware +configuration. + +Requests can be made for the state of a resource, when the subsystem is active +or idle. When all subsystems like Modem, GPU, CPU are idle, the resource state +will be an aggregate of the sleep votes from each of those subsystems. Clients +may request a sleep value for their shared resources in addition to the active +mode requests. + +Properties: + +- compatible: + Usage: required + Value type: + Definition: Should be "qcom,rpmh-rsc". + +- reg: + Usage: required + Value type: + Definition: The first register specifies the base address of the DRV. + The second register specifies the start address of the + TCS. + +- reg-names: + Usage: required + Value type: + Definition: Maps the register specified in the reg property. Must be + "drv" and "tcs". + +- interrupts: + Usage: required + Value type: + Definition: The interrupt that trips when a message complete/response + is received for this DRV from the accelerators. + +- qcom,drv-id: + Usage: required + Value type: + Definition: the id of the DRV in the RSC block. + +- qcom,tcs-config: + Usage: required + Value type: + Definition: the tuple defining the configuration of TCS. + Must have 2 cells which describe each TCS type. + . + The order of the TCS must match the hardware + configuration. + - Cell #1 (TCS Type): TCS types to be specified - + SLEEP_TCS + WAKE_TCS + ACTIVE_TCS + CONTROL_TCS + - Cell #2 (Number of TCS): + +- label: + Usage: optional + Value type: + Definition: Name for the RSC. The name would be used in trace logs. + +Drivers that want to use the RSC to communicate with RPMH must specify their +bindings as child of the RSC controllers they wish to communicate with. + +Example 1: + +For a TCS whose RSC base address is is 0x179C0000 and is at a DRV id of 2, the +register offsets for DRV2 start at 0D00, the register calculations are like +this - +First tuple: 0x179C0000 + 0x10000 * 2 = 0x179E0000 +Second tuple: 0x179E0000 + 0xD00 = 0x179E0D00 + + apps_rsc: rsc@179e000 { + label = "apps_rsc"; + compatible = "qcom,rpmh-rsc"; + reg = <0x179e0000 0x10000>, <0x179e0d00 0x3000>; + reg-names = "drv", "tcs"; + interrupts = ; + qcom,drv-id = <2>; + qcom,tcs-config = , + , + , + ; + }; + +Example 2: + +For a TCS whose RSC base address is 0xAF20000 and is at DRV id of 0, the +register offsets for DRV0 start at 01C00, the register calculations are like +this - +First tuple: 0xAF20000 +Second tuple: 0xAF20000 + 0x1C00 = 0xAF21C00 + + disp_rsc: rsc@af20000 { + label = "disp_rsc"; + compatible = "qcom,rpmh-rsc"; + reg = <0xaf20000 0x10000>, <0xaf21c00 0x3000>; + reg-names = "drv", "tcs"; + interrupts = ; + qcom,drv-id = <0>; + qcom,tcs-config = , + , + , + ; + }; -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project