From: Wolfgang Grandegger <wg@grandegger.com>
To: "j.p.lammertink" <j.p.lammertink@kubicas.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Evaluating the c_can driver for EG20T
Date: Fri, 26 Apr 2013 13:42:44 +0200 [thread overview]
Message-ID: <517A6834.5080400@grandegger.com> (raw)
In-Reply-To: <20130425101119.ADC62B6CB1792@bmail02.one.com>
On 04/25/2013 12:11 PM, j.p.lammertink wrote:
>
> <><> Hi Wolfgang,
> <><>< Hi Jeroen,
> <><><> Hi Wolfgang,
> <><><> I think I have a patch for the "Loosing CAN messages problem"
> <><><> See at the bottom Appendix 7 Sugested patch.
> <><><> I realize that this patch has a performance penalty, but I didn't dare
> <><><> to make more rigorous changes.
> <><><> I've put the patch on top of Patch 1, of the patches that you sugested (see
> <><><> text below)
> <><><> I'm interested in all feedback.
> <><>< Well, we want to get rid of the pch_can driver sooner than later.
> <><>< Therefore I would appreciate if you could test and improve the c_can
> <><>< driver instead.
> <><>< Wolfgang.
> <><> I tried once before but I did not succeed. I probably did something
> <><> wrong. Can you tell me how I can replace the pch_can driver by the
> <><> c_can driver?
> <><> We have reduced confidence in the pch_can driver and therefor we
> <><> are also intrested in evaluating the c_can driver.
> <>< Good, anyway, could you sent me your patches pch_can.c to understand
> <>< better your lates problems.
> <><> Note, after applying patch 1/7 to the pch_can driver, I also
> <><> attemped to
> <><> apply the patches 2/7-7/7 which mainly/only(?) effect the c_can
> <><> driver.
> <><> 1/7 went succesfull, 2/7-7/7 not. Do I still need to apply those
> <><> patches?
> <>< What exact kernel disto and kernel version are you using. With that
> <>< knowledge I could provid new patches.
> <>< Wolfgang.
> <> Hi Wolfgang,
> <> I've included the patch in the E-mail:
> <> "Losing CAN messages with socket-CAN" of 24 apr 2013 11:11. (Appendix 7)
> <> It also contains kernel disto and kernel version and also
> <> the problem description.
> < OK. could you send the file "pch_can.c" you used (sorry for my bad
> < English). Your kernel is obviously 3.5.0-27-generic from Ubuntu. I'm
> < going to rebase the patches on top of mainline Linux 3.5.0. Any chance
> < for you to use a recent mailing Linux version?
> <> You replied to above mentioned E-mail:
> <> "Therefore I would appreciate if you could test and improve the c_can
> <> driver instead."
> <> Can you please indicate how to activate the c_can driver
> <> (instead of the pch_driver)?
> < You need to deselect the PCH_CAN and select the C_CAN PCI driver in your
> < kernel config. I use "make menuconfig" for that purpose. But you need
> < the complete patch stack.
> < Wolfgang.
>
> Hi Wolfgang,
>
> I've attached pch_can.c.
> I also enlarged the scope of the spinlock in the pch_xmit() function.
Ah! Could you please revert your other fix and retry?
> With this version of the pch_can driver I do no longer loose any messages.
> Seems that the problem is solved. I have to admit that I do not
> thoroughly understand this driver (yet) and that I just made educated
> guesses based on testing and debugging.
There is obviously a race which I also have not yet fully understood.
Still the driver has other issues, unfortunately.
Wolfgang.
next prev parent reply other threads:[~2013-04-26 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 7:43 Evaluating the c_can driver for EG20T j.p.lammertink
2013-04-25 7:52 ` Wolfgang Grandegger
2013-04-25 8:55 ` j.p.lammertink
2013-04-25 9:23 ` Wolfgang Grandegger
2013-04-25 10:11 ` j.p.lammertink
2013-04-26 11:42 ` Wolfgang Grandegger [this message]
2013-04-25 13:25 ` Wolfgang Grandegger
-- strict thread matches above, loose matches on Subject: below --
2013-04-26 7:23 j.p.lammertink
2013-04-26 11:45 ` Wolfgang Grandegger
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=517A6834.5080400@grandegger.com \
--to=wg@grandegger.com \
--cc=j.p.lammertink@kubicas.com \
--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 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.