From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: pl022: enable compile testing
Date: Wed, 8 Apr 2026 14:11:27 +0200 [thread overview]
Message-ID: <adZF70NON1o8mmg_@hovoldconsulting.com> (raw)
In-Reply-To: <66cc9a3a-bf75-4a9b-952d-2da82c847308@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]
On Wed, Apr 08, 2026 at 12:47:41PM +0100, Mark Brown wrote:
> On Wed, Apr 08, 2026 at 10:44:07AM +0200, Johan Hovold wrote:
> > There seems to be nothing preventing this driver from being compile
> > tested so enable that for wider build coverage.
>
> $ grep amba drivers/spi/spi-pl022.c
> #include <linux/amba/bus.h>
> #include <linux/amba/pl022.h>
> struct amba_device *adev;
> static int pl022_probe(struct amba_device *adev, const struct amba_id *id)
> status = amba_request_regions(adev, NULL);
> amba_set_drvdata(adev, pl022);
> amba_release_regions(adev);
> pl022_remove(struct amba_device *adev)
> struct pl022 *pl022 = amba_get_drvdata(adev);
> amba_release_regions(adev);
> static const struct amba_id pl022_ids[] = {
> MODULE_DEVICE_TABLE(amba, pl022_ids);
> static struct amba_driver pl022_driver = {
> return amba_driver_register(&pl022_driver);
> amba_driver_unregister(&pl022_driver);
>
> At least amba_request_regions() and amba_release_regions() don't appear
> to have stubs for !AMBA?
Hmm, it builds here on x86 with gcc (15) both as a module and as
built-in.
It seems the probe function is discarded before linking as the amba
driver struct is never used on !AMBA. It definitely compiles.
$ nm /tmp/kbuild/nu/drivers/spi/spi-pl022.o
0000000000000000 d __exitcall_pl022_exit
0000000000000000 r __initcall__kmod_spi_pl022__527_2185_pl022_init4
0000000000000000 r __mod_device_table__kmod_spi_pl022__amba__pl022_ids
0000000000000000 t pl022_exit
0000000000000000 r pl022_ids
0000000000000000 t pl022_init
U __SCK__WARN_trap
0000000000000000 d __UNIQUE_ID_addressable_pl022_init_528
0000000000000008 d __UNIQUE_ID_addressable___SCK__WARN_trap_496.15
000000000000006d r __UNIQUE_ID_modinfo_529
000000000000003b r __UNIQUE_ID_modinfo_530
0000000000000016 r __UNIQUE_ID_modinfo_531
0000000000000000 r __UNIQUE_ID_modinfo_532
0000000000000030 d vendor_arm
0000000000000000 d vendor_lsi
0000000000000020 d vendor_st
0000000000000010 d vendor_st_pl023
Johan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]
next prev parent reply other threads:[~2026-04-08 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 8:44 [PATCH] spi: pl022: enable compile testing Johan Hovold
2026-04-08 11:47 ` Mark Brown
2026-04-08 12:11 ` Johan Hovold [this message]
2026-04-08 15:01 ` Mark Brown
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=adZF70NON1o8mmg_@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.