devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Roland Stigge <stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: I2C bus timeout property
Date: Fri, 20 Apr 2012 14:15:20 +0200	[thread overview]
Message-ID: <20120420121520.GB15613@pengutronix.de> (raw)
In-Reply-To: <4F912F3B.2090105-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>


[-- 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

      parent reply	other threads:[~2012-04-20 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120420121520.GB15613@pengutronix.de \
    --to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).