From: Markuss Broks <markuss.broks@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Markuss Broks <markuss.broks@gmail.com>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
devicetree@vger.kernel.org
Subject: [PATCH v5 1/5] extcon: sm5502: Clarify SM5703's i2c device ID
Date: Sat, 23 Apr 2022 11:53:14 +0300 [thread overview]
Message-ID: <20220423085319.483524-2-markuss.broks@gmail.com> (raw)
In-Reply-To: <20220423085319.483524-1-markuss.broks@gmail.com>
While SM5502 and SM5504 are purely micro USB switching
circuits, SM5703 is a multi-function device which has multiple
modules in it. Change the i2c_device_id of it to avoid conflict
with MFD driver.
Signed-off-by: Markuss Broks <markuss.broks@gmail.com>
---
drivers/extcon/extcon-sm5502.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/extcon/extcon-sm5502.c b/drivers/extcon/extcon-sm5502.c
index 17a40c3782ee..f706f5288257 100644
--- a/drivers/extcon/extcon-sm5502.c
+++ b/drivers/extcon/extcon-sm5502.c
@@ -831,7 +831,7 @@ static SIMPLE_DEV_PM_OPS(sm5502_muic_pm_ops,
static const struct i2c_device_id sm5502_i2c_id[] = {
{ "sm5502", (kernel_ulong_t)&sm5502_data },
{ "sm5504", (kernel_ulong_t)&sm5504_data },
- { "sm5703", (kernel_ulong_t)&sm5502_data },
+ { "sm5703-muic", (kernel_ulong_t)&sm5502_data },
{ }
};
MODULE_DEVICE_TABLE(i2c, sm5502_i2c_id);
--
2.35.1
next prev parent reply other threads:[~2022-04-23 8:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 8:53 [PATCH v5 0/5] Add support for Silicon Mitus SM5703 MFD Markuss Broks
2022-04-23 8:53 ` Markuss Broks [this message]
2022-04-26 15:44 ` [PATCH v5 1/5] extcon: sm5502: Clarify SM5703's i2c device ID Chanwoo Choi
2022-04-23 8:53 ` [PATCH v5 2/5] dt-bindings: regulator: Add bindings for Silicon Mitus SM5703 regulators Markuss Broks
2022-04-25 18:17 ` Rob Herring
2022-04-28 16:36 ` Rob Herring
2022-04-28 17:04 ` Markuss Broks
2022-04-28 18:45 ` Rob Herring
2022-04-23 8:53 ` [PATCH v5 3/5] dt-bindings: mfd: Add bindings for Silicon Mitus SM5703 MFD Markuss Broks
2022-04-25 18:17 ` Rob Herring
2022-04-23 8:53 ` [PATCH v5 4/5] mfd: sm5703: Add support for " Markuss Broks
2022-06-14 21:32 ` Lee Jones
2022-07-09 10:56 ` Markuss Broks
2022-07-11 7:56 ` Lee Jones
2022-07-15 16:16 ` Markuss Broks
2022-07-18 8:17 ` Lee Jones
2022-07-19 13:58 ` Markuss Broks
2022-07-20 8:22 ` Lee Jones
2022-07-20 12:33 ` Markuss Broks
2022-07-20 13:29 ` Lee Jones
2022-07-20 14:12 ` Markuss Broks
2022-07-20 14:19 ` Lee Jones
2022-04-23 8:53 ` [PATCH v5 5/5] regulator: sm5703-regulator: Add regulators " Markuss Broks
2022-04-26 15:51 ` (subset) [PATCH v5 0/5] Add support for Silicon Mitus " Mark Brown
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=20220423085319.483524-2-markuss.broks@gmail.com \
--to=markuss.broks@gmail.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).