linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi-topcliff-pch: Fix probing when DMA mode is used
Date: Tue, 04 Mar 2014 07:52:56 +0100	[thread overview]
Message-ID: <3771945.ph3nlbMubQ@ws-stein> (raw)
In-Reply-To: <20140304044422.GJ2411-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>

On Tuesday 04 March 2014 12:44:22, Mark Brown wrote:
> On Mon, Mar 03, 2014 at 08:21:16AM +0100, Alexander Stein wrote:
> > Well, i think this is a rather rarely use case. You need either all
> > drivers compiled in where the SPI device driver is loaded before SPI
> > master or you need SPI master als module while the SPI device driver
> > is already compiled in. Oh, and the SPI device driver must do a SPI
> > transfer during probe. So the conditions are reptty strict when this
> > problem might happen.
> 
> > PS: On EG20T (PCH) it seems this will never happen as the DMA channels
> > are allocated wrongly (see other patch from me) andso DMA will never
> > be used.
> 
> OK, so this doesn't sound terribly urgent then?  It's hard to see and
> other bugs mean it wouldn't be triggered anyway?

Yes, at least for EG20T. I have no idea about those MLxxxx IOH.

Alexander

--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2014-03-04  6:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 15:31 [PATCH] spi-topcliff-pch: Fix probing when DMA mode is used Alexander Stein
     [not found] ` <1393428679-18462-1-git-send-email-alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org>
2014-02-27  4:37   ` Mark Brown
     [not found]     ` <20140227043719.GH9383-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-02-27  8:13       ` Alexander Stein
2014-02-28  3:43         ` Mark Brown
     [not found]           ` <20140228034331.GG9383-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-03-03  7:21             ` Alexander Stein
2014-03-04  4:44               ` Mark Brown
     [not found]                 ` <20140304044422.GJ2411-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-03-04  6:52                   ` Alexander Stein [this message]

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=3771945.ph3nlbMubQ@ws-stein \
    --to=alexander.stein-93q1ybgzjsme9jswtwoym3xstj4p+dsv@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).