From: Wolfram Sang <wsa@the-dreams.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH v2] i2c: rcar: make sure clocks are on when doing hw init
Date: Fri, 30 Oct 2015 08:02:10 +0000 [thread overview]
Message-ID: <20151030080210.GA1589@katana> (raw)
In-Reply-To: <1726774.W1OrN54TP1@avalon>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
> First of all, I got one kernel panic.
:( I am starting to think i should revert my last i2c-rcar series until
these issues are gone...
> I have also seen different errors:
>
> [ 1.177690] i2c-rcar e6530000.i2c: error -16 : 0
> [ 1.182534] adv7511: probe of 2-0039 failed with error -16
> [ 1.188293] i2c-rcar e6530000.i2c: probed
>
> -110 occurred as well.
I'd think you always get a -110 somewhere and all later accesses to
the bus will return -16. The bus is stalled.
> This occurred when rebooting the board by pressing the reset button, and if I
I use the reset button quite frequently, too.
> remember correctly moving from renesas-devel-20151013v2-v4.3-rc5 to renesas-
> devel-20151026-v4.3-rc7. Even though it occurred several times in a row I
> can't seem to reproduce this issue now I'm afraid.
Darn...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-30 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 22:46 [PATCH v2] i2c: rcar: make sure clocks are on when doing hw init Wolfram Sang
2015-10-30 0:41 ` Kuninori Morimoto
2015-10-30 4:35 ` Laurent Pinchart
2015-10-30 8:02 ` Wolfram Sang [this message]
2015-10-30 8:16 ` Geert Uytterhoeven
2015-10-30 14:19 ` Laurent Pinchart
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=20151030080210.GA1589@katana \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).