From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] spi: trigger trace event for message-done before mesg->complete
Date: Wed, 18 Mar 2015 15:48:54 +0100 [thread overview]
Message-ID: <20150318144854.GS10068@pengutronix.de> (raw)
In-Reply-To: <20150318135854.GI2869@sirena.org.uk>
On Wed, Mar 18, 2015 at 01:58:54PM +0000, Mark Brown wrote:
> On Wed, Mar 18, 2015 at 02:32:26PM +0100, Uwe Kleine-K?nig wrote:
> > On Wed, Mar 18, 2015 at 11:36:35AM +0000, Mark Brown wrote:
>
> > > Applied, thanks. I'm a bit suspicious that the changelog talks only
> > > about spidev though...
>
> > That's my workflow. Maybe the important thing here is also that I use
> > -rt?!
>
> My point here is that the analysis of the issue shouldn't depend on
> spidev in particular, if you need to call out the specific driver you're
> working with that's an alarm sign that it's doing something weird and
> perhaps the problem is with the driver.
This just happens to be the driver I saw the problem with. Don't have
another spi device on that bus to cross check with other drivers. I
wouldn't be too concerned here.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-03-18 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 10:27 [PATCH] spi: trigger trace event for message-done before mesg->complete Uwe Kleine-König
2015-03-18 11:36 ` Mark Brown
2015-03-18 13:32 ` Uwe Kleine-König
2015-03-18 13:58 ` Mark Brown
2015-03-18 14:48 ` Uwe Kleine-König [this message]
2015-03-19 11:24 ` Mark Brown
2015-03-19 11:48 ` Uwe Kleine-König
2015-03-19 11:51 ` Mark Brown
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=20150318144854.GS10068@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).