From nobody Fri Dec 19 00:08:07 2025 Received: from michel.telenet-ops.be (michel.telenet-ops.be [195.130.137.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2A5A61A01AE for ; Tue, 30 Jul 2024 13:35:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=195.130.137.88 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1722346558; cv=none; b=OXZ09j5a8Fx+oQOnMqgdVjGq9APOsVIbjC7V2jZflpXN+RtpKC54X1mkRec3ctWFs/+hu7zFpesgzAKOVCH6FzDOeVraGidePre9N/h02LgZJ7jqanK9jUraxf6jUyS16S+VqCArEuF1Uv5PV9FB4McS/kLPkr5/0QAekQwvdfo= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1722346558; c=relaxed/simple; bh=8ZKVgUkDg1H9qoLmR9WGjhmiqAIJWR6xufVkeSIkI6s=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=e48NHiPFVC9hLmOXDZIVVNnLZhjLaAgGVchBW8laShT0NQ89eOQ2JPCGMY5+l6f++mq5Kep4Gu73vuAsV1BcFK9TEQU4TpzrTKzCJROMengUy7l0g6f0sMa4Gmh1HQs4VcDs6OSIFfX134jFq4LkzO7xZSLhJUj8M7nKIuTBhdw= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=glider.be; spf=none smtp.mailfrom=linux-m68k.org; arc=none smtp.client-ip=195.130.137.88 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=glider.be Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux-m68k.org Received: from ramsan.of.borg ([IPv6:2a02:1810:ac12:ed80:520d:93ad:ff6d:335e]) by michel.telenet-ops.be with bizsmtp id tpbo2C00330Ayot06pbooH; Tue, 30 Jul 2024 15:35:48 +0200 Received: from rox.of.borg ([192.168.97.57]) by ramsan.of.borg with esmtp (Exim 4.95) (envelope-from ) id 1sYn0f-004Akz-4Y; Tue, 30 Jul 2024 15:35:48 +0200 Received: from geert by rox.of.borg with local (Exim 4.95) (envelope-from ) id 1sYn12-00DzGt-5X; Tue, 30 Jul 2024 15:35:48 +0200 From: Geert Uytterhoeven To: Mark Brown , Maxime Ripard , Conor Dooley Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven Subject: [PATCH] spi: spidev: Add missing spi_device_id for bh2228fv Date: Tue, 30 Jul 2024 15:35:47 +0200 Message-Id: X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" When the of_device_id entry for "rohm,bh2228fv" was added, the corresponding spi_device_id was forgotten, causing a warning message during boot-up: SPI driver spidev has no spi_device_id for rohm,bh2228fv Fix module autoloading and shut up the warning by adding the missing entry. Fixes: fc28d1c1fe3b3e2f ("spi: spidev: add correct compatible for Rohm BH22= 28FV") Signed-off-by: Geert Uytterhoeven --- drivers/spi/spidev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c index 05e6d007f9a7f617..5304728c68c20d3a 100644 --- a/drivers/spi/spidev.c +++ b/drivers/spi/spidev.c @@ -700,6 +700,7 @@ static const struct class spidev_class =3D { }; =20 static const struct spi_device_id spidev_spi_ids[] =3D { + { .name =3D "bh2228fv" }, { .name =3D "dh2228fv" }, { .name =3D "ltc2488" }, { .name =3D "sx1301" }, --=20 2.34.1