From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [RFC 0/2] i2c: sh_mobile: don't regress on deferred probing
Date: Wed, 10 Dec 2014 15:19:12 +0100 [thread overview]
Message-ID: <20141210141912.GA8247@katana> (raw)
In-Reply-To: <CAMuHMdUwsUakz7S_7xCob4__wR-PXcdpZKTGx0i_6ZatDeSvXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
> On Wed, Dec 10, 2014 at 2:21 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> > Okay, here is my take on solving the problem found by Geert. I still don't like
> > it much but it is not as bad as I expected it to be ;) Let me know what you
> > think.
>
> Thanks, it's indeed less ugly than I would have expected ;-)
:D
> Note that in spi-rspi.c and spi-sh-msiof, any error returned by *_request_dma()
> is considered an error, and -EPROBE_DEFER is not handled specially.
> So it won't retry if the DMA engine driver isn't available, but just use PIO
> (until unbind/bind).
For historic reasons, i2c-sh_mobile uses subsys_initcall() and at that
time, DMA is never available. Converting to module_init() will just
create its own set of potential regressions :(
> Now we have a nice sample implementation, perhaps I should port it to
> spi-rspi and spi-sh-msiof, too?
>
> Let's wait and see for other comments...
Yeah, let's see first...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-12-10 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 13:21 [RFC 0/2] i2c: sh_mobile: don't regress on deferred probing Wolfram Sang
2014-12-10 13:21 ` [RFC 2/2] i2c: sh_mobile: rework " Wolfram Sang
2014-12-10 13:44 ` Geert Uytterhoeven
2014-12-16 11:35 ` Wolfram Sang
[not found] ` <1418217709-26392-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2014-12-10 13:21 ` [RFC 1/2] i2c: sh_mobile: refactor DMA setup Wolfram Sang
2014-12-10 19:06 ` Sergei Shtylyov
2014-12-16 11:34 ` Wolfram Sang
2014-12-16 21:06 ` Sergei Shtylyov
2014-12-10 13:49 ` [RFC 0/2] i2c: sh_mobile: don't regress on deferred probing Geert Uytterhoeven
2014-12-10 14:19 ` Wolfram Sang [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=20141210141912.GA8247@katana \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).