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-next>] [day] [month] [year] [list]
Message-ID: <76471664-425b-c386-3ad8-efeabc2eaf7e@analog.com>
Date:   Tue, 4 Apr 2017 10:28:23 +0200
From:   Michael Hennerich <michael.hennerich@...log.com>
To:     <broonie@...nel.org>, <", linus.walleij"@linaro.org>,
        <wsa@...-dreams.de>
CC:     <linux-gpio@...r.kernel.org>, <linux-i2c@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: question about concurrent regmap i2c usage

Hi Mark,

During the discussion here: https://lkml.org/lkml/2017/4/4/76

A question came up, regarding whether it's recommended to mix regmap_i2c 
and plain i2c_smbus or direct adapter transfers.

In this specific case for the i2c MUX portion we need to avoid double 
locks, and therefore use un-locked direct adapter transfers.

The same time we also implement a small gpiochip, where we would like to 
use regmap to avoid some boilerplate code for the register cache.


What is your thought on this?


-- 
Greetings,
Michael

--
Analog Devices GmbH      Otl-Aicher Strasse 60-64      80807 München
Sitz der Gesellschaft München, Registergericht München HRB 40368,
Geschäftsführer: Peter Kolberg, Ali Raza Husain, Eileen Wynne

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ