devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Ludovic Desroches <ludovic.desroches@atmel.com>,
	nicolas.ferre@atmel.com, alexandre.belloni@free-electrons.com,
	plagnioj@jcrosoft.com, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, cyrille.pichen@atmel.com,
	Wenyou Yang <wenyou.yang@atmel.com>
Subject: Re: [PATCH 1/3] i2c: at91: add setting HOLD field of TWIHS_CWGR via DT
Date: Mon, 30 Nov 2015 16:57:23 +0100	[thread overview]
Message-ID: <20151130155723.GA29282@odux.rfo.atmel.com> (raw)
In-Reply-To: <20151130151319.GM1513@katana>

On Mon, Nov 30, 2015 at 04:13:20PM +0100, Wolfram Sang wrote:
> On Tue, Nov 24, 2015 at 02:47:40PM +0100, Ludovic Desroches wrote:
> > From: Wenyou Yang <wenyou.yang@atmel.com>
> > 
> > Add the HOLD field management. Some i2c devices need a longer data hold
> > time than the one given in the i2c bus specification. Since this value
> > depends on the i2c device connected to the bus, add a DT property to
> > configure it: "atmel,twd-hold-cycles".
> 
> We already have "i2c-sda-hold-time-ns". Can you use that one? Sorry that
> this is not obviously documented, I am working on it...
> 

I think we can use it, I'll rework the patch to convert duration in
number of cycles.

      reply	other threads:[~2015-11-30 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 13:47 [PATCH 1/3] i2c: at91: add setting HOLD field of TWIHS_CWGR via DT Ludovic Desroches
2015-11-24 13:47 ` [PATCH 2/3] i2c: at91: add DT property "atmel,twd-hold-cycles" to binding Ludovic Desroches
2015-11-25 22:46   ` Rob Herring
2015-11-24 13:47 ` [PATCH 3/3] ARM: dts: at91: specify DT property "atmel,twd-hold-cycles" Ludovic Desroches
2015-11-30 15:13 ` [PATCH 1/3] i2c: at91: add setting HOLD field of TWIHS_CWGR via DT Wolfram Sang
2015-11-30 15:57   ` Ludovic Desroches [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=20151130155723.GA29282@odux.rfo.atmel.com \
    --to=ludovic.desroches@atmel.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=cyrille.pichen@atmel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=plagnioj@jcrosoft.com \
    --cc=wenyou.yang@atmel.com \
    --cc=wsa@the-dreams.de \
    /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).