From: Nicolas Frayer <nfrayer@baylibre.com>
To: nm@ti.com, ssantosh@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: khilman@baylibre.com, glaroque@baylibre.com, nfrayer@baylibre.com
Subject: [PATCH v5 0/2] soc: ti: Add module build support to the k3 socinfo driver
Date: Wed, 16 Nov 2022 15:51:01 +0100 [thread overview]
Message-ID: <20221116145103.26744-1-nfrayer@baylibre.com> (raw)
In order for the TI K3 SoC info driver to be built as a module, the
following changes have been made:
- Converted memory allocations to devm and added the remove callback
- Added necessary code to build the driver as a module
v2->v3:
dropped module conversion part of this series while other driver
dependencies on socinfo are worked out.
A dependency issue is introduced by changing subsys_initcall()
to module_platform_driver(). Some drivers using the socinfo information
probe before the socinfo driver itself and it makes their probe fail.
v3->v4:
reintegrated the module build support and added patches for udma and mdio
drivers to allow for deferred probe if socinfo hasn't probed yet.
v4->v5:
Remove the k3 udma and mdio patches from this series and sent them
individually
Nicolas Frayer (2):
soc: ti: Convert allocations to devm
soc: ti: Add module build support
arch/arm64/Kconfig.platforms | 1 -
drivers/soc/ti/Kconfig | 3 ++-
drivers/soc/ti/k3-socinfo.c | 47 +++++++++++++++++++++++-------------
3 files changed, 32 insertions(+), 19 deletions(-)
--
2.25.1
next reply other threads:[~2022-11-16 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 14:51 Nicolas Frayer [this message]
2022-11-16 14:51 ` [PATCH v5 1/2] soc: ti: Convert allocations to devm Nicolas Frayer
2022-11-16 14:51 ` [PATCH v5 2/2] soc: ti: Add module build support Nicolas Frayer
2022-11-17 7:28 ` [PATCH v5 0/2] soc: ti: Add module build support to the k3 socinfo driver Nishanth Menon
2022-11-17 9:55 ` 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=20221116145103.26744-1-nfrayer@baylibre.com \
--to=nfrayer@baylibre.com \
--cc=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=ssantosh@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