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] [day] [month] [year] [list]
Date:   Fri, 14 Jul 2017 16:14:39 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Sean Wang <sean.wang@...iatek.com>
Cc:     mark.rutland@....com, jamesjj.liao@...iatek.com,
        devicetree@...r.kernel.org, chenglin.xu@...iatek.com,
        lgirdwood@...il.com, henryc.chen@...iatek.com,
        linux-kernel@...r.kernel.org, robh+dt@...nel.org,
        linux-mediatek@...ts.infradead.org, matthias.bgg@...il.com,
        chen.zhong@...iatek.com
Subject: Re: [PATCH 3/9] regulator: mt6380: Add support for MT6380

On Fri, Jul 14, 2017 at 11:06:08PM +0800, Sean Wang wrote:

> We usually want to use /sys/class/regulator/regulator.*/status to get
> actual status from hardware, but if we remove the get_status(), the
> status entry under sysfs would be gone. So could I keep the get_status
> callback in this driver ?

If the device doesn't support physical status readback it shouldn't have
a get_status() callback.  

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ