From: Jean Delvare <jdelvare@suse.de>
To: Linux I2C <linux-i2c@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Wolfram Sang <wsa@the-dreams.de>
Subject: [PATCH 4/4] i2c: i801: Instantiate SPD EEPROMs automatically
Date: Mon, 14 Oct 2019 11:41:46 +0200 [thread overview]
Message-ID: <20191014114146.08b58f16@endymion> (raw)
In-Reply-To: <20191014113636.57b5ce89@endymion>
Call the function to instantiate SPD EEPROMs automatically on the
main SMBus controller.
Multiplexed SMBus systems are excluded for now as they are more
complex to handle.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
---
drivers/i2c/busses/i2c-i801.c | 4 ++++
1 file changed, 4 insertions(+)
--- linux-5.3.orig/drivers/i2c/busses/i2c-i801.c 2019-10-11 11:00:10.574348301 +0200
+++ linux-5.3/drivers/i2c/busses/i2c-i801.c 2019-10-11 11:20:03.741576063 +0200
@@ -1314,6 +1314,10 @@ static void i801_probe_optional_slaves(s
if (is_dell_system_with_lis3lv02d())
register_dell_lis3lv02d_i2c_device(priv);
+
+ /* Instantiate SPD EEPROMs unless the SMBus is multiplexed */
+ if (!priv->mux_drvdata)
+ i2c_register_spd(&priv->adapter);
}
#else
static void __init input_apanel_init(void) {}
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2019-10-14 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 9:36 [PATCH 0/4] Instantiate SPD EEPROMs at boot on x86 Jean Delvare
2019-10-14 9:38 ` [PATCH 1/4] firmware: dmi: Remember the memory type Jean Delvare
2019-10-14 9:38 ` [PATCH 2/4] firmware: dmi: Add dmi_memdev_handle Jean Delvare
2019-10-14 9:39 ` [PATCH 3/4] i2c: smbus: Add a way to instantiate SPD EEPROMs automatically Jean Delvare
2019-10-14 10:21 ` kbuild test robot
2019-10-14 14:55 ` Jean Delvare
2019-10-14 9:41 ` Jean Delvare [this message]
2019-10-14 10:22 ` [PATCH 4/4] i2c: i801: Instantiate " kbuild test robot
2019-10-14 18:02 ` Jean Delvare
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=20191014114146.08b58f16@endymion \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).