linux-kernel - Re: [PATCH] IIO ADC support for AD7923

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Jan 2013 18:36:21 +0100
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Alessandro Rubini <rubini@...dd.com>
CC:	christophe.leroy@....fr, jic23@....ac.uk,
	linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
	patrick.vasseur@....fr
Subject: Re: [PATCH] IIO ADC support for AD7923

On 01/17/2013 06:11 PM, Alessandro Rubini wrote:
>>> I wonder if IIO config symbols should have IIO_ in their name, so
>>> people looking at config files knows what they actually are.
>>> Actually, all USB drivers have USB in their config name, which is
>>> useful even if e.g. "PL2303" cannot be but USB.
>>>
>>> On the other hand, AD7923 and all the others can well be driven by
>>> something else than IIO, even if currently this is the only mainstream
>>> option.
>>
>> No, IIO is and should be the only option for these devices. We really don't
>> want to drivers for the same device in different subsystems of the kernel.
> 
> We really don't want a non-USB driver for a USB device, but still the
> name is in the config symbol and is useful. And this is an hardware
> constraint.
> 
> And your argument may well have applied to comedi. But they wisely
> made the right choice and allowed iio to take over and possibly drive
> the same devices.
> 
> But sure your code is perfect and no other subsystem will ever be needed.
> 

I'm not implying IIO is perfect. IIO has certain shortcomings and some of
these shortcomings have been addressed in ZIO.

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.

Btw. I'd be arguing the same way if ZIO was currently inside the kernel and
Jonathan came along and proposed to merge IIO.

> 
> [...]
>
> 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.
> 
> I hope to meet you in person at fosdem and be able to talk over a beer
> or two.
> 

Looking forward to meeting you :)

- Lars

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/