linux-kernel - Re: regmap I3C support

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: <ZzXfmonkRB-KaBhi@finisterre.sirena.org.uk>
Date: Thu, 14 Nov 2024 11:31:38 +0000
From: Mark Brown <broonie@...nel.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Frank Li <Frank.Li@....com>
Subject: Re: regmap I3C support

On Wed, Nov 13, 2024 at 12:16:37PM -0800, Guenter Roeck wrote:
> On 11/13/24 06:41, Mark Brown wrote:

> > That's kind of my question.  If we are going to have this sort of stuff
> > we should also have it for I2C and SPI since it's such a common pattern.

> I'll take that as "we are not going to provide a dummy regmap i3c registration
> function". Thanks, that is all I needed to know.

It's not a definite no, it's a "is this just going to run into the same
problems we ran into with I2C and SPI and never get used?" or
alternatively "have people figured out a better solution to the problems
we had with I2C and SPI which we can adopt there?" - it's something we
wanted to do before but ran into trouble with.

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