linux-kernel - Re: [RFC][PATCH] regmap: Drop CONFIG

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: <f0098753-8219-27c0-d992-a209f3c67d4d@denx.de>
Date:   Wed, 26 Jun 2019 13:20:17 +0200
From:   Marek Vasut <marex@...x.de>
To:     Mark Brown <broonie@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        "Rafael J . Wysocki" <rafael@...nel.org>
Subject: Re: [RFC][PATCH] regmap: Drop CONFIG_64BIT checks from core

On 6/26/19 1:15 PM, Mark Brown wrote:
> On Wed, Jun 26, 2019 at 01:31:16AM +0200, Marek Vasut wrote:
>> Drop the CONFIG_64BIT checks from core regmap code, as it is well
>> possible to access e.g. an SPI device with 64bit registers from a
>> 32bit CPU. The CONFIG_64BIT checks are still left in place in the
>> regmap mmio code however.
> 
> The issue with 8 bit

byte

> registers was that we use unsigned long for
> addresses and values and a 64 bit value won't fit in those on a 32 bit
> system.  Some of the bulk APIs will work but things like individual
> register writes and the caches will have problems.

Good thing I sent this as RFC, I realized that shortly after too.

So, what would be the suggestion here ?

-- 
Best regards,
Marek Vasut