linux-kernel - Re: [PATCH 0/4] Add SDCA register map 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] [day] [month] [year] [list]

Message-ID: <Z7hLc647A8wUIQtO@opensource.cirrus.com>
Date: Fri, 21 Feb 2025 09:46:27 +0000
From: Charles Keepax <ckeepax@...nsource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>
CC: <broonie@...nel.org>, <lgirdwood@...il.com>,
        <peter.ujfalusi@...ux.intel.com>, <yung-chuan.liao@...ux.intel.com>,
        <linux-kernel@...r.kernel.org>, <linux-sound@...r.kernel.org>
Subject: Re: [PATCH 0/4] Add SDCA register map support

On Thu, Feb 20, 2025 at 07:01:44AM -0600, Pierre-Louis Bossart wrote:
> On 2/17/25 08:01, Charles Keepax wrote:
> > This series is the next step of adding SDCA support. Here we add
> > helper functions to allow drivers to easily use the SDCA DisCo
> > information to create a register map for the device.
> 
> Can you remind me where we ended-up in the discussion on one
> regmap per physical device or one regmap per function?
> 
> The DisCo definition are all function-centric, but the physical
> SoundWire bus access for all read/writes is shared by all functions
> so having a single regmap isn't silly either.
> 

We haven't really fully resolved that yet, however, I have
came to the conclusion that all the helper function bits I am
currently adding are completely agnostic of the choice.

So I think it makes most sense to address this once we are adding
an actually driver component. That way we will have the most
context for discussion.

Thanks,
Charles