From: John Whitmore <arigead@gmail.com>
To: "Rost, Martin" <Martin.Rost@tonfunk.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH] mcp251x: mcp2515 stops receiving
Date: Thu, 22 May 2014 11:28:44 +0100 [thread overview]
Message-ID: <20140522102442.GB3826@griso.site> (raw)
In-Reply-To: <2E9F00CBB66AB544A1ACDC59627518BA0DC96DCF@mailserver>
On Thu, May 22, 2014 at 06:38:18AM +0000, Rost, Martin wrote:
>
> Hello John,
>
> > -----Original Message-----
> > From: linux-can-owner@vger.kernel.org [mailto:linux-can-
> > owner@vger.kernel.org] On Behalf Of John Whitmore
> > Sent: Thursday, May 22, 2014 1:54 AM
> > To: Marc Kleine-Budde
> > Cc: Rost, Martin; linux-can@vger.kernel.org; Alexander Shiyan
> > Subject: Re: [PATCH] mcp251x: mcp2515 stops receiving
> >
> > I'm not an expert in the Linux Driver code nor the implemented fix but I can
> > confirm that the Interrupt is generated with no flags set. I'm not sure of the
> > 10mS timing but I'd imagine that should work.
> >
>
> Thanks for confirming it.
> I fiddled a bit with the timing, and it seemed that 5ms would catch some but not all occurrences of this problem.
> So I went for 10 to make sure.
>
> I'm not too deep into kernel internals, so is there some best practice to this?
>
I honestly can't answer about best practice on working around apparent flaws in
Hardware ;-) I'll leave somebody else to answer that one.
> Regards,
> Martin
next prev parent reply other threads:[~2014-05-22 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 6:33 [PATCH] mcp251x: mcp2515 stops receiving Rost, Martin
2014-05-12 17:00 ` Marc Kleine-Budde
2014-05-12 17:14 ` Alexander Shiyan
2014-05-12 17:34 ` AW: " Rost, Martin
2014-05-12 17:47 ` Alexander Shiyan
2014-05-21 23:53 ` John Whitmore
2014-05-22 6:38 ` Rost, Martin
2014-05-22 10:28 ` John Whitmore [this message]
2014-05-22 16:08 ` Gerhard Bertelsmann
-- strict thread matches above, loose matches on Subject: below --
2014-05-12 17:27 Rost, Martin
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=20140522102442.GB3826@griso.site \
--to=arigead@gmail.com \
--cc=Martin.Rost@tonfunk.de \
--cc=linux-can@vger.kernel.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