From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Stigge Subject: I2C bus timeout property Date: Fri, 20 Apr 2012 11:41:15 +0200 Message-ID: <4F912F3B.2090105@antcom.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org List-Id: devicetree@vger.kernel.org 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