From: Ssagarr Patil <hugarsagar@outlook.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: RE: C_CAN: can frame drops
Date: Fri, 25 Jul 2014 13:50:40 +0530 [thread overview]
Message-ID: <BAY176-W3963100D46A519A34EBE75D3FC0@phx.gbl> (raw)
In-Reply-To: <53D14BE7.6030007@hartkopp.net>
Hi Oliver,
>
> unfortunately I'm not really a C_CAN expert.
>
> I know from a Beaglebone Black which run's at 99% busload without any issues
> on the two integrated D_CAN controllers.
>
Ok.
> Do you have these problems with a stock 2.6.37.x on your hardware too?
>
Yes
> Can you send the dmesg output of the c_can related content?
>
Unfortunately in c_can driver there are no lot of debug prints but
I am only concerned about function c_can_handle_lost_msg_obj()
being called frequently in which can frame is overwritten.
Rest of the driver works fine.
Regards,
--Sagar
next prev parent reply other threads:[~2014-07-25 8:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 14:48 C_CAN: can frame drops Ssagarr Patil
2014-07-23 16:04 ` Oliver Hartkopp
2014-07-23 16:33 ` Ssagarr Patil
2014-07-24 7:40 ` Ssagarr Patil
2014-07-24 18:09 ` Oliver Hartkopp
2014-07-25 8:20 ` Ssagarr Patil [this message]
2014-07-25 7:17 ` Marc Kleine-Budde
2014-07-25 8:13 ` Ssagarr Patil
2014-07-25 8:16 ` Marc Kleine-Budde
2014-07-25 8:22 ` Ssagarr Patil
2014-07-25 8:27 ` Marc Kleine-Budde
2014-07-25 8:35 ` Ssagarr Patil
2014-07-25 8:48 ` Marc Kleine-Budde
2014-07-25 9:47 ` Ssagarr Patil
2014-07-25 10:10 ` Marc Kleine-Budde
2014-07-25 11:22 ` Ssagarr Patil
2014-07-25 10:43 ` Oliver Hartkopp
2014-07-25 11:24 ` Ssagarr Patil
2014-07-30 11:28 ` Prabhakar Lad
2014-07-30 16:17 ` Oliver Hartkopp
2014-07-31 12:41 ` Ssagarr Patil
2014-07-31 12:42 ` Marc Kleine-Budde
2014-07-31 14:11 ` Oliver Hartkopp
2014-07-31 14:19 ` Prabhakar Lad
2014-12-18 9:41 ` [RFC] sched policies for candump Oliver Hartkopp
2014-12-18 12:33 ` Prabhakar Lad
2014-12-18 13:51 ` Oliver Hartkopp
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=BAY176-W3963100D46A519A34EBE75D3FC0@phx.gbl \
--to=hugarsagar@outlook.com \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.