linux-kernel - Re: [PATCH v2] regmap: mmio: add config option to allow relaxed MMIO accesses

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] [day] [month] [year] [list]

Message-Id: <160375601585.32276.1378661556975438111.b4-ty@kernel.org>
Date:   Mon, 26 Oct 2020 23:46:55 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Adrian Ratiu <adrian.ratiu@...labora.com>
Cc:     linux-kernel@...r.kernel.org, kernel@...labora.com,
        "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v2] regmap: mmio: add config option to allow relaxed MMIO accesses

On Wed, 14 Oct 2020 23:30:24 +0300, Adrian Ratiu wrote:
> On some platforms (eg armv7 due to the CONFIG_ARM_DMA_MEM_BUFFERABLE)
> MMIO R/W operations always add memory barriers which can increase load,
> decrease battery life or in general reduce performance unnecessarily
> on devices which access a lot of configuration registers and where
> ordering does not matter (eg. media accelerators like the Verisilicon /
> Hantro video decoders).
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regmap: mmio: add config option to allow relaxed MMIO accesses
      commit: 6e1e90ec027509a7e8d4efbd77a65b32b5a8b3ec

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark