* I2C bus timeout property @ 2012-04-20 9:41 Roland Stigge [not found] ` <4F912F3B.2090105-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org> 0 siblings, 1 reply; 2+ messages in thread From: Roland Stigge @ 2012-04-20 9:41 UTC (permalink / raw) To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ Hi, as you may already have noticed, in the ARM devicetree conversion, we are wondering how to handle the I2C bus timeout property. There is already an "fsl,timeout" property, but introducing several driver or vendor specific properties for basically the same kind of property doesn't make much sense. We already searched devicetree.org and EPAPR but without finding timeout properties. I propose using a generic "timeout" property with newly supported i2c busses, holding a bus timeout value in microseconds (as already done with "fsl,timeout". What do you think? Thanks in advance, Roland ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: <4F912F3B.2090105-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>]
* Re: I2C bus timeout property [not found] ` <4F912F3B.2090105-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org> @ 2012-04-20 12:15 ` Wolfram Sang 0 siblings, 0 replies; 2+ messages in thread From: Wolfram Sang @ 2012-04-20 12:15 UTC (permalink / raw) To: Roland Stigge; +Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ [-- Attachment #1.1: Type: text/plain, Size: 1169 bytes --] On Fri, Apr 20, 2012 at 11:41:15AM +0200, Roland Stigge wrote: > Hi, > > as you may already have noticed, in the ARM devicetree conversion, we > are wondering how to handle the I2C bus timeout property. > > There is already an "fsl,timeout" property, but introducing several > driver or vendor specific properties for basically the same kind of > property doesn't make much sense. We already searched devicetree.org and > EPAPR but without finding timeout properties. > > I propose using a generic "timeout" property with newly supported i2c > busses, holding a bus timeout value in microseconds (as already done > with "fsl,timeout". There is also "i2c-gpio,timeout-ms" already. > What do you think? Basically same question goes for "slave-addr". Since I2C is multi-master, an I2C controller may also be slave (not that we support that in the I2C core yet, but drivers could have that implemented on their own). We have "samsung,i2c-slave-addr" already. Regards, Wolfram -- Pengutronix e.K. | Wolfram Sang | Industrial Linux Solutions | http://www.pengutronix.de/ | [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 198 bytes --] [-- Attachment #2: Type: text/plain, Size: 192 bytes --] _______________________________________________ devicetree-discuss mailing list devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org https://lists.ozlabs.org/listinfo/devicetree-discuss ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-04-20 12:15 UTC | newest] Thread overview: 2+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-04-20 9:41 I2C bus timeout property Roland Stigge [not found] ` <4F912F3B.2090105-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org> 2012-04-20 12:15 ` Wolfram Sang
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).