From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiada Wang <jiada_wang@mentor.com>
Cc: nick@shmanahar.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, george_davis@mentor.com
Subject: Re: [PATCH v1 31/63] Input: atmel_mxt_ts - add memory access interface via sysfs
Date: Fri, 16 Aug 2019 10:29:20 -0700 [thread overview]
Message-ID: <20190816172920.GK121898@dtor-ws> (raw)
In-Reply-To: <20190816083451.18947-2-jiada_wang@mentor.com>
On Fri, Aug 16, 2019 at 05:34:19PM +0900, Jiada Wang wrote:
> From: Nick Dyer <nick.dyer@itdev.co.uk>
>
> Atmel maXTouch chips can be addressed via an "Object Based Protocol" which
> defines how i2c registers are mapped to different functions within the
> chips. This interface exposes the register map and allows user-space
> utilities to inspect and alter object configuration, and to view diagnostic
> data, while the device is running.
I'd say if we want this we should look into write support in regmap and
switching the driver over.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-08-16 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 8:34 [PATCH v1 30/63] Input: atmel_mxt_ts - implement debug output for messages Jiada Wang
2019-08-16 8:34 ` [PATCH v1 31/63] Input: atmel_mxt_ts - add memory access interface via sysfs Jiada Wang
2019-08-16 17:29 ` Dmitry Torokhov [this message]
2019-08-23 3:00 ` Jiada Wang
2019-08-16 8:34 ` [PATCH v1 32/63] Input: atmel_mxt_ts - implement improved debug message interface Jiada Wang
2019-08-16 8:34 ` [PATCH v1 33/63] Input: atmel_mxt_ts - eliminate data->raw_info_block Jiada Wang
2019-08-16 8:34 ` [PATCH v1 34/63] Input: atmel_mxt_ts - Change call-points of mxt_free_* functions Jiada Wang
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=20190816172920.GK121898@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=george_davis@mentor.com \
--cc=jiada_wang@mentor.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@shmanahar.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).