linux-kernel - Re: [PATCH v2 15/18] dt-bindings: sound: Add bindings for Cirrus Logic Madera codecs

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: <20170514100403.nocjlb77q5r3nvo2@sirena.org.uk>
Date:   Sun, 14 May 2017 19:04:03 +0900
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>
Cc:     lee.jones@...aro.org, linus.walleij@...aro.org, gnurou@...il.com,
        robh+dt@...nel.org, tglx@...utronix.de, jason@...edaemon.net,
        alsa-devel@...a-project.org, patches@...nsource.wolfsonmicro.com,
        linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 15/18] dt-bindings: sound: Add bindings for Cirrus
 Logic Madera codecs

On Tue, Apr 25, 2017 at 05:27:44PM +0100, Richard Fitzgerald wrote:
> On Tue, 2017-04-25 at 16:52 +0100, Mark Brown wrote:

> > > +Required properties:
> > > +  - compatible : One of the following chip-specific strings:
> > > +        "cirrus,cs47l35-codec"
> > > +        "cirrus,cs47l85-codec"
> > > +        "cirrus,cs47l90-codec"

> > You shouldn't have compatible strings for subfunctions of a MFD unless
> > these represent meaningful reusable IPs that can exist separately from
> > the parent chip, that's clearly not the case here.  All you're doing
> > here is encoding Linux internal abstractions which aren't OS neutral and
> > might change in future (for example clocking might move more into the
> > clock API).

> While that's nice, the of_node doesn't get populated if there isn't a
> compatible string. And people don't like workarounds for the missing
> of_node.

What workarounds are you referring to?  Why would this need any kind of
workaround, there is no requirement for magic broken nodes like this in
the subsystem and if there is we should fix that rather than bodge the
ABI.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)