public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-kernel@vger.kernel.org,
	uclinux-dist-devel@blackfin.uclinux.org,
	michael.hennerich@analog.com, chrisv@cyberswitching.com
Subject: Re: [PATCH] ad525x_dpot: new driver for AD525x digital potentiometers
Date: Tue, 29 Sep 2009 15:39:02 -0700	[thread overview]
Message-ID: <20090929153902.ab74aa01.akpm@linux-foundation.org> (raw)
In-Reply-To: <1253161357-22453-1-git-send-email-vapier@gentoo.org>

On Thu, 17 Sep 2009 00:22:37 -0400
Mike Frysinger <vapier@gentoo.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.

  reply	other threads:[~2009-09-29 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  4:22 [PATCH] ad525x_dpot: new driver for AD525x digital potentiometers Mike Frysinger
2009-09-29 22:39 ` Andrew Morton [this message]
2009-09-30  1:14   ` [Uclinux-dist-devel] " Mike Frysinger
2009-09-30  1:27     ` Andrew Morton
2009-09-30  1:44       ` Mike Frysinger
2009-10-02  0:53 ` [PATCH v2] " Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090929153902.ab74aa01.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=chrisv@cyberswitching.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox