From: Wolfram Sang <wsa@the-dreams.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linux I2C <linux-i2c@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH 2/5] i2c: sh_mobile: add DMA support
Date: Mon, 15 Dec 2014 10:45:33 +0100 [thread overview]
Message-ID: <20141215094533.GA3510@katana> (raw)
In-Reply-To: <20141215091314.GQ16827@intel.com>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
> Quite right, this is a good question. Today we cannot distinguish between the
> two. Should we improve the deferred probe to tell us when the init
> is complete and all the modules have been initialized? If we ever have such
> a mechanism to check then we know no modules are to be inserted then we can
> fall back to PIO mode.
Well, the user can load modules from userspace. And I could imagine
there are people wanting to defer things until they load a module
manually. And surely there will be a case where, for some reason, the
deferred code has to be built-in. I trust Murphy's law here...
> Without that we should use some timeout counter to fall back on, say
> try requesting 5 times and give up and move to PIO after that
Won't work. In my case, the I2C driver gets deferred two times and then
the list becomes static already.
On top of that, arbitrary retry values don't make me happy. Mentioning
Murphy's law again...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-15 9:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 10:11 [PATCH 0/5] i2c: sh_mobile: add DMA support Wolfram Sang
2014-11-07 10:11 ` [PATCH 1/5] i2c: sh_mobile: sort includes alphabetically Wolfram Sang
2014-11-12 16:10 ` Wolfram Sang
2014-11-07 10:11 ` [PATCH 2/5] i2c: sh_mobile: add DMA support Wolfram Sang
2014-11-12 16:11 ` Wolfram Sang
2014-12-09 10:53 ` Geert Uytterhoeven
2014-12-09 14:09 ` Wolfram Sang
2014-12-10 5:44 ` Magnus Damm
2014-12-10 8:01 ` Wolfram Sang
2014-12-10 14:19 ` Laurent Pinchart
2014-12-10 14:23 ` Wolfram Sang
2014-12-11 5:02 ` Vinod Koul
2014-12-11 7:37 ` Wolfram Sang
2014-12-11 7:47 ` Laurent Pinchart
2014-12-11 8:28 ` Wolfram Sang
2014-12-11 21:42 ` Laurent Pinchart
2014-12-11 21:47 ` Wolfram Sang
2014-12-11 21:52 ` Laurent Pinchart
2014-12-12 11:07 ` Wolfram Sang
2014-12-15 6:43 ` Vinod Koul
2014-12-15 8:31 ` Geert Uytterhoeven
2014-12-15 9:06 ` Wolfram Sang
2014-12-15 9:32 ` Geert Uytterhoeven
2014-12-15 9:13 ` Vinod Koul
[not found] ` <20141215091314.GQ16827-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-15 9:42 ` Laurent Pinchart
2014-12-15 14:48 ` Vinod Koul
2014-12-15 9:45 ` Wolfram Sang [this message]
2014-12-15 14:50 ` Vinod Koul
2014-11-07 10:11 ` [PATCH 3/5] i2c: sh_mobile: improve success message Wolfram Sang
2014-11-12 16:12 ` Wolfram Sang
2014-11-13 0:27 ` Simon Horman
2014-11-07 10:11 ` [PATCH 4/5] ARM: shmobile: r8a7790: add DMA nodes for IIC Wolfram Sang
2014-11-13 0:26 ` Simon Horman
2014-11-07 10:11 ` [PATCH 5/5] ARM: shmobile: r8a7791: " Wolfram Sang
2014-11-13 0:26 ` Simon Horman
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=20141215094533.GA3510@katana \
--to=wsa@the-dreams.de \
--cc=dmaengine@vger.kernel.org \
--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 \
--cc=vinod.koul@intel.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).