From: Kevin Hilman <khilman@baylibre.com>
To: Peter 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: [PATCH v2 0/3] dma/ti: enable udma and psil to be built as modules
Date: Tue, 27 Sep 2022 16:08:01 -0700 [thread overview]
Message-ID: <20220927230804.4085579-1-khilman@baylibre.com> (raw)
Enable the UDMA driver & glue and PSIL lib 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.
v1->v2:
- rework PSIL lib into a single .ko
Kevin Hilman (3):
of/irq: export of_msi_get_domain
dma/ti: convert k3-udma to module
dma/ti: convert PSIL to be buildable as module
drivers/dma/ti/Kconfig | 7 +++---
drivers/dma/ti/Makefile | 15 +++++++------
drivers/dma/ti/k3-psil.c | 2 ++
drivers/dma/ti/k3-udma-glue.c | 5 ++++-
drivers/dma/ti/k3-udma.c | 40 +++++------------------------------
drivers/of/irq.c | 1 +
6 files changed, 24 insertions(+), 46 deletions(-)
base-commit: 568035b01cfb107af8d2e4bd2fb9aea22cf5b868
--
2.34.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-09-27 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 23:08 Kevin Hilman [this message]
2022-09-27 23:08 ` [PATCH v2 1/3] of/irq: export of_msi_get_domain Kevin Hilman
2022-09-27 23:08 ` [PATCH v2 2/3] dma/ti: convert k3-udma to module Kevin Hilman
2022-09-28 14:59 ` Corentin Labbe
2022-09-29 7:35 ` Vinod Koul
2022-09-29 23:31 ` Kevin Hilman
2022-09-27 23:08 ` [PATCH v2 3/3] dma/ti: convert PSIL to be buildable as module Kevin Hilman
2022-09-28 13:53 ` 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=20220927230804.4085579-1-khilman@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).