From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/4] driver name fixes
Date: Mon, 08 Dec 2025 13:00:50 +0100 [thread overview]
Message-ID: <20251208-nvmem-eeprom-v1-0-41ba588e2f3a@pengutronix.de> (raw)
Starting point of this series was that I had multiple EEPROMs on a board
from which one had an alias "eeprom0" and the other ones didn't have
aliases. the EEPROMs without aliases failed to register because they
tried to register themselves as "eeprom0" as well.
While EEPROMs triggered this series it fixes a longstanding problem in
barebox: It was possible to register two devices with the same name when
one device was registered as "foo0", DEVICE_ID_SINGLE and another one
as "foo", id = 0.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (4):
driver: implement get_free_deviceid_from()
nvmem: fix device name setting
driver: fix device name clashes
eeprom: at24: reserve EEPROM names which have an alias
drivers/base/driver.c | 25 ++++++++++++++-----------
drivers/eeprom/at24.c | 12 ++++++++----
drivers/nvmem/core.c | 22 +++++++++++++++-------
include/driver.h | 7 ++++++-
4 files changed, 43 insertions(+), 23 deletions(-)
---
base-commit: 500df27eb054f86ce232c5bb30c3a7ea8f771e61
change-id: 20251208-nvmem-eeprom-94b9b05b1c04
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2025-12-08 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 12:00 Sascha Hauer [this message]
2025-12-08 12:00 ` [PATCH 1/4] driver: implement get_free_deviceid_from() Sascha Hauer
2025-12-08 12:00 ` [PATCH 2/4] nvmem: fix device name setting Sascha Hauer
2025-12-08 12:00 ` [PATCH 3/4] driver: fix device name clashes Sascha Hauer
2025-12-08 12:00 ` [PATCH 4/4] eeprom: at24: reserve EEPROM names which have an alias Sascha Hauer
2025-12-10 7:09 ` [PATCH 0/4] driver name fixes Sascha Hauer
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=20251208-nvmem-eeprom-v1-0-41ba588e2f3a@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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