linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shubhrajyoti Datta <shubhrajyoti.datta@gmail.com>
To: iztok.jeras@redpitaya.com
Cc: Moritz Fischer <moritz.fischer@ettus.com>,
	p.zabel@pengutronix.de, linux-kernel@vger.kernel.org
Subject: Re: Re: Reset implementation for Zynq
Date: Tue, 8 Nov 2016 17:26:29 +0530	[thread overview]
Message-ID: <CAKfKVtFKp8ZnLmDh-Qq5LvHTaqVafZ3P3M+E6HfvSM+Z0qYcQA@mail.gmail.com> (raw)
In-Reply-To: <20161108024052.6b4c15d01df5508dab02973c2a5944d9.803a60fc5b.mailapi@email21.godaddy.com>

Hi Iztok,



On Tue, Nov 8, 2016 at 3:10 PM,  <iztok.jeras@redpitaya.com> wrote:
> Hi Shubhrajyoti,
>
> By lockup state, I mean an undefined/unhandled state of the HW logic state
> machine,
> or something similar in the software driver.
> Based on symptoms I assume it is a HW lockup.
> In practice asking the driver for a new I2C transfer would result in
> nothing happening on the I2C bus (signals remain in hi-Z state).
> Driver or userspace tool reports a transfer error, but I did not copy it.
> And I did not check the state of the driver.
>
> To enter this mode it was enough to connect an oscilloscope probe to the SDA
> signal.
> The capacitance of the probe causes a deep voltage fall, which is quickly
> corrected by the pullup.
> I did not time the glitch, and the shape was partially defined by an I2C
> level shifter.
> The issue can be repeated with about 80% probability.
>
> There are two ways to get back to a working state:
> 1. create a longer zero pulse (about 50ms manual grounding) on SDA
> 2. reset the HW, this was done with a patched driver.
Thanks  for the explaination.
May be recovery mechanism  implementation could be considered.


>
> Regards,
> Iztok Jeras
>
>

      parent reply	other threads:[~2016-11-08 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161021030847.6b4c15d01df5508dab02973c2a5944d9.645b3cfd21.mailapi@email21.godaddy.com>
2016-10-21 17:04 ` Reset implementation for Zynq Moritz Fischer
2016-10-24  9:00   ` Philipp Zabel
2016-10-24 17:03     ` Moritz Fischer
2016-11-08  6:34   ` Shubhrajyoti Datta
     [not found]     ` <20161108024052.6b4c15d01df5508dab02973c2a5944d9.803a60fc5b.mailapi@email21.godaddy.com>
2016-11-08 11:56       ` Shubhrajyoti Datta [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=CAKfKVtFKp8ZnLmDh-Qq5LvHTaqVafZ3P3M+E6HfvSM+Z0qYcQA@mail.gmail.com \
    --to=shubhrajyoti.datta@gmail.com \
    --cc=iztok.jeras@redpitaya.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moritz.fischer@ettus.com \
    --cc=p.zabel@pengutronix.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).