public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Vinod Koul <vkoul@kernel.org>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	linux-kernel@vger.kernel.org, linux-amarula@amarulasolutions.com,
	Michael Trimarchi <michael@amarulasolutions.com>,
	stable@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>,
	dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH v5 1/2] dmaengine: mxs: use platform_driver_register
Date: Wed, 21 Sep 2022 12:39:30 +0200	[thread overview]
Message-ID: <20220921103930.GM12909@pengutronix.de> (raw)
In-Reply-To: <YyqDq9FL1W5gMveQ@matsya>

On Wed, Sep 21, 2022 at 08:53:23AM +0530, Vinod Koul wrote:
> On 20-09-22, 19:10, Dario Binacchi wrote:
> > Hi Vinoud,
> > 
> > On Tue, Sep 13, 2022 at 6:35 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > >
> > > Hi Dario,
> > >
> > > On Sun, Sep 04, 2022 at 04:10:19PM +0200, Dario Binacchi wrote:
> > > > Driver registration fails on SOC imx8mn as its supplier, the clock
> > > > control module, is probed later than subsys initcall level. This driver
> > > > uses platform_driver_probe which is not compatible with deferred probing
> > > > and won't be probed again later if probe function fails due to clock not
> > > > being available at that time.
> > > >
> > > > This patch replaces the use of platform_driver_probe with
> > > > platform_driver_register which will allow probing the driver later again
> > > > when the clock control module will be available.
> > > >
> > > > Fixes: a580b8c5429a ("dmaengine: mxs-dma: add dma support for i.MX23/28")
> > > > Co-developed-by: Michael Trimarchi <michael@amarulasolutions.com>
> > > > Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
> > > > Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> > > > Cc: stable@vger.kernel.org
> > >
> > > How I see it v3 of this patch is perfectly fine and should be taken
> > > instead of this one. I just commented that to v3.
> > >
> > > Not sure if Vinod would take v3, or if you should resend v3 as v6
> > > instead. If you do, you can add my Acked-by.
> > >
> > > Vinod, please let us know what you prefer.
> > 
> > Could you please let me know how to proceed? This patch has been pending for
> > a while and it's a real shame as the change is minimal and fixes a
> > real issue that is
> > still present in the mainline and stable kernels.
> 
> Ooops, Somehow this seems to have really slipped. Sorry I owe you an
> apology for this
> 
> I am still not sure of this patch yet, lets get it right and merged
> quickly. I will send my review later today

I just realized that unlike what I said v3 of this patch is still wrong
as it leaves the __init annotation on mxs_dma_init() which is called
from (non __init) mxs_dma_probe(). v3 probably doesn't give a section
mismatch warning because mxs_dma_init() is inlined.

Really v2 is the one we should take which is at:

https://lore.kernel.org/linux-arm-kernel/20220523132247.1429321-1-dario.binacchi@amarulasolutions.com/T/

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2022-09-21 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 14:10 [RESEND PATCH v5 1/2] dmaengine: mxs: use platform_driver_register Dario Binacchi
2022-09-04 14:10 ` [RESEND PATCH v5 2/2] dmaengine: mxs: fix section mismatch Dario Binacchi
2022-09-21  9:35   ` Robin Murphy
2022-09-13 16:35 ` [RESEND PATCH v5 1/2] dmaengine: mxs: use platform_driver_register Sascha Hauer
2022-09-20 17:10   ` Dario Binacchi
2022-09-21  3:23     ` Vinod Koul
2022-09-21 10:39       ` Sascha Hauer [this message]
2022-09-21 12:50         ` Vinod Koul
  -- strict thread matches above, loose matches on Subject: below --
2022-08-20  8:44 Dario Binacchi
2022-07-28  6:18 Dario Binacchi

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=20220921103930.GM12909@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@amarulasolutions.com \
    --cc=shawnguo@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vkoul@kernel.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