From: Mark Brown <broonie@kernel.org>
To: Gustav Wiklander <gustavwi@axis.com>
Cc: Gustav Wiklander <gustav.wiklander@axis.com>,
kernel@axis.com, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: spidev: Fix so the module is autoloaded when built as external
Date: Thu, 7 Jan 2021 17:40:52 +0000 [thread overview]
Message-ID: <20210107174052.GH4726@sirena.org.uk> (raw)
In-Reply-To: <124e3214-37b9-524b-7888-a31e8cb455da@axis.com>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
On Tue, Jan 05, 2021 at 10:44:21AM +0100, Gustav Wiklander wrote:
> On 1/4/21 10:34 PM, Mark Brown wrote:
> > On Mon, Jan 04, 2021 at 04:34:35PM +0100, Gustav Wiklander wrote:
> > > The spi framework sets the modalias for the spi device to belong in
> > > either the acpi device table or the SPI device table. It can never
> > > be in the OF table. Therefore the spidev driver should populate the
> > > spi device table rather than the OF table.
> > Why is this a good solution rather than ensuring the the OF IDs can be
> > used directly?
> You suggestion is of course a solid alternative forward. However, the
> downside with supporting the OF device table for automatic module loading is
> that a lot of spi device drivers must be updated. Also
Is the module code too limited to cope with more than one table?
> If adding support of OF device table the spi device drivers must now include
> a MODULE_DEVICE_TABLE(of,...) as the spi device alias will no longer match
> the alias in the module.
> This command gives 186 spi device drivers.
How about SPI drivers that already have an OF table and expect it to
work, I rather suspect we have a lot of cases where people are adding
SPI IDs to DT that don't appear in the module tables and frankly I think
that's a reasonable expectation. If there's an issue here beyond
missing MODULE_DEVICE_TABLEs in drivers I'd expect it to be fixed in the
core, otherwise we're just leaving sharp edges for everyone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-01-07 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 15:34 [PATCH] spi: spidev: Fix so the module is autoloaded when built as external Gustav Wiklander
2021-01-04 21:34 ` Mark Brown
2021-01-05 9:44 ` Gustav Wiklander
2021-01-07 17:40 ` Mark Brown [this message]
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=20210107174052.GH4726@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gustav.wiklander@axis.com \
--cc=gustavwi@axis.com \
--cc=kernel@axis.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox