From: Naresh Solanki <naresh.solanki@9elements.com>
To: Jean Delvare <jdelvare@suse.com>, Guenter Roeck <linux@roeck-us.net>
Cc: Naresh Solanki <Naresh.Solanki@9elements.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/2] hwmon: (max6639) Add compatible string
Date: Thu, 20 Apr 2023 13:17:58 +0200 [thread overview]
Message-ID: <20230420111759.2687001-2-Naresh.Solanki@9elements.com> (raw)
In-Reply-To: <20230420111759.2687001-1-Naresh.Solanki@9elements.com>
Use maxim,max6639 as compatible string for the driver.
Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
...
Changes in V2:
- None, Updated DT patch
---
drivers/hwmon/max6639.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/hwmon/max6639.c b/drivers/hwmon/max6639.c
index 9b895402c80d..ada410bfb7b6 100644
--- a/drivers/hwmon/max6639.c
+++ b/drivers/hwmon/max6639.c
@@ -618,11 +618,17 @@ MODULE_DEVICE_TABLE(i2c, max6639_id);
static DEFINE_SIMPLE_DEV_PM_OPS(max6639_pm_ops, max6639_suspend, max6639_resume);
+static const struct of_device_id max6639_of_match[] = {
+ { .compatible = "maxim,max6639", },
+ { },
+};
+
static struct i2c_driver max6639_driver = {
.class = I2C_CLASS_HWMON,
.driver = {
.name = "max6639",
.pm = pm_sleep_ptr(&max6639_pm_ops),
+ .of_match_table = max6639_of_match,
},
.probe_new = max6639_probe,
.id_table = max6639_id,
--
2.39.1
next prev parent reply other threads:[~2023-04-20 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 11:17 [PATCH v2 1/2] dt-bindings: hwmon: Add max6639 Naresh Solanki
2023-04-20 11:17 ` Naresh Solanki [this message]
2023-04-21 7:37 ` Krzysztof Kozlowski
2023-04-24 9:18 ` Naresh Solanki
2023-04-24 9:42 ` Krzysztof Kozlowski
2023-04-24 9:53 ` Naresh Solanki
2023-05-03 8:26 ` Naresh Solanki
2023-05-03 16:18 ` Krzysztof Kozlowski
2023-05-04 9:47 ` Naresh Solanki
2023-05-04 10:47 ` Krzysztof Kozlowski
2023-05-04 11:36 ` Naresh Solanki
2023-05-04 11:44 ` Krzysztof Kozlowski
2023-07-19 17:39 ` Guenter Roeck
2023-07-20 7:51 ` Naresh Solanki
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=20230420111759.2687001-2-Naresh.Solanki@9elements.com \
--to=naresh.solanki@9elements.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.