From: Martyn Welch <martyn.welch@collabora.com>
To: Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: gehc: Add SPI ID table
Date: Tue, 28 Sep 2021 10:27:33 +0100 [thread overview]
Message-ID: <e50923c01c77ee84141eba071c009ff4b59982be.camel@collabora.com> (raw)
In-Reply-To: <20210923194609.52647-1-broonie@kernel.org>
On Thu, 2021-09-23 at 20:46 +0100, Mark Brown wrote:
> Currently autoloading for SPI devices does not use the DT ID table,
> it uses
> SPI modalises. Supporting OF modalises is going to be difficult if
> not
> impractical, an attempt was made but has been reverted, so ensure
> that
> module autoloading works for this driver by adding a SPI ID table
> entry
> for the device name part of the compatible - currently only the full
> compatible is listed which isn't very idiomatic and won't match the
> modalias that is generated.
>
> Fixes: 96c8395e2166 ("spi: Revert modalias changes")
> Signed-off-by: Mark Brown <broonie@kernel.org>
Tested-by: Martyn Welch <martyn.welch@collabora.com>
> ---
> drivers/misc/gehc-achc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/misc/gehc-achc.c b/drivers/misc/gehc-achc.c
> index 02f33bc60c56..4c9c5394da6f 100644
> --- a/drivers/misc/gehc-achc.c
> +++ b/drivers/misc/gehc-achc.c
> @@ -539,6 +539,7 @@ static int gehc_achc_probe(struct spi_device
> *spi)
>
> static const struct spi_device_id gehc_achc_id[] = {
> { "ge,achc", 0 },
> + { "achc", 0 },
> { }
> };
> MODULE_DEVICE_TABLE(spi, gehc_achc_id);
prev parent reply other threads:[~2021-09-28 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 19:46 Mark Brown
2021-09-28 9:27 ` Martyn Welch [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=e50923c01c77ee84141eba071c009ff4b59982be.camel@collabora.com \
--to=martyn.welch@collabora.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.reichel@collabora.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
all inboxes | Powered by JetHome®