From: "Michal Vokáč" <michal.vokac@ysoft.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Fabio Estevam" <festevam@gmail.com>,
"Michal Vokáč" <michal.vokac@ysoft.com>
Subject: [PATCH] Input: pixcir_i2c_ts - add support for one-time total calibration
Date: Wed, 12 Nov 2025 14:00:19 +0100 [thread overview]
Message-ID: <20251112130019.1488005-1-michal.vokac@ysoft.com> (raw)
The Pixcir Tango controller has support for a one-time total calibration
(manual calibration) procedure. Its purpose is to measure the capacitance
offsets of the electrode system and to store these values into EEPROM.
During normal operation this calibration data is subtracted from the values
measured. This calibration should be necessary only once in the product
lifetime. It should be performed as part of the final adjustment after
the panel is mounted in the product.
Add support for the calibration with sysfs interface.
Signed-off-by: Michal Vokáč <michal.vokac@ysoft.com>
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 34 +++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/drivers/input/touchscreen/pixcir_i2c_ts.c b/drivers/input/touchscreen/pixcir_i2c_ts.c
index dad5786e82a4..2215e56b1458 100644
--- a/drivers/input/touchscreen/pixcir_i2c_ts.c
+++ b/drivers/input/touchscreen/pixcir_i2c_ts.c
@@ -24,6 +24,7 @@
*/
#define PIXCIR_REG_POWER_MODE 51
#define PIXCIR_REG_INT_MODE 52
+#define PIXCIR_REG_SPECOP 58
/*
* Power modes:
@@ -82,6 +83,7 @@ struct pixcir_i2c_ts_data {
const struct pixcir_i2c_chip_data *chip;
struct touchscreen_properties prop;
bool running;
+ struct mutex sysfs_mutex;
};
struct pixcir_report_data {
@@ -462,6 +464,35 @@ static int pixcir_i2c_ts_resume(struct device *dev)
static DEFINE_SIMPLE_DEV_PM_OPS(pixcir_dev_pm_ops,
pixcir_i2c_ts_suspend, pixcir_i2c_ts_resume);
+static ssize_t calibrate_store(struct device *dev,
+ struct device_attribute *attr,
+ const char *buf, size_t count)
+{
+ struct i2c_client *client = to_i2c_client(dev);
+ struct pixcir_i2c_ts_data *ts = i2c_get_clientdata(client);
+ static const u8 cmd = 0x03;
+ int error;
+
+ error = mutex_lock_interruptible(&ts->sysfs_mutex);
+ if (error)
+ return error;
+
+ error = i2c_smbus_write_byte_data(ts->client, PIXCIR_REG_SPECOP, cmd);
+ if (error)
+ dev_err(dev, "calibrate command failed: %d\n", error);
+
+ mutex_unlock(&ts->sysfs_mutex);
+ return error ?: count;
+}
+
+static DEVICE_ATTR_WO(calibrate);
+
+static struct attribute *pixcir_i2c_ts_attrs[] = {
+ &dev_attr_calibrate.attr,
+ NULL,
+};
+ATTRIBUTE_GROUPS(pixcir_i2c_ts);
+
static int pixcir_i2c_ts_probe(struct i2c_client *client)
{
const struct i2c_device_id *id = i2c_client_get_device_id(client);
@@ -488,6 +519,8 @@ static int pixcir_i2c_ts_probe(struct i2c_client *client)
return -ENOMEM;
}
+ mutex_init(&tsdata->sysfs_mutex);
+
tsdata->client = client;
tsdata->input = input;
@@ -600,6 +633,7 @@ MODULE_DEVICE_TABLE(of, pixcir_of_match);
static struct i2c_driver pixcir_i2c_ts_driver = {
.driver = {
.name = "pixcir_ts",
+ .dev_groups = pixcir_i2c_ts_groups,
.pm = pm_sleep_ptr(&pixcir_dev_pm_ops),
.of_match_table = of_match_ptr(pixcir_of_match),
},
--
2.43.0
reply other threads:[~2025-11-12 13:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251112130019.1488005-1-michal.vokac@ysoft.com \
--to=michal.vokac@ysoft.com \
--cc=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).