From: Chun-Jie Chen <chun-jie.chen@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Stephen Boyd <sboyd@kernel.org>,
Nicolas Boichat <drinkcat@chromium.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <srv_heupstream@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v2 01/15] dt-bindings: ARM: Mediatek: Add new document bindings of MT8186 clock
Date: Thu, 10 Mar 2022 21:36:27 +0800 [thread overview]
Message-ID: <d80c89fd5fb704ed03244a7e333d59d0ee972e8f.camel@mediatek.com> (raw)
In-Reply-To: <YhkmnnIApvU7gRlZ@robh.at.kernel.org>
On Fri, 2022-02-25 at 12:57 -0600, Rob Herring wrote:
> On Mon, Feb 21, 2022 at 09:52:44AM +0800, Chun-Jie Chen wrote:
> > This patch adds the new binding documentation for system clock
> > and functional clock on Mediatek MT8186.
> >
> > Signed-off-by: Chun-Jie Chen <chun-jie.chen@mediatek.com>
> > ---
> > .../arm/mediatek/mediatek,mt8186-clock.yaml | 56 +++
> > .../mediatek/mediatek,mt8186-sys-clock.yaml | 54 +++
> > include/dt-bindings/clock/mt8186-clk.h | 445
> > ++++++++++++++++++
> > 3 files changed, 555 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-
> > clock.yaml
> > create mode 100644
> > Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-sys-
> > clock.yaml
> > create mode 100644 include/dt-bindings/clock/mt8186-clk.h
> >
> > diff --git
> > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-
> > clock.yaml
> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-
> > clock.yaml
> > new file mode 100644
> > index 000000000000..373e8a100da3
> > --- /dev/null
> > +++
> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-
> > clock.yaml
> > @@ -0,0 +1,56 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: "
> > https://urldefense.com/v3/__http://devicetree.org/schemas/arm/mediatek/mediatek,mt8186-clock.yaml*__;Iw!!CTRNKA9wMg0ARbw!xKDeg6ddrFWd8p__fZiG7r5F5Py9NVWCmi7zVue5fUzuxKtvqHCSu_pslcpXRWfJmMCT$
> > "
> > +$schema: "
> > https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml*__;Iw!!CTRNKA9wMg0ARbw!xKDeg6ddrFWd8p__fZiG7r5F5Py9NVWCmi7zVue5fUzuxKtvqHCSu_pslcpXRfM3OA21$
> > "
> > +
> > +title: Mediatek Functional Clock Controller for MT8186
> > +
> > +maintainers:
> > + - Chun-Jie Chen <chun-jie.chen@mediatek.com>
> > +
> > +description:
>
> You need a '|' to preserve the formatting.
>
> > + The clock architecture in Mediatek like below
> > + PLLs -->
> > + dividers -->
> > + muxes
> > + -->
> > + clock gate
> > +
> > + The devices provide clock gate control in different IP blocks.
> > +
> > +properties:
> > + compatible:
> > + items:
> > + - enum:
> > + - mediatek,mt8186-imp_iic_wrap
> > + - mediatek,mt8186-mfgsys
> > + - mediatek,mt8186-wpesys
> > + - mediatek,mt8186-imgsys1
> > + - mediatek,mt8186-imgsys2
> > + - mediatek,mt8186-vdecsys
> > + - mediatek,mt8186-vencsys
> > + - mediatek,mt8186-camsys
> > + - mediatek,mt8186-camsys_rawa
> > + - mediatek,mt8186-camsys_rawb
> > + - mediatek,mt8186-mdpsys
> > + - mediatek,mt8186-ipesys
> > + reg:
> > + maxItems: 1
> > +
> > + '#clock-cells':
> > + const: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + imp_iic_wrap: clock-controller@11017000 {
> > + compatible = "mediatek,mt8186-imp_iic_wrap";
> > + reg = <0x11017000 0x1000>;
> > + #clock-cells = <1>;
> > + };
> > diff --git
> > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-
> > sys-clock.yaml
> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-
> > sys-clock.yaml
> > new file mode 100644
> > index 000000000000..4c071dd66b76
> > --- /dev/null
> > +++
> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-
> > sys-clock.yaml
> > @@ -0,0 +1,54 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: "
> > https://urldefense.com/v3/__http://devicetree.org/schemas/arm/mediatek/mediatek,mt8186-sys-clock.yaml*__;Iw!!CTRNKA9wMg0ARbw!xKDeg6ddrFWd8p__fZiG7r5F5Py9NVWCmi7zVue5fUzuxKtvqHCSu_pslcpXRRtmGvUx$
> > "
> > +$schema: "
> > https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml*__;Iw!!CTRNKA9wMg0ARbw!xKDeg6ddrFWd8p__fZiG7r5F5Py9NVWCmi7zVue5fUzuxKtvqHCSu_pslcpXRfM3OA21$
> > "
> > +
> > +title: Mediatek System Clock Controller for MT8186
> > +
> > +maintainers:
> > + - Chun-Jie Chen <chun-jie.chen@mediatek.com>
> > +
> > +description:
>
> And here.
>
> With that,
>
> Reviewed-by: Rob Herring <robh@kernel.org>
>
Ok, I will fix it in next version.
Thanks!
> > + The clock architecture in Mediatek like below
> > + PLLs -->
> > + dividers -->
> > + muxes
> > + -->
> > + clock gate
> > +
> > + The apmixedsys provides most of PLLs which generated from SoC
> > 26m.
> > + The topckgen provides dividers and muxes which provide the clock
> > source to other IP blocks.
> > + The infracfg_ao provides clock gate in peripheral and
> > infrastructure IP blocks.
> > + The mcusys provides mux control to select the clock source in AP
> > MCU.
> > + The device nodes also provide the system control capacity for
> > configuration.
next prev parent reply other threads:[~2022-03-10 13:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 1:52 [PATCH v2 00/15] Mediatek MT8186 clock support Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 01/15] dt-bindings: ARM: Mediatek: Add new document bindings of MT8186 clock Chun-Jie Chen
2022-02-25 18:57 ` Rob Herring
2022-03-10 13:36 ` Chun-Jie Chen [this message]
2022-03-10 23:45 ` Miles Chen
2022-03-11 4:37 ` Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 02/15] clk: mediatek: Add MT8186 mcusys clock support Chun-Jie Chen
2022-03-09 10:13 ` Chen-Yu Tsai
2022-03-22 8:30 ` Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 03/15] clk: mediatek: Add MT8186 topckgen " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 04/15] clk: mediatek: Add MT8186 infrastructure " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 05/15] clk: mediatek: Add MT8186 apmixedsys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 06/15] clk: mediatek: Add MT8186 imp i2c wrapper " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 07/15] clk: mediatek: Add MT8186 mfgsys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 08/15] clk: mediatek: Add MT8186 mmsys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 09/15] clk: mediatek: Add MT8186 wpesys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 10/15] clk: mediatek: Add MT8186 imgsys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 11/15] clk: mediatek: Add MT8186 vdecsys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 12/15] clk: mediatek: Add MT8186 vencsys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 13/15] clk: mediatek: Add MT8186 camsys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 14/15] clk: mediatek: Add MT8186 mdpsys " Chun-Jie Chen
2022-02-21 1:52 ` [PATCH v2 15/15] clk: mediatek: Add MT8186 ipesys " Chun-Jie 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=d80c89fd5fb704ed03244a7e333d59d0ee972e8f.camel@mediatek.com \
--to=chun-jie.chen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@mediatek.com \
/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).