From: Rob Herring <robh@kernel.org>
To: Henry Chen <henryc.chen@mediatek.com>
Cc: Georgi Djakov <georgi.djakov@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Stephen Boyd <swboyd@chromium.org>,
Ryan Case <ryandcase@chromium.org>,
Mark Rutland <mark.rutland@arm.com>,
Nicolas Boichat <drinkcat@google.com>,
Fan Chen <fan.chen@mediatek.com>,
James Liao <jamesjj.liao@mediatek.com>,
Arvin Wang <arvin.wang@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH V8 01/12] dt-bindings: soc: Add dvfsrc driver bindings
Date: Fri, 5 Feb 2021 14:43:06 -0600 [thread overview]
Message-ID: <20210205204306.GA3692875@robh.at.kernel.org> (raw)
In-Reply-To: <1611648234-15043-2-git-send-email-henryc.chen@mediatek.com>
On Tue, Jan 26, 2021 at 04:03:43PM +0800, Henry Chen wrote:
> Document the binding for enabling dvfsrc on MediaTek SoC.
>
> Signed-off-by: Henry Chen <henryc.chen@mediatek.com>
> ---
> .../devicetree/bindings/soc/mediatek/dvfsrc.yaml | 67 ++++++++++++++++++++++
> include/dt-bindings/interconnect/mtk,mt8183-emi.h | 21 +++++++
> 2 files changed, 88 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/mediatek/dvfsrc.yaml
> create mode 100644 include/dt-bindings/interconnect/mtk,mt8183-emi.h
>
> diff --git a/Documentation/devicetree/bindings/soc/mediatek/dvfsrc.yaml b/Documentation/devicetree/bindings/soc/mediatek/dvfsrc.yaml
> new file mode 100644
> index 0000000..0b746a8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/mediatek/dvfsrc.yaml
> @@ -0,0 +1,67 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/soc/mediatek/dvfsrc.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: MediaTek dynamic voltage and frequency scaling resource collector (DVFSRC)
> +
> +description: |
> + The Dynamic Voltage and Frequency Scaling Resource Collector (DVFSRC) is a
> + HW module which is used to collect all the requests from both software and
> + hardware and turn into the decision of minimum operating voltage and minimum
> + DRAM frequency to fulfill those requests.
> +
> +maintainers:
> + - henryc.chen <henryc.chen@mediatek.com>
> +
> +properties:
> + reg:
> + description: DVFSRC common register address and length.
maxItems: 1
> +
> + compatible:
> + enum:
> + - mediatek,mt6873-dvfsrc
> + - mediatek,mt8183-dvfsrc
> + - mediatek,mt8192-dvfsrc
> +
> + '#interconnect-cells':
> + const: 1
> +
> +patternProperties:
> + dvfsrc-vcore:
Not a pattern. Move to 'properties'.
> + type: object
> + description:
> + The DVFSRC regulator is modelled as a subdevice of the DVFSRC.
> + Because DVFSRC can request power directly via register read/write, likes
> + vcore which is a core power of mt8183. As such, the DVFSRC regulator
> + requires that DVFSRC nodes be present.
> + $ref: /schemas/regulator/regulator.yaml#
> +
> +required:
> + - compatible
> + - reg
> + - "#interconnect-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interconnect/mtk,mt8183-emi.h>
> +
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + dvfsrc@10012000 {
> + compatible = "mediatek,mt8183-dvfsrc";
> + reg = <0 0x10012000 0 0x1000>;
> + #interconnect-cells = <1>;
> + dvfsrc_vcore: dvfsrc-vcore {
> + regulator-name = "dvfsrc-vcore";
> + regulator-min-microvolt = <725000>;
> + regulator-max-microvolt = <800000>;
> + regulator-always-on;
> + };
> + };
> + };
> diff --git a/include/dt-bindings/interconnect/mtk,mt8183-emi.h b/include/dt-bindings/interconnect/mtk,mt8183-emi.h
> new file mode 100644
> index 0000000..dfd143f
> --- /dev/null
> +++ b/include/dt-bindings/interconnect/mtk,mt8183-emi.h
> @@ -0,0 +1,21 @@
> +/* SPDX-License-Identifier: GPL-2.0
> + *
> + * Copyright (c) 2021 MediaTek Inc.
> + */
> +
> +#ifndef __DT_BINDINGS_INTERCONNECT_MTK_MT8183_EMI_H
> +#define __DT_BINDINGS_INTERCONNECT_MTK_MT8183_EMI_H
> +
> +#define MT8183_SLAVE_DDR_EMI 0
> +#define MT8183_MASTER_MCUSYS 1
> +#define MT8183_MASTER_GPU 2
> +#define MT8183_MASTER_MMSYS 3
> +#define MT8183_MASTER_MM_VPU 4
> +#define MT8183_MASTER_MM_DISP 5
> +#define MT8183_MASTER_MM_VDEC 6
> +#define MT8183_MASTER_MM_VENC 7
> +#define MT8183_MASTER_MM_CAM 8
> +#define MT8183_MASTER_MM_IMG 9
> +#define MT8183_MASTER_MM_MDP 10
> +
> +#endif
> --
> 1.9.1
>
next prev parent reply other threads:[~2021-02-05 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 8:03 [PATCH V8 00/13] Add driver for dvfsrc, support for interconnect Henry Chen
2021-01-26 8:03 ` [PATCH V8 01/12] dt-bindings: soc: Add dvfsrc driver bindings Henry Chen
2021-02-05 20:43 ` Rob Herring [this message]
2021-01-26 8:03 ` [PATCH V8 02/12] soc: mediatek: add header for mediatek SIP interface Henry Chen
2021-01-26 8:03 ` [PATCH V8 03/12] soc: mediatek: add driver for dvfsrc support Henry Chen
2021-01-26 8:03 ` [PATCH V8 04/12] soc: mediatek: add support for mt6873 Henry Chen
2021-01-26 8:03 ` [PATCH V8 05/12] arm64: dts: mt8183: add dvfsrc related nodes Henry Chen
2021-01-26 8:03 ` [PATCH V8 06/12] arm64: dts: mt8192: " Henry Chen
2021-01-26 8:03 ` [PATCH V8 07/12] dt-bindings: interconnect: add MT6873 interconnect dt-bindings Henry Chen
2021-02-05 20:45 ` Rob Herring
2021-01-26 8:03 ` [PATCH V8 08/12] interconnect: mediatek: Add interconnect provider driver Henry Chen
2021-01-26 8:03 ` [PATCH V8 09/12] arm64: dts: mt8183: add dvfsrc related nodes Henry Chen
2021-01-26 8:03 ` [PATCH V8 10/12] arm64: dts: mt8192: " Henry Chen
2021-01-26 8:03 ` [PATCH V8 11/12] arm64: dts: mt8183: add dvfsrc regulator nodes Henry Chen
2021-01-26 8:03 ` [PATCH V8 12/12] arm64: dts: mt8192: " Henry Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210205204306.GA3692875@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=arvin.wang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@google.com \
--cc=fan.chen@mediatek.com \
--cc=georgi.djakov@linaro.org \
--cc=henryc.chen@mediatek.com \
--cc=jamesjj.liao@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=ryandcase@chromium.org \
--cc=swboyd@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).