From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Mirza Krak <mirza.krak@hostmobility.com>
Cc: wg@grandegger.com, andri.yngvason@marel.com,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
netdev@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Christian Magnusson <Christian.Magnusson@semcon.com>
Subject: Re: [PATCH 1/1] can: sja1000: clear interrupts on start
Date: Wed, 11 Nov 2015 13:37:12 +0100 [thread overview]
Message-ID: <56433678.1090104@pengutronix.de> (raw)
In-Reply-To: <CAJ=nTstPCev0TGjZCYkzf4qX+6NUUv8+-6PeVEKL9bcOwBKc0A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]
On 11/11/2015 01:29 PM, Mirza Krak wrote:
>> Can you put a scope on the interrupt pin and see if it's a problem of
>> the SoC and/or Linux or the SJA1000 not pulling the IRQ line.
>
> A little demonstration on what it looks like when the system is
> resumed (added a printk in sja1000_start without my patch, though my
> printk also clears IR register):
>
> root@mx4-vcc:/opt/hm# ip -det link show can0
> 33: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state
> UNKNOWN mode DEFAULT qlen 10
> link/can
> can state ERROR-ACTIVE (berr-counter tx 0 rx 128) restart-ms 0
> bitrate 500000 sample-point 0.875
> tq 250 prop-seg 3 phase-seg1 3 phase-seg2 1 sjw 1
> sja1000: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..64 brp-inc 1
> clock 12000000
> root@mx4-vcc:/opt/hm# ifconfig can0 down
> root@mx4-vcc:/opt/hm# ifconfig can0 up
> [ 1612.621187] sja1000: MOD: 0x1
> [ 1612.640992] sja1000: SR: 0x7c
> [ 1612.660039] sja1000: IR: 0x24
>
> Also did a measurement with the scope, it is the SJA1000 chip not
> pulling the IRQ line.
>
> I can actually send one frame when the controller is in this state but
> never get a TI interrupt.
Thanks for testing.
[...]
>>> Yes, resume code should be implemented to handle this and other
>>> problems (receive data). But still a DOWN/UP procedure should clear
>>> any previous state that could exist in the controller registers.
>>
>> I'll add your patch to can/master and add stable on Cc. Looking forward
>> for some suspend/resume code :)
>
> Looking forward to writing suspend/resume code :).
>
> Some cred should go to Christian (added him to CC) for finding this
> problem and reporting it to me.
I'll add a
Reported-by: Christian Magnusson <Christian.Magnusson@semcon.com>
to the patch.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2015-11-11 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 13:59 [PATCH 1/1] can: sja1000: clear interrupts on start Mirza Krak
2015-11-11 8:04 ` Marc Kleine-Budde
2015-11-11 9:54 ` Mirza Krak
2015-11-11 10:06 ` Marc Kleine-Budde
2015-11-11 12:29 ` Mirza Krak
2015-11-11 12:37 ` Marc Kleine-Budde [this message]
2015-11-11 12:46 ` Mirza Krak
2015-11-11 12:48 ` Marc Kleine-Budde
2015-11-11 12:49 ` Christian Magnusson
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=56433678.1090104@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=Christian.Magnusson@semcon.com \
--cc=andri.yngvason@marel.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirza.krak@hostmobility.com \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.com \
/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).