linux-kernel - Re: [PATCH] ad525x_dpot: new driver for AD525x digital potentiometers

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: <20090929153902.ab74aa01.akpm@linux-foundation.org>
Date:	Tue, 29 Sep 2009 15:39:02 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Mike Frysinger <vapier@...too.org>
Cc:	linux-kernel@...r.kernel.org,
	uclinux-dist-devel@...ckfin.uclinux.org,
	michael.hennerich@...log.com, chrisv@...erswitching.com
Subject: Re: [PATCH] ad525x_dpot: new driver for AD525x digital
 potentiometers

On Thu, 17 Sep 2009 00:22:37 -0400
Mike Frysinger <vapier@...too.org> wrote:

> This driver supports the non-volatile digital potentiometers via I2C:
> AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, and AD5255
> 
> It provides a sysfs interface to each device for reading/writing.

This sysfs interface is by far the most important aspect of this
driver.  For both its users and for its reviewers.

Yet you tell us nothing about it!  Not in code comments, not in the
changelog, not in supporting documentation.

So some poor idiot (ie: me) is left having to scratch his way through
the implementation trying to work out what the propoed userspace
interface is supposed to look like.

Then I come across something this:

+	if (reg & AD525X_REG_TOL)
+		return sprintf(buf, "0x%04x\n", value & 0xFFFF);
+	else
+		return sprintf(buf, "%u\n", value & data->rdac_mask);

which makes me suspect that the proposed userspace interface is quite
poor.

Patch not applied!  Not even close.
--
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/