[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55E40715.1040204@st.com>
Date: Mon, 31 Aug 2015 09:49:41 +0200
From: Maxime Coquelin <maxime.coquelin@...com>
To: Paul Bolle <pebolle@...cali.nl>,
Peter Griffin <peter.griffin@...aro.org>
CC: <lee.jones@...aro.org>, <devicetree@...r.kernel.org>,
<dmaengine@...r.kernel.org>, <ludovic.barre@...com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <srinivas.kandagatla@...il.com>,
<patrice.chotard@...com>, <vinod.koul@...el.com>,
<dan.j.williams@...el.com>
Subject: Re: [PATCH 3/7] dmaengine: st_fdma: Add STMicroelectronics FDMA
engine driver support
Hi Paul,
On 07/09/2015 10:17 AM, Paul Bolle wrote:
>> >+static int __exit st_fdma_remove(struct platform_device *pdev)
>> >+{
>> >+ struct st_fdma_dev *fdev = platform_get_drvdata(pdev);
>> >+
>> >+ wait_for_completion(&fdev->fw_ack);
>> >+
>> >+ st_fdma_clk_disable(fdev);
>> >+
>> >+ return 0;
>> >+}
> Since this driver is built-in only this means st_fdma_remove() can never
> be used, right?
>
It's not because a driver is built-in only that it does not need a
remove callback.
An instance can be probed/removed any time via driver's bind/unbind
SysFS entries.
Am I missing something?
Kind regards,
Maxime
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists