linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	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: Thu, 11 Dec 2014 22:47:32 +0100	[thread overview]
Message-ID: <20141211214732.GC21482@katana> (raw)
In-Reply-To: <2462101.Er8OZg9N24@avalon>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]


> > Note that the I2C drives uses subsys_initcall() for historic reasons,
> > while the DMA driver uses module_init(). This is hard to revert without
> > introducing potential regressions on older boards. So, the I2C DMA
> > support needs to handle deferred probe definately. I am with Laurent, I
> > don't see any other way, but I'd be glad to be enlightened...
> 
> While I believe that requesting the channel at transfer time is the good 
> solution, I think we should still try to move to module initcalls where 
> possible. The risk of regressions is real so proper testing is needed. My 
> question is, have you tried it ?

I would need to test all boards using this driver to not fail booting.
Usually I2C drivers are moved to subsys_initcall because they need
access to something critical (PMIC, GPIOs...) early. I don't see a sane
way to do that testing.

Other than that, even if we move to module_init, we reduce the chance of
getting a deferred probe, but we do not eliminate it...


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-12-11 21:47 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 [this message]
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
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=20141211214732.GC21482@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 \
    /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).