public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg KH <greg@kroah.com>, Jean Delvare <khali@linux-fr.org>,
	Guenter Roeck <guenter.roeck@ericsson.com>
Subject: Re: IIO comments
Date: Thu, 17 Mar 2011 18:54:52 +0100	[thread overview]
Message-ID: <201103171854.52777.arnd@arndb.de> (raw)
In-Reply-To: <4D823AF8.8070408@cam.ac.uk>

On Thursday 17 March 2011 17:46:48 Jonathan Cameron wrote:
> > 
> > Since I haven't fully understood the distinction between the
> > three chardevs, it may of course turn out a bad idea, but I
> > think it would simplify the core code if you could assume
> > that every iio device has exactly one chardev interface,
> > so you could give them the same unique number and manage
> > the life time together.
>
> It simplifies that corner, but I'm a little worried that it
> will add a lot of interlinks between the currently fairly
> disconnected elements that go through a character device.
> 
> If we can keep those links to a minimum (which I think
> we can, but haven't tried yet!) it will be a sensible move.

Let's first work out how a single event buffer should work
using read and poll, as discussed in the other thread.
Once we have sorted that out, this may become a lot clearer.

	Arnd

  parent reply	other threads:[~2011-03-17 17:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 21:15 IIO comments Arnd Bergmann
2011-03-16 11:57 ` Jonathan Cameron
2011-03-16 13:33   ` Arnd Bergmann
2011-03-16 14:50     ` Jonathan Cameron
2011-03-16 15:09       ` Guenter Roeck
2011-03-16 15:15       ` Arnd Bergmann
2011-03-16 15:33         ` Jonathan Cameron
2011-03-17 13:24           ` Arnd Bergmann
2011-03-17 16:47             ` Jonathan Cameron
2011-03-17 17:51               ` Arnd Bergmann
2011-03-17 18:33                 ` Jonathan Cameron
2011-03-18 12:47                   ` Arnd Bergmann
2011-03-18 16:06                     ` Jonathan Cameron
2011-03-18 16:18                       ` Arnd Bergmann
2011-03-18 16:29                         ` Jonathan Cameron
2011-03-18 16:57                           ` Arnd Bergmann
2011-03-18 17:51                             ` Jonathan Cameron
2011-03-17 13:47       ` Arnd Bergmann
2011-03-17 14:42         ` Jonathan Cameron
2011-03-17 15:03           ` Arnd Bergmann
2011-03-17 16:46             ` Jonathan Cameron
2011-03-17 16:47               ` Jonathan Cameron
2011-03-17 17:54               ` Arnd Bergmann [this message]
2011-03-16 16:54   ` Jonathan Cameron
2011-03-16 18:52     ` Arnd Bergmann

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=201103171854.52777.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=greg@kroah.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=jic23@cam.ac.uk \
    --cc=kay.sievers@vrfy.org \
    --cc=khali@linux-fr.org \
    --cc=linux-iio@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox