From: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
To: Vinod Koul <vkoul@kernel.org>, Nicolas Frayer <nfrayer@baylibre.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
khilman@baylibre.com, glaroque@baylibre.com
Subject: Re: [PATCH v3] dmaengine: ti: k3-udma: Deferring probe when soc_device_match() returns NULL
Date: Thu, 29 Dec 2022 18:29:27 +0200 [thread overview]
Message-ID: <52a11d11-20a0-bf08-ce64-401b5d0ad133@gmail.com> (raw)
In-Reply-To: <Y6wlhfdDdm+XAsuH@matsya>
On 28/12/2022 13:16, Vinod Koul wrote:
> On 17-11-22, 19:44, Nicolas Frayer wrote:
>> When the k3 socinfo driver is built as a module, there is a possibility
>> that it will probe after the k3 udma driver and the later returns -ENODEV.
>> By deferring the k3 udma probe we allow the k3 socinfo to probe and
>> register the soc_device_attribute structure needed by the k3 udma driver.
>> Removed the dev_err() message as well as it's deferring and not failing.
>
> lgtm, but need rebase as I already picked commit 3f58e10615f3 dmaengine: ti:
> k3-udma: Add support for BCDMA CSI RX
Is this path needed at all? afaik the k3 socinfo is not going to be
module built.
>
>>
>> Signed-off-by: Nicolas Frayer <nfrayer@baylibre.com>
>> ---
>> v1->v2:
>> Extracted this patch from the following series:
>> https://lore.kernel.org/all/20221108181144.433087-1-nfrayer@baylibre.com/
>>
>> v2->v3:
>> Removed the dev_err() message
>>
>> drivers/dma/ti/k3-udma.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/dma/ti/k3-udma.c b/drivers/dma/ti/k3-udma.c
>> index ce8b80bb34d7..ca1512eb9910 100644
>> --- a/drivers/dma/ti/k3-udma.c
>> +++ b/drivers/dma/ti/k3-udma.c
>> @@ -5271,10 +5271,10 @@ static int udma_probe(struct platform_device *pdev)
>> ud->match_data = match->data;
>>
>> soc = soc_device_match(k3_soc_devices);
>> - if (!soc) {
>> - dev_err(dev, "No compatible SoC found\n");
>> - return -ENODEV;
>> - }
>> +
>> + if (!soc)
>> + return -EPROBE_DEFER;
>> +
>> ud->soc_data = soc->data;
>>
>> ret = udma_get_mmrs(pdev, ud);
>> --
>> 2.25.1
>
--
Péter
next prev parent reply other threads:[~2022-12-29 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 18:44 [PATCH v3] dmaengine: ti: k3-udma: Deferring probe when soc_device_match() returns NULL Nicolas Frayer
2022-11-18 20:11 ` Kevin Hilman
2022-12-28 11:16 ` Vinod Koul
2022-12-29 16:29 ` Péter Ujfalusi [this message]
2022-12-29 23:31 ` Nicolas Frayer
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=52a11d11-20a0-bf08-ce64-401b5d0ad133@gmail.com \
--to=peter.ujfalusi@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfrayer@baylibre.com \
--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