From: Paulius Zaleckas <paulius.zaleckas@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Cc: "Eddie James" <eajames@linux.ibm.com>,
"Joel Stanley" <joel@jms.id.au>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Rupesh Majhi" <zoone.rupert@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Paulius Zaleckas" <paulius.zaleckas@gmail.com>
Subject: [PATCH v2 4/6] iio: pressure: dps310: add per-chip data
Date: Tue, 13 Oct 2026 14:21:22 +0300 [thread overview]
Message-ID: <20261013112124.1878296-5-paulius.zaleckas@gmail.com> (raw)
In-Reply-To: <20261013112124.1878296-1-paulius.zaleckas@gmail.com>
Move the coefficient count, the TMP_CFG startup value and the IIO device
name into a per-chip structure, passed through the I2C and ACPI match
data. This prepares for the Zilltek ZTS8032, which has two more
coefficients and a different TMP_CFG layout.
No functional change.
Assisted-by: LLM
Signed-off-by: Paulius Zaleckas <paulius.zaleckas@gmail.com>
---
drivers/iio/pressure/dps310.c | 34 ++++++++++++++++++++++++++--------
1 file changed, 26 insertions(+), 8 deletions(-)
diff --git a/drivers/iio/pressure/dps310.c b/drivers/iio/pressure/dps310.c
index 3bc690cc8609..0d558edff5ab 100644
--- a/drivers/iio/pressure/dps310.c
+++ b/drivers/iio/pressure/dps310.c
@@ -61,6 +61,7 @@
#define DPS310_RESET 0x0c
#define DPS310_RESET_MAGIC 0x09
#define DPS310_COEF_BASE 0x10
+#define DPS310_COEF_LEN 18
/* Make sure sleep time is <= 30ms for usleep_range */
#define DPS310_POLL_SLEEP_US(t) min(30000, (t) / 8)
@@ -85,10 +86,23 @@ static const int scale_factors[] = {
2088960,
};
+struct dps310_chip_info {
+ const char *name;
+ u8 tmp_cfg; /* TMP_CFG at startup: sensor the coefficients are for */
+ u8 coef_len;
+};
+
+static const struct dps310_chip_info dps310_chip_info = {
+ .name = "dps310",
+ .tmp_cfg = DPS310_TMP_EXT,
+ .coef_len = DPS310_COEF_LEN,
+};
+
struct dps310_data {
struct i2c_client *client;
struct regmap *regmap;
struct mutex lock; /* Lock for sequential HW access functions */
+ const struct dps310_chip_info *info;
s32 c0, c1;
s32 c00, c10, c20, c30, c01, c11, c21;
@@ -148,13 +162,13 @@ static const struct iio_chan_spec dps310_channels[] = {
static int dps310_get_coefs(struct dps310_data *data)
{
int rc;
- u8 coef[18];
+ u8 coef[DPS310_COEF_LEN];
u32 c0, c1;
u32 c00, c10, c20, c30, c01, c11, c21;
/* Read all sensor calibration coefficients from the COEF registers. */
rc = regmap_bulk_read(data->regmap, DPS310_COEF_BASE, coef,
- sizeof(coef));
+ data->info->coef_len);
if (rc < 0)
return rc;
@@ -251,10 +265,10 @@ static int dps310_startup(struct dps310_data *data)
return rc;
/*
- * Set up external (MEMS) temperature sensor in single sample, one
- * measurement per second mode
+ * Set up the temperature sensor the coefficients are for in single
+ * sample, one measurement per second mode
*/
- rc = regmap_write(data->regmap, DPS310_TMP_CFG, DPS310_TMP_EXT);
+ rc = regmap_write(data->regmap, DPS310_TMP_CFG, data->info->tmp_cfg);
if (rc)
return rc;
@@ -983,7 +997,11 @@ static int dps310_probe(struct i2c_client *client)
data->client = client;
mutex_init(&data->lock);
- iio->name = DPS310_DEV_NAME;
+ data->info = i2c_get_match_data(client);
+ if (!data->info)
+ return -ENODATA;
+
+ iio->name = data->info->name;
iio->channels = dps310_channels;
iio->num_channels = ARRAY_SIZE(dps310_channels);
iio->info = &dps310_info;
@@ -1022,13 +1040,13 @@ static int dps310_probe(struct i2c_client *client)
}
static const struct i2c_device_id dps310_id[] = {
- { .name = DPS310_DEV_NAME },
+ { .name = "dps310", .driver_data = (kernel_ulong_t)&dps310_chip_info },
{ }
};
MODULE_DEVICE_TABLE(i2c, dps310_id);
static const struct acpi_device_id dps310_acpi_match[] = {
- { "IFX3100" },
+ { "IFX3100", (kernel_ulong_t)&dps310_chip_info },
{ }
};
MODULE_DEVICE_TABLE(acpi, dps310_acpi_match);
--
2.55.0
next prev parent reply other threads:[~2026-10-13 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 11:21 [PATCH v2 0/6] iio: pressure: dps310: fix pressure overflow, add Zilltek ZTS8032 Paulius Zaleckas
2026-10-13 11:21 ` [PATCH v2 1/6] iio: pressure: dps310: fix overflow in the pressure compensation Paulius Zaleckas
2026-10-13 11:21 ` [PATCH v2 2/6] dt-bindings: vendor-prefixes: Add ZillTek Technology Paulius Zaleckas
2026-10-13 11:21 ` [PATCH v2 3/6] dt-bindings: iio: pressure: infineon,dps310: Add Zilltek ZTS8032 Paulius Zaleckas
2026-10-13 11:21 ` Paulius Zaleckas [this message]
2026-10-13 16:52 ` [PATCH v2 4/6] iio: pressure: dps310: add per-chip data Andy Shevchenko
2026-10-13 11:21 ` [PATCH v2 5/6] iio: pressure: dps310: add an OF match table Paulius Zaleckas
2026-10-13 11:21 ` [PATCH v2 6/6] iio: pressure: dps310: add Zilltek ZTS8032 support Paulius Zaleckas
2026-10-13 16:59 ` Andy Shevchenko
2026-10-14 9:56 ` Paulius Zaleckas
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=20261013112124.1878296-5-paulius.zaleckas@gmail.com \
--to=paulius.zaleckas@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=eajames@linux.ibm.com \
--cc=jic23@kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=zoone.rupert@gmail.com \
/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
all inboxes | Powered by JetHome®