From: Jean Delvare <khali@linux-fr.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
LKML <linux-kernel@vger.kernel.org>,
Vojtech Pavlik <vojtech@ucw.cz>
Subject: Re: Writing a driver for a legacy serial device
Date: Thu, 21 Jun 2007 20:38:43 +0200 [thread overview]
Message-ID: <20070621203843.044fd19a@hyperion.delvare> (raw)
In-Reply-To: <1182437233.2782.36.camel@shinybook.infradead.org>
Hi David,
On Thu, 21 Jun 2007 22:47:12 +0800, David Woodhouse wrote:
> On Thu, 2007-06-21 at 11:33 +0200, Jean Delvare wrote:
> > OK. This leads me to a question: is it OK for me to add support for my
> > non-input device to inputattach, or is a separate, dedicated helper
> > tool preferred? Both ways are fine with me, I don't know what the
> > input subsystem maintainers expect.
>
> You might do better to implement it as a line discipline instead.
> Or just do it in userspace. What exactly are you trying to do?
I am writing a driver for a TAOS evaluation module. This device is a
limited SMBus master, connecting to the serial port. The evaluation
chip is connected to the SMBus. In my case this is a TSL2550 light
sensor, but virtually all compatible TAOS evaluation modules could be
supported.
I2C bus drivers have to be implemented in the kernel, so user-space
isn't an option for me.
I just posted a first (working) version of my driver, if you want to
take a look:
http://lists.lm-sensors.org/pipermail/i2c/2007-June/001508.html
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2007-06-21 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 17:05 Writing a driver for a legacy serial device Jean Delvare
2007-06-19 18:59 ` Dmitry Torokhov
2007-06-20 8:56 ` Jean Delvare
2007-06-21 3:11 ` Dmitry Torokhov
2007-06-21 9:33 ` Jean Delvare
2007-06-21 14:47 ` David Woodhouse
2007-06-21 18:38 ` Jean Delvare [this message]
2007-06-21 23:31 ` Arnd Bergmann
2007-06-22 19:47 ` Dmitry Torokhov
2007-06-23 8:34 ` Jean Delvare
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=20070621203843.044fd19a@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=dtor@insightbb.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@ucw.cz \
/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.