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:   Fri, 29 Apr 2022 12:10:13 +0800
From:   Jason-JH Lin <jason-jh.lin@...iatek.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Matthias Brugger <matthias.bgg@...il.com>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>
CC:     Fabien Parent <fparent@...libre.com>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-mediatek@...ts.infradead.org>, CK Hu <ck.hu@...iatek.com>,
        Rex-BC Chen <rex-bc.chen@...iatek.com>,
        Nancy Lin <nancy.lin@...iatek.com>,
        Singo Chang <singo.chang@...iatek.com>,
        <Project_Global_Chrome_Upstream_Group@...iatek.com>
Subject: Re: [PATCH] dt-bindings: arm: mediatek: mmsys: refine power and gce
 properties

Hi Krzysztof,

Thanks for the reviews.

On Thu, 2022-04-28 at 09:16 +0200, Krzysztof Kozlowski wrote:
> On 28/04/2022 03:27, jason-jh.lin wrote:
> > From: "Jason-JH.Lin" <jason-jh.lin@...iatek.com>
> > 
> > Power:
> >   Refine description and add item number for power-domains
> > property.
> > 
> > GCE:
> >   Refine description and add item number for mboxes property and
> >   mediatek,gce-client-reg property.
> > 
> > Fixes: 1da90b8a7bae ("dt-bindings: arm: mediatek: mmsys: add power
> > and gce properties")
> > Signed-off-by: Jason-JH.Lin <jason-jh.lin@...iatek.com>
> > ---
> >  .../bindings/arm/mediatek/mediatek,mmsys.yaml | 29 +++++++++----
> > ------
> >  1 file changed, 14 insertions(+), 15 deletions(-)
> > 
> > diff --git
> > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yam
> > l
> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yam
> > l
> > index 6ad023eec193..6722f1b724ef 100644
> > ---
> > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yam
> > l
> > +++
> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yam
> > l
> > @@ -43,28 +43,27 @@ properties:
> >      maxItems: 1
> >  
> >    power-domains:
> > +    maxItems: 1
> >      description:
> > -      A phandle and PM domain specifier as defined by bindings
> > -      of the power controller specified by phandle. See
> > -      Documentation/devicetree/bindings/power/power-domain.yaml
> > for details.
> > +      Each mmsys belongs to a power-domains. If mmsys wants to use
> > PM
> > +      interface to control the power controller of mmsys, it
> > should have
> > +      this property.
> >  
> >    mboxes:
> > +    minItems: 1
> 
> maxItems, surely you cannot have infinite number of mailboxes to talk
> with?

Yes, we cannot have infinite number for this, but we can use not only
one mbox channel for one mmsys.

Its maximum number is equal to GCE HW thread number.
The maximum number in mt8195 is 24 and mt8173 is 16.

But we currently using 1.
So I'm not sure if I need to set the maxItems for this?

> 
> >      description:
> > -      Using mailbox to communicate with GCE, it should have this
> > -      property and list of phandle, mailbox specifiers. See
> > -      Documentation/devicetree/bindings/mailbox/mtk-gce.txt for
> > details.
> > -    $ref: /schemas/types.yaml#/definitions/phandle-array
> > +      If using mailbox to communicate with GCE, it should have
> > this
> > +      property. GCE will help configure the hardware settings for
> > the
> > +      current mmsys data pipeline.
> >  
> >    mediatek,gce-client-reg:
> > -    description:
> > -      The register of client driver can be configured by gce with
> > 4 arguments
> > -      defined in this property, such as phandle of gce, subsys id,
> > -      register offset and size.
> > -      Each subsys id is mapping to a base address of display
> > function blocks
> > -      register which is defined in the gce header
> > -      include/dt-bindings/gce/<chip>-gce.h.
> > -    $ref: /schemas/types.yaml#/definitions/phandle-array
> 
> Why removing ref? Does your binding work after such change?

I removed it unexpectedly, I'll add it back.
> 
> >      maxItems: 1
> > +    items:
> > +      - items:
> > +          - description: phandle to GCE
> > +          - description: subsys id
> > +          - description: register offset
> > +          - description: register size
> >  
> >    "#clock-cells":
> >      const: 1
> 
> 
> Best regards,
> Krzysztof

Regards,
Jason-JH.Lin
-- 
Jason-JH Lin <jason-jh.lin@...iatek.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ