linux-kernel - Re: [PATCH v9 2/5] rust: io: factor common I/O helpers into Io trait

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: <DFQ3EBMAI2N2.O6CY0ZGSL2JH@kernel.org>
Date: Fri, 16 Jan 2026 15:44:31 +0100
From: "Danilo Krummrich" <dakr@...nel.org>
To: "Markus Probst" <markus.probst@...teo.de>, <aliceryhl@...gle.com>
Cc: "Zhi Wang" <zhiw@...dia.com>, <rust-for-linux@...r.kernel.org>,
 <linux-pci@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
 <bhelgaas@...gle.com>, <kwilczynski@...nel.org>, <ojeda@...nel.org>,
 <alex.gaynor@...il.com>, <boqun.feng@...il.com>, <gary@...yguo.net>,
 <bjorn3_gh@...tonmail.com>, <lossin@...nel.org>, <a.hindborg@...nel.org>,
 <tmgross@...ch.edu>, <helgaas@...nel.org>, <cjia@...dia.com>,
 <smitra@...dia.com>, <ankita@...dia.com>, <aniketa@...dia.com>,
 <kwankhede@...dia.com>, <targupta@...dia.com>, <acourbot@...dia.com>,
 <joelagnelf@...dia.com>, <jhubbard@...dia.com>, <zhiwang@...nel.org>,
 <daniel.almeida@...labora.com>
Subject: Re: [PATCH v9 2/5] rust: io: factor common I/O helpers into Io
 trait

On Fri Jan 16, 2026 at 2:57 PM CET, Markus Probst wrote:
> On Thu, 2026-01-15 at 23:26 +0200, Zhi Wang wrote:
> How would this work with I2C as a IO backend?
>
> I2C by itself doesn't have 32-bit IO, which the trait requires.
>
> There is
> "byte data" - 8 bit
> "word data" - 16 bit
> "block data" - arbitrary number of bytes (in SMBus limited to 32 bytes.
> Outside of SMBus it could be higher)

You can use a block data transfer to implement 32bit.

> Note that I only require "byte data" for my led driver.

That's fine, not ever driver has to make use of all capabilities.

However, eventually we want to be able to use regmap to implement I/O backends.
For this it could actually become necessary to have separate traits for 8, 16
and 32 bit. But I think this is out of scope for this series, let's leave that
to a subsequent series. We can always split them up when necessary.