From: Kevin Hilman <khilman@baylibre.com>
To: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>, dmaengine@vger.kernel.org
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Nicolas Frayer <nfrayer@baylibre.com>
Subject: Re: [PATCH 0/3] dma/ti: enable udma and psil to be built as modules
Date: Tue, 27 Sep 2022 16:10:16 -0700 [thread overview]
Message-ID: <7hfsgcxvl3.fsf@baylibre.com> (raw)
In-Reply-To: <541337f7-1c0d-3ea4-d959-cd5aed83e615@gmail.com>
Péter Ujfalusi <peter.ujfalusi@gmail.com> writes:
> On 27/09/2022 00:21, Kevin Hilman wrote:
>> Hi Péter,
>>
>> Péter Ujfalusi <peter.ujfalusi@gmail.com> writes:
>>
>>> On 9/26/22 21:18, Kevin Hilman wrote:
>>>> Enable the UDMA driver & glue and PSIL maps to be built & loaded as modules.
>>>>
>>>> The defauilt Kconfig settings are not changed, so default upstream is
>>>> still to be built in. This series just enables the option to build as
>>>> modules.
>>>
>>> I can finally drop the half backed stuff I roll on top of -next ;)
>>>
>>> Do you plan to convert the ringacc also? It is straight forward, like:
>>> https://github.com/omap-audio/linux-audio/commit/01f9290c1c61e8bbc0fbdd877382672883ba7e73
>>
>> Yes, my colleague Nicolas (cc'd) was planning ringacc shortly, but we
>> didn't realize you had already don it. Your version looks fine to me.
>> Any reason not to submit yours?
>
> It can only be sent after the UDMA is able to be built as a module.
OK, I sent a v2 of this series, which I think should be ready for merge
now.
> When I did the module support there were also a tisci dependency which
> for some reason took too long for me to be able to send these.
> I can send my version later if it is OK, but if Nicolas have a better
> take on it, I don't mind.
We've got a handful of other conversions coming for a fully modular
kernel, so I'm sure Nicolas would be happy if you took care of
ringacc. :)
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-27 23:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 18:18 [PATCH 0/3] dma/ti: enable udma and psil to be built as modules Kevin Hilman
2022-09-26 18:18 ` [PATCH 1/3] of/irq: export of_msi_get_domain Kevin Hilman
2022-09-26 18:18 ` [PATCH 2/3] dma/ti: convert k3-udma to module Kevin Hilman
2022-09-26 18:52 ` Péter Ujfalusi
2022-09-26 21:17 ` Kevin Hilman
2022-09-27 17:07 ` Péter Ujfalusi
2022-09-26 18:18 ` [PATCH 3/3] dma/ti: convert PSIL to be buildable as module Kevin Hilman
2022-09-26 18:47 ` Péter Ujfalusi
2022-09-26 18:50 ` Kevin Hilman
2022-09-27 17:19 ` Péter Ujfalusi
2022-09-27 22:56 ` Kevin Hilman
2022-09-26 19:02 ` [PATCH 0/3] dma/ti: enable udma and psil to be built as modules Péter Ujfalusi
2022-09-26 21:21 ` Kevin Hilman
2022-09-27 17:21 ` Péter Ujfalusi
2022-09-27 23:10 ` Kevin Hilman [this message]
2022-09-28 13:54 ` Péter Ujfalusi
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=7hfsgcxvl3.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nfrayer@baylibre.com \
--cc=peter.ujfalusi@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).