From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [REGRESSION] commit 0461a41 "spi: Pump transfers inside calling context for spi_sync()" breaks Apalis/Colibri T30 with MCP2515 SPI CAN controller
Date: Fri, 10 Apr 2015 14:23:30 +0100 [thread overview]
Message-ID: <20150410132330.GH6023@sirena.org.uk> (raw)
In-Reply-To: <1428670853.7008.87.camel@localhost.localdomain>
On Fri, Apr 10, 2015 at 03:00:53PM +0200, Marcel Ziswiler wrote:
> Hi there
Please try to use somewhat more targetted CC lists...
> I also have not yet looked further into what exactly is happening and
> whether or not the SPI stack, the Tegra SPI controller driver or the
> MCP2515 SPI CAN driver is to blame but rather decided to ask Mr. Brown
> and the community first for any insights they might have to share.
> Anybody?
I'd ask for trace logs but obviously we can't turn them on until boot
has finished... Adding some trace in the relevant bits of code to try
to see where it's deadlocking is the obvious first step.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150410/fbcffabf/attachment.sig>
next prev parent reply other threads:[~2015-04-10 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 13:00 [REGRESSION] commit 0461a41 "spi: Pump transfers inside calling context for spi_sync()" breaks Apalis/Colibri T30 with MCP2515 SPI CAN controller Marcel Ziswiler
2015-04-10 13:23 ` Mark Brown [this message]
2015-04-10 15:15 ` Marc Kleine-Budde
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=20150410132330.GH6023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).