Re: [PATCH]i2c: Make test for force on client probe possible

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry for the delay, had to fix a bug in u-boot...

Jean Delvare said the following:
> Hi Michael,
> 
> I don't know how you sent this mail, but that's not OK. If you intend
> to do kernel development, you have to use a real e-mail addresses all
> along the way.
> 
Discussed in PM.

> On Fri, 13 Mar 2009 11:15:57 +0100, Michael Lawnick wrote:
>> in new driver model 'kind' is no more provided for client's probe
>> function. The driver frame work creates the path
>> sys/bus/i2c/devices/[bus]-[dev]/ and populates it with the entries
>> modalias, name, subsystem@ and uevent. If probe fails (because the
>> device is not on bus at the moment) the client's sysFs-entries are not
>> created, but the entries above remain.
> 
> This is correct, and this is by design. This is how the Linux device
> driver model works, BTW, nothing i2c-specific there.
> 
Even if this is by (current linux) design, I think it is not ok ;-)
It leaves an inconsistent (not instable) system. IMHO either the entries
should be completely removed or completely created but not that half the
way.
Should we CC another list?

-- 
Regards,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux