From: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
To: Stephane Grosjean <s.grosjean@peak-system.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH v4.1] can/sja1000: add support for PEAK-System PCMCIA card
Date: Fri, 17 Feb 2012 15:40:37 +0100 [thread overview]
Message-ID: <4F3E66E5.8070201@volkswagen.de> (raw)
In-Reply-To: <4F3E61D7.1040208@peak-system.com>
On 17.02.2012 15:19, Stephane Grosjean wrote:
> Le 17/02/2012 14:40, Oliver Hartkopp a écrit :
>>
>> The only remaining issue with PEAK PCIeC is the locking warning about the
>> PCIeC LED timer lock (&card->led_timer) when i enable and start the interface
>> under CAN load. I do have a peak_pci v5 driver here - but in v6 only changed
>> the device_id table right?
>
> Yes, mainly.
>>
>> To get this problem you need to connect the PCIeC to a CAN bus which is
>> already having CAN traffic between at least two functional nodes.
>>
>
> Does this issue always occurs, each time you configure the interface?..
No. It's exactly the first time i configure the interface from a xterm in
gnome (after making me su to do so). But only under load.
> Especially with the "new" sja1000.ko?
That's no difference.
I assume there's some LED locking race at startup (e.g. try to blink fast
after detecting the traffic).
Regards,
Oliver
next prev parent reply other threads:[~2012-02-17 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 10:10 [PATCH v4.1] can/sja1000: add support for PEAK-System PCMCIA card Stephane Grosjean
2012-02-17 8:24 ` Dominik Brodowski
2012-02-17 9:21 ` Stephane Grosjean
2012-02-17 9:36 ` Marc Kleine-Budde
2012-02-17 13:40 ` Oliver Hartkopp
2012-02-17 14:19 ` Stephane Grosjean
2012-02-17 14:40 ` Oliver Hartkopp [this message]
2012-02-17 14:47 ` Stephane Grosjean
-- strict thread matches above, loose matches on Subject: below --
2012-02-13 14:18 Stephane Grosjean
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=4F3E66E5.8070201@volkswagen.de \
--to=oliver.hartkopp@volkswagen.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=s.grosjean@peak-system.com \
--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 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).