linux-kernel - Re: [PATCH v4 2/6] dt-bindings: ARM: Mediatek: Document bindings for MT2701

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 1 Feb 2016 09:55:53 -0600
From:	Rob Herring <robh@...nel.org>
To:	James Liao <jamesjj.liao@...iatek.com>
Cc:	Matthias Brugger <matthias.bgg@...il.com>,
	Mike Turquette <mturquette@...libre.com>,
	Stephen Boyd <sboyd@...eaurora.org>,
	John Crispin <blogic@...nwrt.org>,
	Sascha Hauer <kernel@...gutronix.de>,
	Daniel Kurtz <djkurtz@...omium.org>,
	Philipp Zabel <p.zabel@...gutronix.de>,
	srv_heupstream@...iatek.com,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-mediatek@...ts.infradead.org,
	linux-clk <linux-clk@...r.kernel.org>
Subject: Re: [PATCH v4 2/6] dt-bindings: ARM: Mediatek: Document bindings for MT2701

On Wed, Jan 20, 2016 at 11:18 PM, James Liao <jamesjj.liao@...iatek.com> wrote:
> Hi Rob,
>
> On Wed, 2016-01-20 at 10:32 -0600, Rob Herring wrote:
>> On Wed, Jan 20, 2016 at 02:35:43PM +0800, James Liao wrote:
>> > This patch adds the binding documentation for apmixedsys, bdpsys,
>> > ethsys, hifsys, imgsys, infracfg, mmsys, pericfg, topckgen and
>> > vdecsys for Mediatek MT2701.
>> >
>> > Signed-off-by: James Liao <jamesjj.liao@...iatek.com>
>> > Tested-by: John Crispin <blogic@...nwrt.org>
>> > ---
>> >  .../bindings/arm/mediatek/mediatek,apmixedsys.txt  |  1 +
>> >  .../bindings/arm/mediatek/mediatek,bdpsys.txt      | 22 ++++++++++++++++++++++
>> >  .../bindings/arm/mediatek/mediatek,ethsys.txt      | 22 ++++++++++++++++++++++
>> >  .../bindings/arm/mediatek/mediatek,hifsys.txt      | 22 ++++++++++++++++++++++
>> >  .../bindings/arm/mediatek/mediatek,imgsys.txt      |  1 +
>> >  .../bindings/arm/mediatek/mediatek,infracfg.txt    |  1 +
>> >  .../bindings/arm/mediatek/mediatek,mmsys.txt       |  1 +
>> >  .../bindings/arm/mediatek/mediatek,pericfg.txt     |  1 +
>> >  .../bindings/arm/mediatek/mediatek,topckgen.txt    |  1 +
>> >  .../bindings/arm/mediatek/mediatek,vdecsys.txt     |  1 +
>> >  10 files changed, 73 insertions(+)
>> >  create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,bdpsys.txt
>> >  create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,ethsys.txt
>> >  create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,hifsys.txt
>> >
>> > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,apmixedsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,apmixedsys.txt
>> > index 936166f..a701e19 100644
>> > --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,apmixedsys.txt
>> > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,apmixedsys.txt
>> > @@ -6,6 +6,7 @@ The Mediatek apmixedsys controller provides the PLLs to the system.
>> >  Required Properties:
>> >
>> >  - compatible: Should be:
>> > +   - "mediatek,mt2701-apmixedsys"
>> >     - "mediatek,mt8135-apmixedsys"
>> >     - "mediatek,mt8173-apmixedsys"
>> >  - #clock-cells: Must be 1
>> > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,bdpsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,bdpsys.txt
>> > new file mode 100644
>> > index 0000000..4137196
>> > --- /dev/null
>> > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,bdpsys.txt
>> > @@ -0,0 +1,22 @@
>> > +Mediatek bdpsys controller
>> > +============================
>> > +
>> > +The Mediatek bdpsys controller provides various clocks to the system.
>>
>> As you clarified these blocks provide more that just clocks. Please list
>> all the functions here and on the others.
>
> Some blocks may provide clock and reset controller at the same time. But

Then say the block provides clocks and resets is all I'm asking for.

> most of them will not provide functions directly. Instead, some DT
> blocks which provide specific functions may refer to these controller
> nodes due to it need to access the same register space.
>
> For example, scpsys (the power domain provider) refers to infracfg
> because it need to control infracfg registers when power on/off domains:
>
>         scpsys: scpsys@...06000 {
>                 compatible = "mediatek,mt2701-scpsys";
>                 #power-domain-cells = <1>;
>                 reg = <0 0x10006000 0 0x1000>;
>                 infracfg = <&infracfg>;
>         };
>
> So I think it should not need to list all functions for each blocks
> here.

Sorry, but you do need to describe what functions the blocks provide.

Also, if you are accessing the infracfg regs directly to modify clock
registers outside of the clock driver, that is very bad design. The
clock driver could assume that register values are not changing behind
its back and it bypasses any locks around register accesses. I can see
why it is needed though, but we really need a proper interface.

Rob