From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Fix Bug for cadence i2c interrupt overrunning buffer
Date: Thu, 7 Dec 2017 11:49:15 +0100 [thread overview]
Message-ID: <20171207104915.fdqkj35ga2yxeg3n@ninjato> (raw)
In-Reply-To: <CAFcVECLWwo+OxSGAGYJfMSesjNT51X+Cwk+E_-RQk7gsEXy2YQ@mail.gmail.com>
> > I attach a patch of the changes to the i2c driver showing my debug in
> > this driver.
> > As I said I am happy to send more verbose bug output - I have about 36
> > odd runs with 9 occurences of the bug.
> > Once it happen twice in the one run
> >
> > I include the crashing line from the runs where the bug occured (I
> > added more diagnostics as the runs progressed):
>
> I'll check with out HW team as well and check your flow to
> see if we can reproduce it; will also check if the existing errata
> has larger scope.
> I'll let you know if we require further assistance with debug
> next week.
Any news here?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171207/bb2a5f6f/attachment.sig>
next prev parent reply other threads:[~2017-12-07 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 3:02 [PATCH] Fix Bug for cadence i2c interrupt overrunning buffer Andrew Worsley
2017-10-05 12:01 ` Wolfram Sang
2017-10-07 5:32 ` Andrew Worsley
2017-10-13 18:46 ` Wolfram Sang
2017-10-16 5:49 ` Michal Simek
2017-10-16 5:55 ` Harini Katakam
2017-10-16 9:18 ` Andrew Worsley
2017-10-16 10:38 ` Harini Katakam
2017-10-18 9:41 ` Andrew Worsley
2017-10-20 5:04 ` Harini Katakam
2017-12-07 10:49 ` Wolfram Sang [this message]
2017-12-07 13:30 ` Harini Katakam
[not found] ` <CA+Y=x3nZsfJ+hE5YjvYLM0tdaRX9hX1G6crAjOmmnks-9Rekqg@mail.gmail.com>
[not found] ` <CA+Y=x3=NXpwmqk9RR4oZVkndo=kFwG5T39ktHAhFb=Q9m61Mjg@mail.gmail.com>
2019-12-17 7:38 ` Shubhrajyoti Datta
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=20171207104915.fdqkj35ga2yxeg3n@ninjato \
--to=wsa@the-dreams.de \
--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