From: Vasiliy Doylov via B4 Relay <devnull+nekodevelopper.gmail.com@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Vasiliy Doylov <nekodevelopper@gmail.com>
Subject: [PATCH v3 5/5] iio: accel: mc3230: add mc3510c support
Date: Sun, 12 Jan 2025 15:25:39 +0300 [thread overview]
Message-ID: <20250112-mainlining-mc3510c-v3-5-9ee6520ab69d@gmail.com> (raw)
In-Reply-To: <20250112-mainlining-mc3510c-v3-0-9ee6520ab69d@gmail.com>
From: Vasiliy Doylov <nekodevelopper@gmail.com>
This commit integrates support for the mc3510c into the mc3230 driver.
Tested on Huawei MediaPad T3 10 (huawei-agassi)
Signed-off-by: Vasiliy Doylov <nekodevelopper@gmail.com>
---
drivers/iio/accel/mc3230.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/iio/accel/mc3230.c b/drivers/iio/accel/mc3230.c
index 1b58f3ea50655b6563a78a2531b16a8088e8f8d5..92934975edc77b11ed6dc3da077a28d317314fab 100644
--- a/drivers/iio/accel/mc3230.c
+++ b/drivers/iio/accel/mc3230.c
@@ -46,6 +46,14 @@ static struct mc3230_chip_info mc3230_chip_info = {
.scale = 115411765,
};
+static struct mc3230_chip_info mc3510c_chip_info = {
+ .chip_id = 0x23,
+ .name = "mc3510c",
+ .product_code = 0x10,
+ /* Was obtained empirically */
+ .scale = 625000000,
+};
+
#define MC3230_CHANNEL(reg, axis) { \
.type = IIO_ACCEL, \
.address = reg, \
@@ -225,12 +233,14 @@ static DEFINE_SIMPLE_DEV_PM_OPS(mc3230_pm_ops, mc3230_suspend, mc3230_resume);
static const struct i2c_device_id mc3230_i2c_id[] = {
{ "mc3230", (kernel_ulong_t)&mc3230_chip_info },
+ { "mc3510c", (kernel_ulong_t)&mc3510c_chip_info },
{}
};
MODULE_DEVICE_TABLE(i2c, mc3230_i2c_id);
static const struct of_device_id mc3230_of_match[] = {
{ .compatible = "mcube,mc3230", &mc3230_chip_info },
+ { .compatible = "mcube,mc3510c", &mc3510c_chip_info },
{}
};
MODULE_DEVICE_TABLE(of, mc3230_of_match);
--
2.47.1
next prev parent reply other threads:[~2025-01-12 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 12:25 [PATCH v3 0/5] iio: accel: mc3230: add mount matrix, of match and mc3510c support Vasiliy Doylov via B4 Relay
2025-01-12 12:25 ` [PATCH v3 1/5] dt-bindings: iio: accel: mc3230: document mc3510c Vasiliy Doylov via B4 Relay
2025-01-13 8:49 ` Krzysztof Kozlowski
2025-01-12 12:25 ` [PATCH v3 2/5] iio: accel: mc3230: add mount matrix support Vasiliy Doylov via B4 Relay
2025-01-12 16:28 ` Jonathan Cameron
2025-01-12 12:25 ` [PATCH v3 3/5] iio: accel: mc3230: add OF match table Vasiliy Doylov via B4 Relay
2025-01-12 16:29 ` Jonathan Cameron
2025-01-12 16:38 ` Vasiliy Doylov
2025-01-12 12:25 ` [PATCH v3 4/5] iio: accel: mc3230: add multiple devices support Vasiliy Doylov via B4 Relay
2025-01-12 16:32 ` Jonathan Cameron
2025-01-13 8:51 ` Krzysztof Kozlowski
2025-01-12 12:25 ` Vasiliy Doylov via B4 Relay [this message]
2025-01-12 16:34 ` [PATCH v3 5/5] iio: accel: mc3230: add mc3510c support Jonathan Cameron
2025-01-13 8:51 ` Krzysztof Kozlowski
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=20250112-mainlining-mc3510c-v3-5-9ee6520ab69d@gmail.com \
--to=devnull+nekodevelopper.gmail.com@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nekodevelopper@gmail.com \
--cc=robh@kernel.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