linux-kernel - Re: [PATCH v2] dt-bindings: omap: Convert omap.txt to yaml

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]

Message-ID: <20230330181506.4d5fcf51@aktux>
Date:   Thu, 30 Mar 2023 18:15:06 +0200
From:   Andreas Kemnade <andreas@...nade.info>
To:     Tony Lindgren <tony@...mide.com>
Cc:     robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org, Andrew Davis <afd@...com>
Subject: Re: [PATCH v2] dt-bindings: omap: Convert omap.txt to yaml

On Thu, 30 Mar 2023 14:39:18 +0300
Tony Lindgren <tony@...mide.com> wrote:

> * Andreas Kemnade <andreas@...nade.info> [230329 22:22]:
> > From: Andrew Davis <afd@...com>
> > 
> > Convert omap.txt to yaml.
> >  Documentation/devicetree/bindings/arm/ti.yaml | 157 ++++++++++++++++++
> >  1 file changed, 157 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/arm/ti.yaml  
> 
> Great, can we also drop the old txt file or is more changes needed before
> we can do that?
>
we have still 
- ti,hwmods: list of hwmod names (ascii strings), that comes from the OMAP
  HW documentation, attached to a device. Must contain at least
  one hwmod.

Optional properties:
- ti,no_idle_on_suspend: When present, it prevents the PM to idle the module
  during suspend.
- ti,no-reset-on-init: When present, the module should not be reset at init
- ti,no-idle-on-init: When present, the module should not be idled at init
- ti,no-idle: When present, the module is never allowed to idle.

These optional properties are not in the root node but in subnodes.
From my guts feeling this belongs in a separate file and should
be somehow dealed with in a second step.

So how to proceed?

BTW: I think this file then also belongs into
OMAP2+ SUPPORT section of MAINTAINERS

Regards,
Andreas