| 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
| ||
|
Message-Id: <305e71436fd8c7875396c79154b2e6512bb18860.1371145891.git.andi@etezian.org> Date: Thu, 13 Jun 2013 20:20:42 +0200 From: Andi Shyti <andi@...zian.org> To: arnd@...db.de, gregkh@...uxfoundation.org Cc: linux-kernel@...r.kernel.org, pc@...f.org, oatilla@...il.com, andi@...zian.org Subject: [PATCH 08/19] bh1770glc: logic change in the proximity read the prox0_raw file in the sysfs interface reads the proximity value directly from the register instead of reporting the last read value; in this way userspace applications can have a real time value Signed-off-by: Andi Shyti <andi@...zian.org> --- drivers/misc/bh1770glc.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/misc/bh1770glc.c b/drivers/misc/bh1770glc.c index ac6d0c8..031a9fa 100644 --- a/drivers/misc/bh1770glc.c +++ b/drivers/misc/bh1770glc.c @@ -786,6 +786,11 @@ static ssize_t bh1770_prox_result_show(struct device *dev, ssize_t ret; mutex_lock(&chip->mutex); + /* + * if this function fails the prox_data will store + * the value from the previous read + */ + bh1770_ps_get_result(chip); if (chip->prox_enable_count && !pm_runtime_suspended(dev)) ret = sprintf(buf, "%d\n", chip->prox_data); else -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists