linux-kernel - Re: [PATCH 1/2] ASoC: add support for TAS5805M digital amplifier

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]

Date:   Wed, 12 Jan 2022 20:26:22 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Daniel Beer <daniel.beer@...rinstitute.com>
Cc:     alsa-devel@...a-project.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Andy Liu <andy-liu@...com>,
        Derek Simkowiak <derek.simkowiak@...rinstitute.com>,
        Rob Herring <robh+dt@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH 1/2] ASoC: add support for TAS5805M digital amplifier

On Wed, Jan 12, 2022 at 08:28:06AM +1300, Daniel Beer wrote:

> The blob of register writes we get given from PPC3 contains a whole lot
> of explicit page and book changes, and there's not an easy way to tell
> regmap about this, as far as I know. Do you think it's acceptable to
> stick with explicit paging for this reason, or is there a way to make
> this work with regmap's paging?

That's probably fine.  It's *really* hard to get enthusiastic about this
system design TBH, just injecting a stream of unverified register writes 
is going to make the driver very fragile against changes but I'm not
sure you're going to much better there.

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