Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp268850imp; Thu, 21 Feb 2019 00:49:16 -0800 (PST) X-Google-Smtp-Source: AHgI3IaqOPGW+ecGctIpZ6oBVAiKuhxI76pTeaIvMLfSyi3y47a6u77tLJzq1LshvrHW6cfORyQT X-Received: by 2002:a63:7c07:: with SMTP id x7mr19268375pgc.284.1550738955993; Thu, 21 Feb 2019 00:49:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550738955; cv=none; d=google.com; s=arc-20160816; b=0OV7SaRMqK27fJakCJr6/kGgGEMVfDh0w9TuP8W+sAbAIh8xrXABzOGwl/DZstOQBP zChXXQ/gycWe9qGBH93yb3+09lV78MyLFZQkAPGlxDkpczZ2Mpqs7U5qv+uQYuuRJ0wH A8lwqkN/s/1EFV4iNPOGbFW1fbzyCRI9u9w43CJ0FnihXJUMJuN6lwoTe+kPHZVxzHEk v/GDoMLQKzOo6RNuPD6XrjVxTr/rlwrA8FgfzJAqda7QCvkybx0kqFnRE5PM+kGzdeZ3 AcibC6bu902z6aDB344qsmCnTUDbDa+LgnjTyUEvlxPeTXX87Ki11CS435n3J9BLHpco o8yg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:from :dkim-signature; bh=q5iBvG4HqidiXxiGis5rvY71e0EFMSebp/Zntf2KFIo=; b=OCW0ielQUtpz8I7asgAdTKse40bJ7D3gt2/xIqMEeN91sxdK0To0eiiKSbS50uDFjX 5GY05e5ZBeU08SxTzqrFBEqWBv9o/1iylrLvNjfBsoZC639NtgZdr7KxY1j1LfQurc5X fHgPWtBehkknG2S+LKhZm+JFZaFO3CmCg+plP9DAAZTkSvrFLSxawJC6UsP8bn8w76V6 mvjjj76QG9Rx3Fmmrd6Yo3M0qGHG3MICgx248xnECGjaGeSdON2suHbrxSN4D/X6rtE5 5yP0Z4Vcrfry1cJhlmuttUT0CpPts4PgYVYpGZKMFCB0g1T6CFyyY0TYH5c2TPKsVf2C oheg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@chromium.org header.s=google header.b="Oa/WRdXX"; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b9si23202791plb.350.2019.02.21.00.49.00; Thu, 21 Feb 2019 00:49:15 -0800 (PST) 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=fail header.i=@chromium.org header.s=google header.b="Oa/WRdXX"; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727095AbfBUIsg (ORCPT + 99 others); Thu, 21 Feb 2019 03:48:36 -0500 Received: from mail-pg1-f193.google.com ([209.85.215.193]:42470 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725850AbfBUIsg (ORCPT ); Thu, 21 Feb 2019 03:48:36 -0500 Received: by mail-pg1-f193.google.com with SMTP id b2so7714622pgl.9 for ; Thu, 21 Feb 2019 00:48:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=q5iBvG4HqidiXxiGis5rvY71e0EFMSebp/Zntf2KFIo=; b=Oa/WRdXX+4W1q0fB/rVIGahugIrASieUZcaKxUUf1E/5TbKb9lwC4zhBD5NDipC8SK 8HW8jRhnxT1cc0AeeKkw1KqJ8EL0NBva/AIJSK7fxVbCbNszg0SOwO87B/bviWxGCjLJ PIzTnoYtieukZcNJ3kWdbXX9PdzM5zGHUdmzE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=q5iBvG4HqidiXxiGis5rvY71e0EFMSebp/Zntf2KFIo=; b=O4WxZyjzZpM7vAgLw12xCthYT8jhEmV1J2hWA3vVIm096B5DfjQJcDN9uUWLkUdspM Gp3xIKHFrlauZ6l06L7eM39Kl+Ss5BZQG+wA5gRTWpLqmGe+49lEMcjBPre9FMS1x3KB dAAbIDtltRiRVDOHFEXfitvZuL/jaVGlaLe7du0rDLvr/ZsZpkvTbqHn9LdueerkZRuH HNvBc1meD3RsluniNGnKGSovVCfeQ7Qc3bDnGALMEW2ZOm7utmGh2srb69jTsEOVPU7O 8MWsEnWQkYvHgLksLGQ/tTo9vJOEf8fDbYAjfhHQm/u6+y0GWYjjJFzaPMFKFKPEdU4l tcAA== X-Gm-Message-State: AHQUAubWtWywkGKK1efBPMrcwjiQf5dXqCkPbJDzBJPZKNL49ILtd/kw I/XpqpupKQBVfoN7c/TDfuUwzQ== X-Received: by 2002:a63:d104:: with SMTP id k4mr32626620pgg.227.1550738915080; Thu, 21 Feb 2019 00:48:35 -0800 (PST) Received: from pihsun-z840.tpe.corp.google.com ([2401:fa00:1:10:7889:7a43:f899:134c]) by smtp.googlemail.com with ESMTPSA id b4sm23154027pgq.57.2019.02.21.00.48.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Feb 2019 00:48:34 -0800 (PST) From: Pi-Hsun Shih Cc: Pi-Hsun Shih , Erin Lo , Ohad Ben-Cohen , Bjorn Andersson , Rob Herring , Mark Rutland , Matthias Brugger , linux-remoteproc@vger.kernel.org (open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM), devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS), linux-arm-kernel@lists.infradead.org (moderated list:ARM/Mediatek SoC support), linux-mediatek@lists.infradead.org (moderated list:ARM/Mediatek SoC support), linux-kernel@vger.kernel.org (open list) Subject: [PATCH v5 1/6] dt-bindings: Add a binding for Mediatek SCP Date: Thu, 21 Feb 2019 16:47:24 +0800 Message-Id: <20190221084729.101784-2-pihsun@chromium.org> X-Mailer: git-send-email 2.21.0.rc0.258.g878e2cd30e-goog In-Reply-To: <20190221084729.101784-1-pihsun@chromium.org> References: <20190221084729.101784-1-pihsun@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit To: unlisted-recipients:; (no To-header on input) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Erin Lo Add a DT binding documentation of SCP for the MT8183 SoC from Mediatek. Signed-off-by: Erin Lo --- Changes from v4: - Add detail of more properties. - Document the usage of mtk,rpmsg-name in subnode from the new design. Changes from v3: - No change. Changes from v2: - No change. I realized that for this patch series, there's no need to add anything under the mt8183-scp node (neither the mt8183-rpmsg or the cros-ec-rpmsg) for them to work, since mt8183-rpmsg is added directly as a rproc_subdev by code, and cros-ec-rpmsg is dynamically created by SCP name service. Changes from v1: - No change. --- .../bindings/remoteproc/mtk,scp.txt | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 Documentation/devicetree/bindings/remoteproc/mtk,scp.txt diff --git a/Documentation/devicetree/bindings/remoteproc/mtk,scp.txt b/Documentation/devicetree/bindings/remoteproc/mtk,scp.txt new file mode 100644 index 00000000000000..8cf8b0e0d98a4c --- /dev/null +++ b/Documentation/devicetree/bindings/remoteproc/mtk,scp.txt @@ -0,0 +1,37 @@ +Mediatek SCP Bindings +---------------------------------------- + +This binding provides support for ARM Cortex M4 Co-processor found on some +Mediatek SoCs. + +Required properties: +- compatible Should be "mediatek,mt8183-scp" +- reg Should contain the address ranges for the two memory + regions, SRAM and CFG. +- reg-names Contains the corresponding names for the two memory + regions. These should be named "sram" & "cfg". +- clocks Clock for co-processor (See: ../clock/clock-bindings.txt) +- clock-names Contains the corresponding name for the clock. This + should be named "main". + +Subnodes +-------- + +When CONFIG_RPMSG_MTK_SCP is enabled, subnodes of the SCP represent rpmsg +devices. The names of the devices are not important. The properties of these +nodes are defined by the individual bindings for the rpmsg devices - but must +contain the following property: + +- mtk,rpmsg-name Contains the name for the rpmsg device. Used to match + the subnode to rpmsg device announced by SCP. + +Example: + + scp: scp@10500000 { + compatible = "mediatek,mt8183-scp"; + reg = <0 0x10500000 0 0x80000>, + <0 0x105c0000 0 0x5000>; + reg-names = "sram", "cfg"; + clocks = <&infracfg CLK_INFRA_SCPSYS>; + clock-names = "main"; + }; -- 2.21.0.rc0.258.g878e2cd30e-goog