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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <814737a6-384b-23ec-1f5c-ddeb08f3758e@linux.ibm.com>
Date:   Thu, 3 Nov 2022 09:59:39 -0500
From:   Eddie James <eajames@...ux.ibm.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     linux-fsi@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
        gregkh@...uxfoundation.org, rafael@...nel.org, jk@...abs.org,
        joel@....id.au, alistair@...ple.id.au
Subject: Re: [PATCH v2 1/5] regmap: Add FSI bus support


On 11/3/22 09:54, Mark Brown wrote:
> On Wed, Nov 02, 2022 at 03:51:44PM -0500, Eddie James wrote:
>> Add regmap support for the FSI bus.
>>
>> Signed-off-by: Eddie James <eajames@...ux.ibm.com>
>> ---
>>   drivers/base/regmap/Kconfig      |   6 +-
>>   drivers/base/regmap/Makefile     |   1 +
>>   drivers/base/regmap/regmap-fsi.c | 231 +++++++++++++++++++++++++++++++
>>   include/linux/regmap.h           |  37 +++++
> I thought the plan was to put this in the MFD since that's the only
> user?


For the I2C responder regmap, yes, that's what I've done. The FSI regmap 
could be used anywhere in the future. We could switch a number of 
drivers to use the FSI regmap if desired, so I feel it's worth it to put 
it in the regmap properly.


Thanks,

Eddie


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ