mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: NISHIMOTO Hiroki <tlayboy@gmail.com>
Cc: linux-kernel@vger.kernel.org, ben-linux@fluff.org,
	Greg KH <greg@kroah.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] driver/misc: Add new driver for Avago ADJD-S371-QR999
Date: Tue, 16 Feb 2010 12:26:55 -0800	[thread overview]
Message-ID: <20100216122655.9a25e83a.akpm@linux-foundation.org> (raw)
In-Reply-To: <1266156496-15269-1-git-send-email-tlayboy@gmail.com>

On Sun, 14 Feb 2010 23:08:16 +0900
NISHIMOTO Hiroki <tlayboy@gmail.com> wrote:

> Add new driver for Avago ADJD-S371-QR999 digital color sensor.
> 
> This driver has two functions.
> 1. raw_color
>        Gets color values of object.
> 2. trim_color
>        Gets color values of object except the influence of natural light.
> 
> Reset, sleep, external clock functions are not mandatory, so not implemented.
> 

There are quite a number of driver commands here which weren't
documented.  Please fully describe the proposed userspace interface
within the changelog.  Or, better, within a documentation file. 
Because the userspace interface is the most important part.  It's the
only thing we can never change.

It appears that the entire userspace interface for this driver is
implemented via sysfs?  This is odd - we used to have this thing called
"/dev" for communicating with device drivers.  What do people think
about this?

The proposed sysfs interface appears to emit multiple values from a
single sysfs file.  This is considered to be against the sysfs design
rules.

Note that all the above discusses the usersapce interface!  Once we get
that sorted out then we can start looking at the implementation.


  reply	other threads:[~2010-02-16 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 14:08 NISHIMOTO Hiroki
2010-02-16 20:26 ` Andrew Morton [this message]
2010-02-16 20:34 ` Greg KH

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=20100216122655.9a25e83a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ben-linux@fluff.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tlayboy@gmail.com \
    /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

Powered by JetHome