linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bengardiner@nanometrics.ca (Ben Gardiner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] i2c-davinci gpio pulsed SCL recovery with ICPFUNC
Date: Tue, 19 Apr 2011 08:20:09 -0400	[thread overview]
Message-ID: <BANLkTinTMi76GmgO6HJ0+ifCXsHE3Mjsvg@mail.gmail.com> (raw)
In-Reply-To: <70E876B0EA86DD4BAF101844BC814DFE093FB40998@Cloud.RL.local>

Hi Jon,

On Mon, Apr 18, 2011 at 9:47 PM, Jon Povey <Jon.Povey@racelogic.co.uk> wrote:
> Ben Gardiner wrote:
>
>>>> When creating this series I noticed that there are obvious
>>>> similarities between the existing recovery routine implemented by
>>>> Philby John and John Povey
>
>> I'm not sure how the 20us in the existing method was derived -- I
>> wonder if Philby John or John Povey could comment?
>
> I've been a little bemused about why I am getting credited for I2C
> bus recovery work. I don't remember doing any work on that.

My mistake -- sorry. Also sorry for getting your name wrong repeatedly.

> I did a couple of patches to fix a race when setting up a TX, but
> those are, afaik, unrelated.

In "i2c-davinci: Fix race when setting up for TX" and "i2c-davinci:
Fix TX setup for more SoCs" you mention testing on DM355 -- is there
any you have hardware on which the recovery procedure is executed on
occasion and that you would be available to test modifications to the
current implementation?

> All I know about the bus recovery stuff is looking at it a while back
> and thinking hmm, that seems to wiggle gpio without changing the
> pinmuxing, so it can't possibly work.

:) Probably not then.

Best Regards,
Ben Gardiner

---
Nanometrics Inc.
http://www.nanometrics.ca

  reply	other threads:[~2011-04-19 12:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 21:38 [PATCH 0/6] i2c-davinci gpio pulsed SCL recovery with ICPFUNC Ben Gardiner
2011-04-05 21:38 ` [PATCH 1/6] i2c-davinci: register dump before attempted bus recovery Ben Gardiner
2011-04-05 21:38 ` [PATCH 2/6] i2c-davinci: convert davinci_i2c_platform_data to kerneldoc Ben Gardiner
2011-04-05 21:38 ` [PATCH 3/6] i2c-davinci: introduce a dev-> function pointer for scl pulsing Ben Gardiner
2011-04-05 21:38 ` [PATCH 4/6] i2c-davinci: use the DA8xx's ICPFUNC to toggle I2C as gpio Ben Gardiner
2011-04-05 21:38 ` [PATCH 5/6] i2c-davinci: if device has pfunc register, dump that group also Ben Gardiner
2011-04-05 21:38 ` [PATCH 6/6] da8xx: enable the use of the ICPFUNC in i2c-davinci Ben Gardiner
2011-04-13 15:10   ` Nori, Sekhar
2011-04-13 15:22     ` Ben Gardiner
2011-04-13 15:42       ` Nori, Sekhar
2011-04-13 16:03         ` Ben Gardiner
2011-04-13 23:04     ` Mike Williamson
2011-04-14  9:26       ` Nori, Sekhar
2011-04-13 16:25 ` [PATCH 0/6] i2c-davinci gpio pulsed SCL recovery with ICPFUNC Nori, Sekhar
2011-04-18 21:36   ` Ben Gardiner
2011-04-19  1:47     ` Jon Povey
2011-04-19 12:20       ` Ben Gardiner [this message]
2011-04-20  1:34         ` Jon Povey

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=BANLkTinTMi76GmgO6HJ0+ifCXsHE3Mjsvg@mail.gmail.com \
    --to=bengardiner@nanometrics.ca \
    --cc=linux-arm-kernel@lists.infradead.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).