| Message ID | 1435633127-31952-3-git-send-email-jamesjj.liao@mediatek.com |
|---|---|
| State | Superseded, archived |
| Headers | show |
On Tue, Jun 30, 2015 at 10:58 AM, James Liao <jamesjj.liao@mediatek.com> wrote: > > This adds the binding documentation for the mmsys, imgsys, vdecsys, > vencsys and vencltsys controllers found on Mediatek SoCs. > > Signed-off-by: James Liao <jamesjj.liao@mediatek.com> > --- > .../bindings/arm/mediatek/mediatek,imgsys.txt | 22 ++++++++++++++++++++++ > .../bindings/arm/mediatek/mediatek,mmsys.txt | 22 ++++++++++++++++++++++ > .../bindings/arm/mediatek/mediatek,vdecsys.txt | 22 ++++++++++++++++++++++ > .../bindings/arm/mediatek/mediatek,vencltsys.txt | 22 ++++++++++++++++++++++ > .../bindings/arm/mediatek/mediatek,vencsys.txt | 22 ++++++++++++++++++++++ > 5 files changed, 110 insertions(+) > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt > > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt > new file mode 100644 > index 0000000..7612bac > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt > @@ -0,0 +1,22 @@ > +Mediatek imgsys controller > +============================ > + > +The Mediatek imgsys controller provides various clocks to the system. > + > +Required Properties: > + > +- compatible: Should be: > + - "mediatek,mt8173-imgsys", "syscon" > +- #clock-cells: Must be 1 > + > +The imgsys controller uses the common clk binding from > +Documentation/devicetree/bindings/clock/clock-bindings.txt > +The available clocks are defined in dt-bindings/clock/mt*-clk.h. > + > +Example: > + > +imgsys: imgsys@15000000 { Since these nodes will be supplying clocks to the rest of the system, I think the "name" part of each of these should all be "clock-controller", like topckgen and apmixedsys: imgsys: clock-controller@15000000 { -Dan > > + compatible = "mediatek,mt8173-imgsys", "syscon"; > + reg = <0 0x15000000 0 0x1000>; > + #clock-cells = <1>; > +}; > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt > new file mode 100644 > index 0000000..b51e417 > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt > @@ -0,0 +1,22 @@ > +Mediatek mmsys controller > +============================ > + > +The Mediatek mmsys controller provides various clocks to the system. > + > +Required Properties: > + > +- compatible: Should be: > + - "mediatek,mt8173-mmsys", "syscon" > +- #clock-cells: Must be 1 > + > +The mmsys controller uses the common clk binding from > +Documentation/devicetree/bindings/clock/clock-bindings.txt > +The available clocks are defined in dt-bindings/clock/mt*-clk.h. > + > +Example: > + > +mmsys: mmsys@14000000 { > + compatible = "mediatek,mt8173-mmsys", "syscon"; > + reg = <0 0x14000000 0 0x1000>; > + #clock-cells = <1>; > +}; > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt > new file mode 100644 > index 0000000..a5b94a7 > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt > @@ -0,0 +1,22 @@ > +Mediatek vdecsys controller > +============================ > + > +The Mediatek vdecsys controller provides various clocks to the system. > + > +Required Properties: > + > +- compatible: Should be: > + - "mediatek,mt8173-vdecsys", "syscon" > +- #clock-cells: Must be 1 > + > +The vdecsys controller uses the common clk binding from > +Documentation/devicetree/bindings/clock/clock-bindings.txt > +The available clocks are defined in dt-bindings/clock/mt*-clk.h. > + > +Example: > + > +vdecsys: vdecsys@16000000 { > + compatible = "mediatek,mt8173-vdecsys", "syscon"; > + reg = <0 0x16000000 0 0x1000>; > + #clock-cells = <1>; > +}; > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt > new file mode 100644 > index 0000000..3d4e8d8 > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt > @@ -0,0 +1,22 @@ > +Mediatek vencltsys controller > +============================ > + > +The Mediatek vencltsys controller provides various clocks to the system. > + > +Required Properties: > + > +- compatible: Should be: > + - "mediatek,mt8173-vencltsys", "syscon" > +- #clock-cells: Must be 1 > + > +The vencltsys controller uses the common clk binding from > +Documentation/devicetree/bindings/clock/clock-bindings.txt > +The available clocks are defined in dt-bindings/clock/mt*-clk.h. > + > +Example: > + > +vencltsys: vencltsys@19000000 { > + compatible = "mediatek,mt8173-vencltsys", "syscon"; > + reg = <0 0x19000000 0 0x1000>; > + #clock-cells = <1>; > +}; > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt > new file mode 100644 > index 0000000..e5b72f5 > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt > @@ -0,0 +1,22 @@ > +Mediatek vencsys controller > +============================ > + > +The Mediatek vencsys controller provides various clocks to the system. > + > +Required Properties: > + > +- compatible: Should be: > + - "mediatek,mt8173-vencsys", "syscon" > +- #clock-cells: Must be 1 > + > +The vencsys controller uses the common clk binding from > +Documentation/devicetree/bindings/clock/clock-bindings.txt > +The available clocks are defined in dt-bindings/clock/mt*-clk.h. > + > +Example: > + > +vencsys: vencsys@18000000 { > + compatible = "mediatek,mt8173-vencsys", "syscon"; > + reg = <0 0x18000000 0 0x1000>; > + #clock-cells = <1>; > +}; > -- > 1.8.1.1.dirty > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Jun 29, 2015 at 9:58 PM, James Liao <jamesjj.liao@mediatek.com> wrote: > This adds the binding documentation for the mmsys, imgsys, vdecsys, > vencsys and vencltsys controllers found on Mediatek SoCs. > > Signed-off-by: James Liao <jamesjj.liao@mediatek.com> > --- > .../bindings/arm/mediatek/mediatek,imgsys.txt | 22 ++++++++++++++++++++++ > .../bindings/arm/mediatek/mediatek,mmsys.txt | 22 ++++++++++++++++++++++ > .../bindings/arm/mediatek/mediatek,vdecsys.txt | 22 ++++++++++++++++++++++ > .../bindings/arm/mediatek/mediatek,vencltsys.txt | 22 ++++++++++++++++++++++ > .../bindings/arm/mediatek/mediatek,vencsys.txt | 22 ++++++++++++++++++++++ > 5 files changed, 110 insertions(+) > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt > > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt > new file mode 100644 > index 0000000..7612bac > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt > @@ -0,0 +1,22 @@ > +Mediatek imgsys controller > +============================ > + > +The Mediatek imgsys controller provides various clocks to the system. Perhaps some detail on what clocks exactly. > + > +Required Properties: > + > +- compatible: Should be: > + - "mediatek,mt8173-imgsys", "syscon" > +- #clock-cells: Must be 1 > + > +The imgsys controller uses the common clk binding from > +Documentation/devicetree/bindings/clock/clock-bindings.txt > +The available clocks are defined in dt-bindings/clock/mt*-clk.h. The header should be part of this patch as it is part of the binding doc. Same comments apply to the other files. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Daniel, > > +Required Properties: > > + > > +- compatible: Should be: > > + - "mediatek,mt8173-imgsys", "syscon" > > +- #clock-cells: Must be 1 > > + > > +The imgsys controller uses the common clk binding from > > +Documentation/devicetree/bindings/clock/clock-bindings.txt > > +The available clocks are defined in dt-bindings/clock/mt*-clk.h. > > + > > +Example: > > + > > +imgsys: imgsys@15000000 { > > Since these nodes will be supplying clocks to the rest of the system, > I think the "name" part of each of these should all be > "clock-controller", like topckgen and apmixedsys: > > imgsys: clock-controller@15000000 { These subsystems (and topckgen also) also contains other functions such as reset controller, which may be implemented in clk/mediatek/ in the future. It is suitable to use "clock-controller" as their name? Best regards, James -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Jul 2, 2015 at 10:52 AM, James Liao <jamesjj.liao@mediatek.com> wrote: > Hi Daniel, > >> > +Required Properties: >> > + >> > +- compatible: Should be: >> > + - "mediatek,mt8173-imgsys", "syscon" >> > +- #clock-cells: Must be 1 >> > + >> > +The imgsys controller uses the common clk binding from >> > +Documentation/devicetree/bindings/clock/clock-bindings.txt >> > +The available clocks are defined in dt-bindings/clock/mt*-clk.h. >> > + >> > +Example: >> > + >> > +imgsys: imgsys@15000000 { >> >> Since these nodes will be supplying clocks to the rest of the system, >> I think the "name" part of each of these should all be >> "clock-controller", like topckgen and apmixedsys: >> >> imgsys: clock-controller@15000000 { > > These subsystems (and topckgen also) also contains other functions such > as reset controller, which may be implemented in clk/mediatek/ in the > future. It is suitable to use "clock-controller" as their name? Hmm, I don't know the "right way" to do this either. Pardon me if you've already had these discussions. I only recently started looking at these clock nodes in detail :-). I think what we really have in register space is a "syscon", as described in [0]: [0] Documentation/devicetree/bindings/mfd/syscon.txt So, we can define this block of registers as a syscon: mmsys_syscon: syscon@14000000 { compatible = "mediatek,mt8173-mmsys", "syscon"; reg = <0 0x14000000 0 0x1000>; }; Then for the clock controller functionality, we create a node with a "clock-controller" name and a "-clock" compatible, like this: mmsys_clock: clock-controller { compatible = "mediatek,mt8173-mmsys-clock"; #clock-cells = <1>; mediatek,syscon = <&mmsys_syscon>; }; You could then do: CLK_OF_DECLARE(mtk_mmsys, "mediatek,mt8173-mmsys-clock", mtk_mmsys_init); If you want to reuse the same register range for some other functionality, we could then use a different node, with a different compatible: mmsys: reset-controller { compatible = "mediatek,mt8173-mmsys-reset"; mediatek,syscon = <&mmsys_syscon>; }; What do you think of this approach? Thanks! -Dan -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 07/01/2015 09:26 PM, Daniel Kurtz wrote: > On Thu, Jul 2, 2015 at 10:52 AM, James Liao <jamesjj.liao@mediatek.com> wrote: >> Hi Daniel, >> >>>> +Required Properties: >>>> + >>>> +- compatible: Should be: >>>> + - "mediatek,mt8173-imgsys", "syscon" >>>> +- #clock-cells: Must be 1 >>>> + >>>> +The imgsys controller uses the common clk binding from >>>> +Documentation/devicetree/bindings/clock/clock-bindings.txt >>>> +The available clocks are defined in dt-bindings/clock/mt*-clk.h. >>>> + >>>> +Example: >>>> + >>>> +imgsys: imgsys@15000000 { >>> Since these nodes will be supplying clocks to the rest of the system, >>> I think the "name" part of each of these should all be >>> "clock-controller", like topckgen and apmixedsys: >>> >>> imgsys: clock-controller@15000000 { >> These subsystems (and topckgen also) also contains other functions such >> as reset controller, which may be implemented in clk/mediatek/ in the >> future. It is suitable to use "clock-controller" as their name? > Hmm, > > I don't know the "right way" to do this either. > Pardon me if you've already had these discussions. > I only recently started looking at these clock nodes in detail :-). > > I think what we really have in register space is a "syscon", as > described in [0]: > [0] Documentation/devicetree/bindings/mfd/syscon.txt > > So, we can define this block of registers as a syscon: > > mmsys_syscon: syscon@14000000 { > compatible = "mediatek,mt8173-mmsys", "syscon"; > reg = <0 0x14000000 0 0x1000>; > }; > > > Then for the clock controller functionality, we create a node with a > "clock-controller" name and a "-clock" compatible, like this: > > mmsys_clock: clock-controller { > compatible = "mediatek,mt8173-mmsys-clock"; > #clock-cells = <1>; > mediatek,syscon = <&mmsys_syscon>; > }; > > You could then do: > CLK_OF_DECLARE(mtk_mmsys, "mediatek,mt8173-mmsys-clock", mtk_mmsys_init); > > > If you want to reuse the same register range for some other > functionality, we could then use a different node, with a different > compatible: > > mmsys: reset-controller { > compatible = "mediatek,mt8173-mmsys-reset"; > mediatek,syscon = <&mmsys_syscon>; > }; > > What do you think of this approach? DT nodes typically have a reg property. Not having a reg property is a good indicator of a problem with the binding. A syscon is used when you have a DT node with a reg property and some driver attached to it, but you need to poke some bits in another register region that isn't part of the reg property. Instead of having multiple nodes with two reg properties where the second one is the same, we use a phandle and a syscon. If clock-controller isn't acceptable maybe clock-reset-contoller would work? Or "power-controller"? We certainly shouldn't be making up multiple nodes for one hardware block. Of course, the subject of the patch is "bindings for clock controllers", so it may be that the registers are predominantly clock related and so the name is appropriate already.
On Fri, Jul 3, 2015 at 7:40 AM, Stephen Boyd <sboyd@codeaurora.org> wrote: > On 07/01/2015 09:26 PM, Daniel Kurtz wrote: >> On Thu, Jul 2, 2015 at 10:52 AM, James Liao <jamesjj.liao@mediatek.com> wrote: >>> Hi Daniel, >>> >>>>> +Required Properties: >>>>> + >>>>> +- compatible: Should be: >>>>> + - "mediatek,mt8173-imgsys", "syscon" >>>>> +- #clock-cells: Must be 1 >>>>> + >>>>> +The imgsys controller uses the common clk binding from >>>>> +Documentation/devicetree/bindings/clock/clock-bindings.txt >>>>> +The available clocks are defined in dt-bindings/clock/mt*-clk.h. >>>>> + >>>>> +Example: >>>>> + >>>>> +imgsys: imgsys@15000000 { >>>> Since these nodes will be supplying clocks to the rest of the system, >>>> I think the "name" part of each of these should all be >>>> "clock-controller", like topckgen and apmixedsys: >>>> >>>> imgsys: clock-controller@15000000 { >>> These subsystems (and topckgen also) also contains other functions such >>> as reset controller, which may be implemented in clk/mediatek/ in the >>> future. It is suitable to use "clock-controller" as their name? >> Hmm, >> >> I don't know the "right way" to do this either. >> Pardon me if you've already had these discussions. >> I only recently started looking at these clock nodes in detail :-). >> >> I think what we really have in register space is a "syscon", as >> described in [0]: >> [0] Documentation/devicetree/bindings/mfd/syscon.txt >> >> So, we can define this block of registers as a syscon: >> >> mmsys_syscon: syscon@14000000 { >> compatible = "mediatek,mt8173-mmsys", "syscon"; >> reg = <0 0x14000000 0 0x1000>; >> }; >> >> >> Then for the clock controller functionality, we create a node with a >> "clock-controller" name and a "-clock" compatible, like this: >> >> mmsys_clock: clock-controller { >> compatible = "mediatek,mt8173-mmsys-clock"; >> #clock-cells = <1>; >> mediatek,syscon = <&mmsys_syscon>; >> }; >> >> You could then do: >> CLK_OF_DECLARE(mtk_mmsys, "mediatek,mt8173-mmsys-clock", mtk_mmsys_init); >> >> >> If you want to reuse the same register range for some other >> functionality, we could then use a different node, with a different >> compatible: >> >> mmsys: reset-controller { >> compatible = "mediatek,mt8173-mmsys-reset"; >> mediatek,syscon = <&mmsys_syscon>; >> }; >> >> What do you think of this approach? > > DT nodes typically have a reg property. Not having a reg property is a > good indicator of a problem with the binding. A syscon is used when you > have a DT node with a reg property and some driver attached to it, but > you need to poke some bits in another register region that isn't part of > the reg property. Instead of having multiple nodes with two reg > properties where the second one is the same, we use a phandle and a syscon. > > If clock-controller isn't acceptable maybe clock-reset-contoller would > work? Or "power-controller"? We certainly shouldn't be making up > multiple nodes for one hardware block. Of course, the subject of the > patch is "bindings for clock controllers", so it may be that the > registers are predominantly clock related and so the name is appropriate > already. Using "clock-controller" seems to fit best with the bindings introduced by this patch. However, if these bindings are for hardware blocks that contain a grab bag of various functionality that will be added in later patches, then I think "syscon" might be best. -Dan > > -- > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, > a Linux Foundation Collaborative Project > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Daniel, On Fri, 2015-07-03 at 18:46 +0800, Daniel Kurtz wrote: > On Fri, Jul 3, 2015 at 7:40 AM, Stephen Boyd <sboyd@codeaurora.org> wrote: > > DT nodes typically have a reg property. Not having a reg property is a > > good indicator of a problem with the binding. A syscon is used when you > > have a DT node with a reg property and some driver attached to it, but > > you need to poke some bits in another register region that isn't part of > > the reg property. Instead of having multiple nodes with two reg > > properties where the second one is the same, we use a phandle and a syscon. > > > > If clock-controller isn't acceptable maybe clock-reset-contoller would > > work? Or "power-controller"? We certainly shouldn't be making up > > multiple nodes for one hardware block. Of course, the subject of the > > patch is "bindings for clock controllers", so it may be that the > > registers are predominantly clock related and so the name is appropriate > > already. > > Using "clock-controller" seems to fit best with the bindings > introduced by this patch. > > However, if these bindings are for hardware blocks that contain a grab > bag of various functionality that will be added in later patches, then > I think "syscon" might be best. I referred some dt-binding documents that contain clock and reset controller in the same unit: qcom,gcc.txt: clock-controller@900000 { compatible = "qcom,gcc-msm8960"; nvidia,tegra124-car.txt: tegra_car: clock { compatible = "nvidia,tegra124-car"; rockchip,rk3188-cru.txt: cru: cru@20000000 { compatible = "rockchip,rk3188-cru"; Rockchip use "Clock and Reset Unit" as their controller's name. The other two use "clock" or "clock-controller" as their controller's name. It looks like "clock-controller" is also an acceptable name for clock/reset controllers. So I would like to keep this name in next patch. Best regards, James -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt new file mode 100644 index 0000000..7612bac --- /dev/null +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt @@ -0,0 +1,22 @@ +Mediatek imgsys controller +============================ + +The Mediatek imgsys controller provides various clocks to the system. + +Required Properties: + +- compatible: Should be: + - "mediatek,mt8173-imgsys", "syscon" +- #clock-cells: Must be 1 + +The imgsys controller uses the common clk binding from +Documentation/devicetree/bindings/clock/clock-bindings.txt +The available clocks are defined in dt-bindings/clock/mt*-clk.h. + +Example: + +imgsys: imgsys@15000000 { + compatible = "mediatek,mt8173-imgsys", "syscon"; + reg = <0 0x15000000 0 0x1000>; + #clock-cells = <1>; +}; diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt new file mode 100644 index 0000000..b51e417 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt @@ -0,0 +1,22 @@ +Mediatek mmsys controller +============================ + +The Mediatek mmsys controller provides various clocks to the system. + +Required Properties: + +- compatible: Should be: + - "mediatek,mt8173-mmsys", "syscon" +- #clock-cells: Must be 1 + +The mmsys controller uses the common clk binding from +Documentation/devicetree/bindings/clock/clock-bindings.txt +The available clocks are defined in dt-bindings/clock/mt*-clk.h. + +Example: + +mmsys: mmsys@14000000 { + compatible = "mediatek,mt8173-mmsys", "syscon"; + reg = <0 0x14000000 0 0x1000>; + #clock-cells = <1>; +}; diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt new file mode 100644 index 0000000..a5b94a7 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt @@ -0,0 +1,22 @@ +Mediatek vdecsys controller +============================ + +The Mediatek vdecsys controller provides various clocks to the system. + +Required Properties: + +- compatible: Should be: + - "mediatek,mt8173-vdecsys", "syscon" +- #clock-cells: Must be 1 + +The vdecsys controller uses the common clk binding from +Documentation/devicetree/bindings/clock/clock-bindings.txt +The available clocks are defined in dt-bindings/clock/mt*-clk.h. + +Example: + +vdecsys: vdecsys@16000000 { + compatible = "mediatek,mt8173-vdecsys", "syscon"; + reg = <0 0x16000000 0 0x1000>; + #clock-cells = <1>; +}; diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt new file mode 100644 index 0000000..3d4e8d8 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt @@ -0,0 +1,22 @@ +Mediatek vencltsys controller +============================ + +The Mediatek vencltsys controller provides various clocks to the system. + +Required Properties: + +- compatible: Should be: + - "mediatek,mt8173-vencltsys", "syscon" +- #clock-cells: Must be 1 + +The vencltsys controller uses the common clk binding from +Documentation/devicetree/bindings/clock/clock-bindings.txt +The available clocks are defined in dt-bindings/clock/mt*-clk.h. + +Example: + +vencltsys: vencltsys@19000000 { + compatible = "mediatek,mt8173-vencltsys", "syscon"; + reg = <0 0x19000000 0 0x1000>; + #clock-cells = <1>; +}; diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt new file mode 100644 index 0000000..e5b72f5 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt @@ -0,0 +1,22 @@ +Mediatek vencsys controller +============================ + +The Mediatek vencsys controller provides various clocks to the system. + +Required Properties: + +- compatible: Should be: + - "mediatek,mt8173-vencsys", "syscon" +- #clock-cells: Must be 1 + +The vencsys controller uses the common clk binding from +Documentation/devicetree/bindings/clock/clock-bindings.txt +The available clocks are defined in dt-bindings/clock/mt*-clk.h. + +Example: + +vencsys: vencsys@18000000 { + compatible = "mediatek,mt8173-vencsys", "syscon"; + reg = <0 0x18000000 0 0x1000>; + #clock-cells = <1>; +};
This adds the binding documentation for the mmsys, imgsys, vdecsys, vencsys and vencltsys controllers found on Mediatek SoCs. Signed-off-by: James Liao <jamesjj.liao@mediatek.com> --- .../bindings/arm/mediatek/mediatek,imgsys.txt | 22 ++++++++++++++++++++++ .../bindings/arm/mediatek/mediatek,mmsys.txt | 22 ++++++++++++++++++++++ .../bindings/arm/mediatek/mediatek,vdecsys.txt | 22 ++++++++++++++++++++++ .../bindings/arm/mediatek/mediatek,vencltsys.txt | 22 ++++++++++++++++++++++ .../bindings/arm/mediatek/mediatek,vencsys.txt | 22 ++++++++++++++++++++++ 5 files changed, 110 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt