From: Nicolas Frayer <nfrayer@baylibre.com>
To: nm@ti.com, ssantosh@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, khilman@baylibre.com,
glaroque@baylibre.com, granquet@baylibre.com,
Nicolas Frayer <nfrayer@baylibre.com>
Subject: [PATCH v2 0/2] soc: ti: Convert K3 SoC info driver to module
Date: Mon, 10 Oct 2022 15:15:36 +0200 [thread overview]
Message-ID: <20221010131538.7333-1-nfrayer@baylibre.com> (raw)
In order for the TI K3 SoC info driver to be built as a module, the
following 2 changes have been made:
- Convert memory allocations to devm and added the remove callback
- Added necessary code to build the driver as a module
v1->v2:
- Some drivers using socinfo do not handle deferred probe when socinfo
is built as a module. So defaulting socinfo to built-in until the deferred
probe is handled correctly by those drivers.
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, 27 insertions(+), 24 deletions(-)
--
2.25.1
_______________________________________________
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-10-10 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 13:15 Nicolas Frayer [this message]
2022-10-10 13:15 ` [PATCH v2 1/2] soc: ti: Convert allocations to devm Nicolas Frayer
2022-10-17 22:15 ` Nishanth Menon
2022-10-19 17:50 ` Nicolas Frayer
2022-10-19 17:58 ` Nicolas Frayer
2022-10-10 13:15 ` [PATCH v2 2/2] soc: ti: Add module build support Nicolas Frayer
2022-10-10 16:40 ` Nicolas Frayer
2022-10-17 22:16 ` Nishanth Menon
2022-10-19 17:57 ` 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=20221010131538.7333-1-nfrayer@baylibre.com \
--to=nfrayer@baylibre.com \
--cc=glaroque@baylibre.com \
--cc=granquet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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