All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Where to put new sensor drivers?
Date: Thu, 5 Mar 2009 16:03:34 +0100	[thread overview]
Message-ID: <20090305150334.GC29699@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090301124134.GE20813@buzzloop.caiaq.de>

On Sun, Mar 01, 2009 at 01:41:34PM +0100, Daniel Mack wrote:
> I wrote a driver for an I2C connected ambient light sensor and submitted
> it to the linux-i2c list[1]. In the first place, I wasn't aware of
> drivers/i2c/chips being deprecated and hencei, I subsequently moved it to
> what seemed to match best in the current tree, drivers/hwmon. But as
> Jean Delvare pointed out, this is not the place for it either because it
> doesn't really monitor the hardware, which is true.
> 
> So I posted a proposal[2] patch series that adds drivers/sensors for
> such cases (some of the drivers in the legacy folder drivers/i2c/chips
> have the same problem than my new one has) but haven't got reply on it
> yet, probably because linux-i2c is the wrong place to ask.

Hmm, no feedback here either? I was pointed to the 'industrial I/O'
thread[1], but that one didn't go mainline yet, and I didn't find any
reference of someone picking up this idea.

Are such drivers not wanted in the kernel? I could also move my code to
userspace, but I though if it's supported by the kernel, more people
can acutally use it easily.

Daniel

[1] http://lkml.org/lkml/2008/12/1/156


  reply	other threads:[~2009-03-05 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01 12:41 Where to put new sensor drivers? Daniel Mack
2009-03-05 15:03 ` Daniel Mack [this message]
2009-03-06 18:55   ` Pavel Machek

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=20090305150334.GC29699@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.