From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Marek Vasut <marex@denx.de>, Adam Ford <aford173@gmail.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Input: ili210x - optionally show calibrate sysfs attribute
Date: Tue, 12 Nov 2019 15:52:47 -0800 [thread overview]
Message-ID: <20191112235247.GF13374@dtor-ws> (raw)
In-Reply-To: <20191112210148.3535-2-TheSven73@gmail.com>
On Tue, Nov 12, 2019 at 04:01:48PM -0500, Sven Van Asbroeck wrote:
> Only show the 'calibrate' sysfs attribute on chip flavours
> which support calibration by writing to a calibration register.
>
> Do this by adding a flag to the chip operations structure.
>
> Link: https://lore.kernel.org/lkml/20191111181657.GA57214@dtor-ws/
> Cc: Marek Vasut <marex@denx.de>
> Cc: Adam Ford <aford173@gmail.com>
> Cc: <linux-kernel@vger.kernel.org>
> Cc: linux-input@vger.kernel.org
> Tree: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/log/?h=next
> Signed-off-by: Sven Van Asbroeck <TheSven73@gmail.com>
Applied, thank you.
> ---
> drivers/input/touchscreen/ili210x.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/input/touchscreen/ili210x.c b/drivers/input/touchscreen/ili210x.c
> index 3b8e24815a1f..b0454cdacf38 100644
> --- a/drivers/input/touchscreen/ili210x.c
> +++ b/drivers/input/touchscreen/ili210x.c
> @@ -32,6 +32,7 @@ struct ili2xxx_chip {
> bool (*continue_polling)(const u8 *data, bool touch);
> unsigned int max_touches;
> unsigned int resolution;
> + bool has_calibrate_reg;
> };
>
> struct ili210x {
> @@ -102,6 +103,7 @@ static const struct ili2xxx_chip ili210x_chip = {
> .parse_touch_data = ili210x_touchdata_to_coords,
> .continue_polling = ili210x_check_continue_polling,
> .max_touches = 2,
> + .has_calibrate_reg = true,
> };
>
> static int ili211x_read_touch_data(struct i2c_client *client, u8 *data)
> @@ -227,6 +229,7 @@ static const struct ili2xxx_chip ili251x_chip = {
> .parse_touch_data = ili251x_touchdata_to_coords,
> .continue_polling = ili251x_check_continue_polling,
> .max_touches = 10,
> + .has_calibrate_reg = true,
> };
>
> static bool ili210x_report_events(struct ili210x *priv, u8 *touchdata)
> @@ -310,8 +313,19 @@ static struct attribute *ili210x_attributes[] = {
> NULL,
> };
>
> +static umode_t ili210x_calibrate_visible(struct kobject *kobj,
> + struct attribute *attr, int index)
> +{
> + struct device *dev = kobj_to_dev(kobj);
> + struct i2c_client *client = to_i2c_client(dev);
> + struct ili210x *priv = i2c_get_clientdata(client);
> +
> + return priv->chip->has_calibrate_reg;
> +}
> +
> static const struct attribute_group ili210x_attr_group = {
> .attrs = ili210x_attributes,
> + .is_visible = ili210x_calibrate_visible,
> };
>
> static void ili210x_power_down(void *data)
> --
> 2.17.1
>
--
Dmitry
next prev parent reply other threads:[~2019-11-12 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 21:01 [PATCH v2 1/2] Input: ili210x - add resolution to chip operations structure Sven Van Asbroeck
2019-11-12 21:01 ` [PATCH v2 2/2] Input: ili210x - optionally show calibrate sysfs attribute Sven Van Asbroeck
2019-11-12 23:52 ` Dmitry Torokhov [this message]
2019-11-12 23:52 ` [PATCH v2 1/2] Input: ili210x - add resolution to chip operations structure Dmitry Torokhov
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=20191112235247.GF13374@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aford173@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=thesven73@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;
as well as URLs for NNTP newsgroup(s).