linux-kernel - Re: [PATCH lora-next] net: lora: sx1301: Fix radio SPI write

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: <20181231182904.GJ1846@sirena.org.uk>
Date:   Mon, 31 Dec 2018 18:29:04 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Ben Whitten <benwhitten@...il.com>
Cc:     Andreas Färber <afaerber@...e.de>,
        linux-lpwan@...ts.infradead.org,
        Ben Whitten <Ben.Whitten@...rdtech.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH lora-next] net: lora: sx1301: Fix radio SPI write

On Mon, Dec 31, 2018 at 12:14:34AM +0000, Ben Whitten wrote:

> If the regmap_bus provider does need to apply the mask, can we get the
> end device regmap_config and apply it from there?
> Mark what are your thoughts on the route to take?

If you're getting a byte stream in then it'll have the mask applied.  If
you're providing per-register read/write ops no formatting at all will
be done, obviously in that case there's no need to bounce the
information through the config.

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