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: <20150520110413.GE21577@sirena.org.uk>
Date:	Wed, 20 May 2015 12:04:13 +0100
From:	Mark Brown <broonie@...nel.org>
To:	"Zha, Qipeng" <qipeng.zha@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Yang, Fei" <fei.yang@...el.com>,
	"Zhong, Huiquan" <huiquan.zhong@...el.com>,
	"Chen, Jason CJ" <jason.cj.chen@...el.com>,
	"Zheng, Qi" <qi.zheng@...el.com>
Subject: Re: [PATCH] regmap: add virtual PMIC IPC bus support

On Wed, May 20, 2015 at 01:02:49AM +0000, Zha, Qipeng wrote:

Please don't top post.

> Not sure what's your mean using regmap api without bus suport for this case
> Confirm many device driver will use this api.

Please take a look at the code, particularly the reg_read() and
reg_write() interface which I've mentioned in each of my previous
replies and their users.  If you have queries about these please ask.

> The detail is
> Beside pmic core driver itself, there are many pmic function device dirvers, 
> such as gpio, theremal, charger, bcu ..., will use this regmap api to access registers.

This sounds like this is a single device, not a generic bus.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ