Received: by 10.192.165.148 with SMTP id m20csp3616802imm; Mon, 30 Apr 2018 03:32:10 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoQyZ2V6lheaJpy3HascYVSQF2YuKhZ4zKQ+3t2FgFiHZKEhDwxFtLORl8APYigU1JAQWXa X-Received: by 2002:a63:31cd:: with SMTP id x196-v6mr9350734pgx.397.1525084330050; Mon, 30 Apr 2018 03:32:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525084329; cv=none; d=google.com; s=arc-20160816; b=KcVRYRrn0sMyruLuEbePlFuMZhsrXOe6dZUO2gQ1RL41zZ5jOmwVaZlEdY1JzVM7fC Ro0UPNyjCyHtcY7aR8q1UV2ZmmhmopfecjTsDXi2Z2fKcrZW9k1xxq9K5ToAiEbk4eaI I8QFMORoTCFDH/RdcGzMpDsvRLXZYoTnF0xqOxF1soaK1mlpOXicSc2PgrT/W9PZheod 4rS9d36nBK1m7IRVbZZSyrx928Qn5zwOYGgGfsJ/95Ei5fM6XzdQlDJSEhk8auDL92RR v1NFB1tnPzHjYTYtpvhK3VJWUL79EaA8wnn8IcanwHXlm1zu1ajTnvRTnSWjEBhu7DhZ fn1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=pNhCL5NHo42HQ/3bdFvBUUZIWwn5z2onYFUV1tH6uu4=; b=uTdWw9M8Z/AGOonjEdHcQAVzVqUadrkUvdgMscqQcYIYTWFfuW7W8PCQ8hwpvhlorK io+7smJQHj4/HEYU/AvOgBjzcmj6BNR3/DQlgZIXbj2x6Aayi8DfKZqikrZpYBBg1mjU 4dedO49uJJ9/ZQozi7wjZpUSHGbJoNUA9uciI2DaR2l71RIyfGEXBy2huvkfbUP9pIFI LNuEKTOj/wwm40PvNxpChoLwj/90aM9fdbfEB/hASlEw+MGbVI4bj9y9eJoJhOIdicS4 H4t9Wq126XA3PFVBRQ3qwK0auT+LwfY5LKUtkiJdJE/JZQ4/RgRsxflXWMvZNo4SOwTw 1K3A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=FaMjiFz+; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e84si3958967pfk.198.2018.04.30.03.31.56; Mon, 30 Apr 2018 03:32:09 -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=@linaro.org header.s=google header.b=FaMjiFz+; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752382AbeD3Kaf (ORCPT + 99 others); Mon, 30 Apr 2018 06:30:35 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:39230 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751361AbeD3Kad (ORCPT ); Mon, 30 Apr 2018 06:30:33 -0400 Received: by mail-wm0-f67.google.com with SMTP id f8so2891571wmc.4 for ; Mon, 30 Apr 2018 03:30:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=pNhCL5NHo42HQ/3bdFvBUUZIWwn5z2onYFUV1tH6uu4=; b=FaMjiFz+1kwASHSwok5B5vt+iDGHejFWeGlAeJx4giWo2LQT/wnOu0i8vzMBkc2xc4 N3bzQt7Gdoq3+y8XPbQNFjudhYuUrU8F2/c8/UoreBmlXuEyx8jybz0RUH5olPm9j5YV /P/2ZM3DFfm99yCe9CdulRca4Q2TKSuHlxmJs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=pNhCL5NHo42HQ/3bdFvBUUZIWwn5z2onYFUV1tH6uu4=; b=YJab75ZqcAq9PC778j09+WTlEalFhxYKwPB3qG3kQ6PRLBzVoAQB/X+Mplcp6pF9Fg hXWPHAUKjQbvniwxClPOuH0zSueNgofre8uP7UIlzquKmbSORHUdPyG4+SzqzJ6kuOhj CZF4SbSmRHIfwUs9g0T7XqFEce/5bhSu6fRWs+Z3o9eNSuWq4jV8e6WUVbKuf7ATMz5k P7gHTGUe7HbjkwKm+rHPxEtqgZzlRrg5DdJEh5R7Gr3k8sZaL7ZqYZf4xByyqmI5JzGc yssFDqcVzOlgC7BKQ0MpVx8rYW7FPCZxiwhHxqW5A4BNp9xfLG9lnpU+S+PPddrVHCwP PdHQ== X-Gm-Message-State: ALQs6tCYew2fu6hinUAVZmGGGcV/ZvP/izodV9EqCtjkTFQwiag4y+Pu m3/lVZ+zIOhYc4vyNNv4izn7jQ== X-Received: by 10.28.95.130 with SMTP id t124mr7053142wmb.124.1525084231808; Mon, 30 Apr 2018 03:30:31 -0700 (PDT) Received: from dell ([2.27.167.55]) by smtp.gmail.com with ESMTPSA id p10-v6sm6932164wre.77.2018.04.30.03.30.30 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 30 Apr 2018 03:30:31 -0700 (PDT) Date: Mon, 30 Apr 2018 11:30:29 +0100 From: Lee Jones To: matthias.bgg@kernel.org Cc: ulrich.hecht+renesas@gmail.com, laurent.pinchart@ideasonboard.com, ck.hu@mediatek.com, p.zabel@pengutronix.de, airlied@linux.ie, robh+dt@kernel.org, mark.rutland@arm.com, mturquette@baylibre.com, sboyd@codeaurora.org, davem@davemloft.net, gregkh@linuxfoundation.org, mchehab@kernel.org, rdunlap@infradead.org, sean.wang@mediatek.com, linux-clk@vger.kernel.org, linux@armlinux.org.uk, matthias.bgg@gmail.com, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Matthias Brugger Subject: Re: [v3 01/10] dt-bindings: mediatek: mmsys: Add support for mfd Message-ID: <20180430103029.GD5147@dell> References: <64ca273429d92f581568a48f3efe6035af65f579.1524820923.git.mbrugger@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <64ca273429d92f581568a48f3efe6035af65f579.1524820923.git.mbrugger@suse.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 27 Apr 2018, matthias.bgg@kernel.org wrote: > From: Matthias Brugger > > Add binding description for the mmsys mfd for some Mediatek > devices. mmsys has some registers to control clock gates (which is > used in the clk driver) and some registers to set the routing and enable > the differnet blocks of the display subsystem. > > Signed-off-by: Matthias Brugger > --- > .../bindings/arm/mediatek/mediatek,mmsys.txt | 2 -- > .../bindings/display/mediatek/mediatek,disp.txt | 2 +- > .../devicetree/bindings/mfd/mediatek,mmsys.txt | 27 ++++++++++++++++++++++ > 3 files changed, 28 insertions(+), 3 deletions(-) > create mode 100644 Documentation/devicetree/bindings/mfd/mediatek,mmsys.txt > > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt > index 4eb8bbe15c01..4468345f8b1a 100644 > --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt > @@ -6,10 +6,8 @@ The Mediatek mmsys controller provides various clocks to the system. > Required Properties: > > - compatible: Should be one of: > - - "mediatek,mt2701-mmsys", "syscon" > - "mediatek,mt2712-mmsys", "syscon" > - "mediatek,mt6797-mmsys", "syscon" > - - "mediatek,mt8173-mmsys", "syscon" > - #clock-cells: Must be 1 > > The mmsys controller uses the common clk binding from > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt > index 383183a89164..85a3b4ec06cd 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt > @@ -9,7 +9,7 @@ function block. > > All DISP device tree nodes must be siblings to the central MMSYS_CONFIG node. > For a description of the MMSYS_CONFIG binding, see > -Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt. > +Documentation/devicetree/bindings/mfd/mediatek,mmsys.txt > > DISP function blocks > ==================== > diff --git a/Documentation/devicetree/bindings/mfd/mediatek,mmsys.txt b/Documentation/devicetree/bindings/mfd/mediatek,mmsys.txt > new file mode 100644 > index 000000000000..2331ae16917e > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/mediatek,mmsys.txt > @@ -0,0 +1,27 @@ > +MediaTek MMSYS Multifunction Device Driver What is "MMSYS"? "Multi-Function Driver"s are specific to Linux. What actually is the device? > +MMSYS is a multifunction device with the following sub modules: > +- clocks for the multi-media subsystem > +- central node for the DRM subsystem. > + > +This document describes the binding for MFD device. The MFD takes care to initailize > +the clock driver and the DRM driver. More info see > +Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt > + > +Required properties: > +- compatible: Should be one of: > + - "mediatek,mt2701-mmsys", "syscon" > + - "mediatek,mt8173-mmsys", "syscon" > +- #clock-cells: Must be 1 > + > +Optional properties: > +- power-domains: list of powerdomains needed for the subsystem to work > + > +Example: > + > +mmsys: clock-controller@14000000 { > + compatible = "mediatek,mt8173-mmsys", "syscon"; > + reg = <0 0x14000000 0 0x1000>; > + power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>; > + #clock-cells = <1>; > +}; -- Lee Jones [李琼斯] Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog