Message-ID: <50A2BAA2.6090009@ahsoftware.de>
Date:	Tue, 13 Nov 2012 22:24:50 +0100
From:	Alexander Holler <holler@...oftware.de>
To:	Jean Delvare <khali@...ux-fr.org>
CC:	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
	Till Harbaum <till@...baum.org>
Subject: Re: [PATCH 1/2] i2c: Add possibility for user-defined (i2c-)devices
 for bus-drivers.

Am 13.11.2012 22:08, schrieb Jean Delvare:


>>> No, no, no. We did that 10 years ago, killed all the code 3 years ago

Btw. I wonder where all you kernel devs have learned that "No, no, no". 
Do you all attend the same rhetoric courses at some conferences? ;)

>>> [1], let's not do the same mistake again, please. We have a sysfs
>>> interface for instantiating clients dynamically from user-space, it's
>>> way more powerful and flexible than your proposal. Just try plugging two
>>
>> So how do I define a device, e.g. an RTC which I want to have alive
>> before userland starts? Currently imho not possible.
>
> If your system relies on a an RTC clock chip hanging off an USB-to-I2C
> adapter, I'd say your design is very wrong to start with. I can only
> suppose (hope!) you are doing that during some development phase and
> the final hardware design is totally different.
 >
> If you need I2C devices to be instantiated early in the boot process,
> this would typically be done by platform code. This is going to be a
> little difficult with i2c-tiny-usb as it was definitely not meant to
> host system-critical chips. But you can probably get it to work if you
> try hard enough (in particular by allowing i2c-tiny-usb to claim
> specific i2c bus number(s).) If you want your development system to
> mimic the final hardware as closely as possible, this is the best
> approach anyway.

I never would develop some hardware meant for usage with Linux which 
doesn't have a RTC. But there are several such boards available. E.g. 
that currently so much hyped Rasberry PI. So there are certainly some 
people which have a usage for such a parameter (including me).

Maybe you could forward your suggestion to those hw-devs which are 
responsible for linux-hw without an RTC. I don't know such poeple. ;)

> It probes in the sense "check if a device is present", not in the sense
> "check if the device there is really what the user told me." So very
> easy to get wrong. Plus there is no universal probe method on I2C,
> i2c_new_probed_device() uses a default heuristic which may not only
> fail to detect a device's presence, but may even heavily confuse the
> device in question. Usage of i2c_new_probed_device() should be limited
> to very specific cases.

I know about that too. But I prefer such a probe instead of doing it 
without an probe. Just try what happens if you add e.g. an pcf8563 (or 
ds1307) which is not available. The driver doesn't care and you will 
find an /dev/rtcN afterwards in your system. So probing is imho better 
than not.

> I am not questioning the quality of your code, I did not even look at
> it. I'm questioning the pertinence of adding yet another way to
> instantiate i2c devices when we already have 4 which made everybody
> else happy for the past 3 years AFAIK.

As said, currently there is no way to do that whithout either patching 
the kernel or working in userspace. And a RTC is just an example for a 
device you really want before userspace starts (but imho a very good).

Regards,

Alexander
--
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/

Powered by blists - more mailing lists