mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kryštof Černý" <cleverline1mc@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>
Cc: Mark Brown <broonie@kernel.org>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Miroslav Ondra <ondra@faster.cz>,
	hyblmatous@gmail.com
Subject: eeprom: at25: no module autoload for chip-specific compatibles
Date: Fri, 13 Nov 2026 21:53:58 +0100	[thread overview]
Message-ID: <139f1f39-2e0b-4ca1-86bc-db9732f9d351@gmail.com> (raw)

Hello,

I am facing an "issue" with the at25 driver. We have the driver
compiled as a module and load a device tree overlay with

     compatible = "fujitsu,mb85rs1mt", "atmel,at25";

as required by the at25.yaml binding. However, the module is not
auto-loaded. We have to either modprobe it manually or add a modprobe
alias.

As far as I understand, the SPI core only emits
MODALIAS=spi:<first compatible without vendor prefix>, so the uevent
carries spi:mb85rs1mt. The at25 module only provides spi:at25 and
spi:fm25, added in commit 9e2cd444909b ("eeprom: at25: Add SPI ID
table"), so nothing matches. Once the module is loaded, the device
binds fine through the "atmel,at25" compatible.

Is there a better solution? I thought of adding SPI IDs for the chips
listed in the binding (mb85rs1mt, mb85rs256, ...) to
at25_spi_ids, rather than only at25 and fm25, but I do not know if
that would be acceptable upstream.

Thank you,
Kryštof Černý


                 reply	other threads:[~2026-11-13 20:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=139f1f39-2e0b-4ca1-86bc-db9732f9d351@gmail.com \
    --to=cleverline1mc@gmail.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hyblmatous@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=ondra@faster.cz \
    /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®