linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Getz, Robin" <robin.getz@analog.com>
To: Lars-Peter Clausen <lars@metafoo.de>,
	Alessandro Rubini <rubini@gnudd.com>,
	"greg@kroah.com" <greg@kroah.com>
Cc: "christophe.leroy@c-s.fr" <christophe.leroy@c-s.fr>,
	"jic23@cam.ac.uk" <jic23@cam.ac.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"patrick.vasseur@c-s.fr" <patrick.vasseur@c-s.fr>
Subject: Re: [PATCH] IIO ADC support for AD7923
Date: Fri, 18 Jan 2013 18:02:12 -0500	[thread overview]
Message-ID: <201301181802.14382.robin.getz@analog.com> (raw)
In-Reply-To: <50F83695.506@metafoo.de>

On Thu 17 Jan 2013 12:36, Lars-Peter Clausen pondered:
> On 01/17/2013 06:11 PM, Alessandro Rubini wrote:
> > [...]
> >
> > But yes, you are right. I'm working on another I/O subsystem. We are
> > gong to release zio-1.0 in a few days, because the thing is mature
> > and used in production.

Neither means it's a good idea for upstream :)

> Still it's a very bad idea to have two subsystem which have a huge overlap
> in both functionality and targeted devices. It will gives us all lots of
> headaches later on. As IIO continues to evolve it will get support for some
> of the features that only ZIO supports at the moment and as ZIO grows it
> will get support for features currently only supported by IIO. So in the
> end we have two frameworks for the very same purpose.

I want to strongly agree with Lars-Peter. Lets work together on one thing - 
which tries to solve all the our system level issues. As an end user - I 
don't want to re-write userspace for multiple interfaces to the same 
underlying ADC/DACs.

I don't know how Greg feels about another subsystem in the kernel which 
duplicates existing functionality/targetted devices - but it doesn't sound 
like a good idea to me.

> > I hope to meet you in person at fosdem and be able to talk over a beer
> > or two.
>
> Looking forward to meeting you :)

Hopefully you can come to some logical conclusions over a friendly beverage. 
Even if you can't decide on how to merge things (plan for adding missing 
features from one to the other), maybe it's just deciding on how to get as 
much reuse as possible (duplication of device register and bit definitions?)

-Robin


  reply	other threads:[~2013-01-18 23:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  8:42 [PATCH] IIO ADC support for AD7923 Christophe Leroy
2013-01-08  9:14 ` Alessandro Rubini
2013-01-12 10:39   ` Jonathan Cameron
2013-01-12 17:14   ` Lars-Peter Clausen
2013-01-17 16:32   ` Alessandro Rubini
2013-01-17 17:11   ` Alessandro Rubini
2013-01-17 17:36     ` Lars-Peter Clausen
2013-01-18 23:02       ` Getz, Robin [this message]
2013-01-19 12:51         ` Jonathan Cameron
2013-01-17 18:26     ` Alessandro Rubini
2013-01-08 10:27 ` Lars-Peter Clausen
2013-01-19 15:05   ` christophe leroy
2013-01-19 19:59     ` Lars-Peter Clausen

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=201301181802.14382.robin.getz@analog.com \
    --to=robin.getz@analog.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=greg@kroah.com \
    --cc=jic23@cam.ac.uk \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick.vasseur@c-s.fr \
    --cc=rubini@gnudd.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;
as well as URLs for NNTP newsgroup(s).