From: "Martin Tůma" <tumic@gpxsee.org>
To: Vinod Koul <vkoul@kernel.org>, Lizhi Hou <lizhi.hou@amd.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
max.zhen@amd.com, sonal.santan@amd.com, larry.liu@amd.com,
brian.xu@amd.com
Subject: Re: [RESEND PATCH V11 XDMA 1/2] dmaengine: xilinx: xdma: Add xilinx xdma driver
Date: Wed, 18 Jan 2023 16:20:39 +0100 [thread overview]
Message-ID: <e2cc9724-1ac3-53c4-e33a-197262b989a2@gpxsee.org> (raw)
In-Reply-To: <Y8eRhO0j+zozVL8N@matsya>
>> +static struct platform_driver xdma_driver = {
>> + .driver = {
>> + .name = "xdma",
>> + },
>> + .id_table = xdma_id_table,
>> + .probe = xdma_probe,
>> + .remove = xdma_remove,
>> +};
>> +
>> +module_platform_driver(xdma_driver);
>
> who creates this platform device? Any reason why this is not a _real_
> device?
>
The platform device is created by the PCIe card device/driver that uses
XDMA. See for example our mgb4 v4l2 driver:
https://patchwork.kernel.org/project/linux-media/patch/20230113172636.2590-2-tumic@gpxsee.org/
M.
next prev parent reply other threads:[~2023-01-18 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 20:54 [RESEND PATCH V11 XDMA 0/2] xilinx XDMA driver Lizhi Hou
2023-01-17 20:54 ` [RESEND PATCH V11 XDMA 1/2] dmaengine: xilinx: xdma: Add xilinx xdma driver Lizhi Hou
2023-01-18 6:28 ` Vinod Koul
2023-01-18 15:20 ` Martin Tůma [this message]
2023-01-18 21:59 ` Lizhi Hou
2023-01-17 20:54 ` [RESEND PATCH V11 XDMA 2/2] dmaengine: xilinx: xdma: Add user logic interrupt support Lizhi Hou
2023-01-18 6:29 ` Vinod Koul
2023-01-18 15:28 ` Martin Tůma
2023-01-18 15:33 ` Lars-Peter Clausen
2023-01-18 16:39 ` Martin Tůma
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 16:40 [RESEND PATCH V11 XDMA 0/2] xilinx XDMA driver Lizhi Hou
2023-01-04 16:40 ` [RESEND PATCH V11 XDMA 1/2] dmaengine: xilinx: xdma: Add xilinx xdma driver Lizhi Hou
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=e2cc9724-1ac3-53c4-e33a-197262b989a2@gpxsee.org \
--to=tumic@gpxsee.org \
--cc=brian.xu@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=larry.liu@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=max.zhen@amd.com \
--cc=sonal.santan@amd.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
all inboxes | Powered by JetHome®