linux-kernel - Re: [PATCH v4 2/4] dt-bindings: sound: add rockchip i2s-tdm binding

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: <20210920114914.GC4192@sirena.org.uk>
Date:   Mon, 20 Sep 2021 12:49:14 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Nicolas Frattaroli <frattaroli.nicolas@...il.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Heiko Stuebner <heiko@...ech.de>,
        linux-rockchip@...ts.infradead.org, alsa-devel@...a-project.org,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 2/4] dt-bindings: sound: add rockchip i2s-tdm binding

On Sun, Sep 19, 2021 at 07:38:47PM +0200, Nicolas Frattaroli wrote:

> Going forward, what would be a solution that is acceptable for upstream? As 
> far as I understand, the obvious route here is to drop the rockchip,fsync-
> half-frame property and just always set this mode when we're using a TDM bus 
> format. Is this correct?

Yes.

> According to the TRM, the register bit this sets only affects TDM modes. 
> Though since TDM is not standardised in any way from what I've read online, it 
> is possible that there is hardware out there which expects the non-fsync-half-
> frame mode, but I am completely fine with only thinking about this hardware 
> when it actually surfaces.

Right, we can figure it out later.

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