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] [day] [month] [year] [list]
Message-ID: <YK3wLgJSy0sVUn51@atomide.com>
Date:   Wed, 26 May 2021 09:52:30 +0300
From:   Tony Lindgren <tony@...mide.com>
To:     Vignesh Raghavendra <vigneshr@...com>
Cc:     Grygorii Strashko <grygorii.strashko@...com>,
        Andreas Kemnade <andreas@...nade.info>,
        Rob Herring <robh+dt@...nel.org>, linux-omap@...r.kernel.org,
        linux-i2c@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
        Nishanth Menon <nm@...com>
Subject: Re: [PATCH v2] dt-bindings: i2c: Move i2c-omap.txt to YAML format

* Vignesh Raghavendra <vigneshr@...com> [210510 11:06]:
> What do you prefer here? Removing dmas from schema would mean I would
> have to delete dmas property from omap2/3 dtsi files that list dmas
> property today? Note that driver does not support DMA mode today.

If the dma channels are not used by the driver, and not in the binding,
it's unlikely they will ever get used. Sure the dma channels describe
the hardware, and there's a slim chance some other OS needs them, but I
doubt it.

It seems weird we stop describing hardware in the devicetree to avoid
binding check warnings though. Up to you to figure out what you want
to do as far as I'm concerned.

Regards,

Tony

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ