From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Sangwon Jee <jeesw@melfas.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [V4] Input: Add MELFAS MIP4 Touchscreen driver
Date: Tue, 23 Feb 2016 15:18:19 -0800 [thread overview]
Message-ID: <20160223231819.GE30638@dtor-ws> (raw)
In-Reply-To: <1455543645-7156-1-git-send-email-jeesw@melfas.com>
Hi,
On Mon, Feb 15, 2016 at 10:40:45PM +0900, Sangwon Jee wrote:
> This is an input driver for MELFAS MIP4 Touchscreen devices,
> made by the original vendor, MELFAS.
>
> MIP4 means MELFAS Interface Protocol Version 4.
> MELFAS MMS400, MMS500, MCS8000, MIT200, MIT300, MIT400, MFS10 and other
> recent touchscreen devices are using MIP4 and supported by this driver.
>
> There are two MELFAS touchscreen drivers(mcs5000_ts, mms114) in the kernel.
> But those drivers are for discontinued models and not supported by MELFAS.
>
> Signed-off-by: Sangwon Jee <jeesw@melfas.com>
As you may have noticed I ended up applying the previous version of the
driver. Any additional changes should be made against the version in my
'next' branch or linux-next.
> +static ssize_t mip4_sysfs_read_hw_version(struct device *dev,
> + struct device_attribute *attr,
> + char *buf)
> +{
> + struct i2c_client *client = to_i2c_client(dev);
> + struct mip4_ts *ts = i2c_get_clientdata(client);
> + size_t count;
> +
> + /* Take lock to prevent racing with firmware update */
> + mutex_lock(&ts->input->mutex);
> +
> + count = snprintf(buf, PAGE_SIZE, "%s\n", "MIT400");
> +
> + mutex_unlock(&ts->input->mutex);
> +
> + return count;
> +}
It is unclear why we need basically a constant attribute.
Thanks.
--
Dmitry
prev parent reply other threads:[~2016-02-23 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 13:40 [V4] Input: Add MELFAS MIP4 Touchscreen driver Sangwon Jee
2016-02-23 23:18 ` Dmitry Torokhov [this message]
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=20160223231819.GE30638@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=jeesw@melfas.com \
--cc=linux-input@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).