From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Tirdea, Irina" <irina.tirdea@intel.com>
Cc: Bastien Nocera <hadess@hadess.net>,
Mark Rutland <mark.rutland@arm.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Purdila, Octavian" <octavian.purdila@intel.com>
Subject: Re: [PATCH 6/9] input: goodix: write configuration data to device
Date: Fri, 5 Jun 2015 09:43:26 -0700 [thread overview]
Message-ID: <20150605164326.GC26708@dtor-ws> (raw)
In-Reply-To: <1F3AC3675D538145B1661F571FE1805F19A79DAD@irsmsx105.ger.corp.intel.com>
On Fri, Jun 05, 2015 at 04:36:24PM +0000, Tirdea, Irina wrote:
>
>
> > -----Original Message-----
> > From: Bastien Nocera [mailto:hadess@hadess.net]
> > Sent: 04 June, 2015 15:55
> > To: Tirdea, Irina
> > Cc: Mark Rutland; Dmitry Torokhov; linux-input@vger.kernel.org; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; Purdila,
> > Octavian
> > Subject: Re: [PATCH 6/9] input: goodix: write configuration data to device
> >
> > On Thu, 2015-05-28 at 13:51 +0000, Tirdea, Irina wrote:
> > >
> > > > -----Original Message-----
> > > > From: Mark Rutland [mailto:mark.rutland@arm.com]
> > > > Sent: 28 May, 2015 16:22
> > > > To: Tirdea, Irina
> > > > Cc: Dmitry Torokhov; Bastien Nocera; linux-input@vger.kernel.org;
> > > > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org;
> > > > Purdila, Octavian
> > > > Subject: Re: [PATCH 6/9] input: goodix: write configuration data to
> > > > device
> > > >
> > > > On Thu, May 28, 2015 at 01:47:42PM +0100, Irina Tirdea wrote:
> > > > > Goodix devices can be configured by writing this information
> > > > > to the device at init. The configuration data can
> > > > > be provided through the ACPI/device tree property
> > > > > "device-config". If "device-config" is not set, the default
> > > > > device configuration will be used.
> > > > >
> > > > > Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
> > > > > Signed-off-by: Irina Tirdea <irina.tirdea@intel.com>
> > > > > ---
> > > > > .../bindings/input/touchscreen/goodix.txt | 5 +
> > > > > drivers/input/touchscreen/goodix.c | 143
> > > > > +++++++++++++++++++++
> > > > > 2 files changed, 148 insertions(+)
> > > > >
> > > > > diff --git
> > > > > a/Documentation/devicetree/bindings/input/touchscreen/goodix.txt
> > > > b/Documentation/devicetree/bindings/input/touchscreen/goodix.txt
> > > > > index 7137881..9e4ff69 100644
> > > > > ---
> > > > > a/Documentation/devicetree/bindings/input/touchscreen/goodix.txt
> > > > > +++
> > > > > b/Documentation/devicetree/bindings/input/touchscreen/goodix.txt
> > > > > @@ -15,6 +15,11 @@ Required properties:
> > > > > - irq-gpio : GPIO pin used for IRQ
> > > > > - reset-gpio : GPIO pin used for reset
> > > > >
> > > > > +Optional properties:
> > > > > +
> > > > > + - device-config : device configuration information
> > > > > (specified as byte
> > > > > + array). Maximum size is 240 bytes.
> > > >
> > > > Generally we frown on passing opaque data.
> > > >
> > > > What exactly is encoded in device-config? The description is very
> > > > vague.
> > > >
> > > > Does this correspond to anything in a data sheet or manual?
> > >
> > > Yes, it is configuration data described in chapter 6.2. b of the
> > > datasheet:
> > > https://drive.google.com/folderview?id=0BxCVOQS3ZymGfmJyY2RKbE5XbVlKN
> > > lktVTlwV0lxNEdxd2dzeWZER094cmJPVnMxN1F0Yzg&usp=sharing.
> > > This includes things like x/y resolution, maximum touch numbers
> > > supported,
> > > interrupt flags, various sensitivity factors.
> > >
> > > I should have included a link to the datasheet in the commit message
> > > - will do that in v2 for all patches.
> > >
> > > I did consider writing this as firmware, but it seems that some
> > > Goodix touchscreens have a
> > > real firmware they need to write in addition to this configuration
> > > data.
> > > If there is a better way to do this, please let me know and I will
> > > change it.
> >
> > I would at least expect an excerpt from an ACPI DSDT that would make
> > use of that feature.
>
> Ok, I will add this to the commit message.
No, it really shoudl be done via request_firmware() mechanism. There are
drivers in kernel that use request_firmware() for both firmware and
configuration data (see elan_i2c, elants_i2c, atmel_mxt_ts and I am sure
there are others).
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-06-05 16:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 12:47 [PATCH 0/9] Goodix touchscreen enhancements Irina Tirdea
2015-05-28 12:47 ` [PATCH 1/9] input: goodix: fix alignment issues Irina Tirdea
2015-06-04 12:48 ` Bastien Nocera
2015-06-05 16:49 ` Dmitry Torokhov
2015-06-05 17:07 ` Tirdea, Irina
2015-06-05 17:17 ` Joe Perches
2015-06-05 17:31 ` Dmitry Torokhov
2015-05-28 12:47 ` [PATCH 2/9] input: goodix: fix variable length array warning Irina Tirdea
2015-05-28 15:57 ` Antonio Ospite
2015-06-03 10:26 ` Tirdea, Irina
2015-06-03 20:49 ` Antonio Ospite
2015-06-05 16:34 ` Tirdea, Irina
2015-06-05 16:40 ` Dmitry Torokhov
2015-06-05 17:00 ` Tirdea, Irina
2015-06-05 17:11 ` Dmitry Torokhov
2015-06-05 17:34 ` Tirdea, Irina
2015-05-28 12:47 ` [PATCH 3/9] input: goodix: export id and version read from device Irina Tirdea
2015-05-28 12:47 ` [PATCH 4/9] input: goodix: add ACPI IDs for GT911 and GT9271 Irina Tirdea
2015-06-04 12:51 ` Bastien Nocera
2015-06-05 16:36 ` Tirdea, Irina
2015-06-05 16:41 ` Dmitry Torokhov
2015-06-05 17:01 ` Tirdea, Irina
2015-05-28 12:47 ` [PATCH 5/9] input: goodix: reset device at init Irina Tirdea
[not found] ` <1432817265-23891-6-git-send-email-irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-05-28 13:19 ` Mark Rutland
2015-05-28 13:42 ` Tirdea, Irina
2015-05-28 12:47 ` [PATCH 6/9] input: goodix: write configuration data to device Irina Tirdea
2015-05-28 13:21 ` Mark Rutland
2015-05-28 13:51 ` Tirdea, Irina
2015-06-04 12:55 ` Bastien Nocera
2015-06-05 16:36 ` Tirdea, Irina
2015-06-05 16:43 ` Dmitry Torokhov [this message]
2015-06-05 17:05 ` Tirdea, Irina
2015-05-28 12:47 ` [PATCH 7/9] input: goodix: add power management support Irina Tirdea
2015-06-04 13:01 ` Bastien Nocera
2015-06-05 16:42 ` Tirdea, Irina
[not found] ` <1432817265-23891-1-git-send-email-irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-05-28 12:47 ` [PATCH 8/9] input: goodix: add support for ESD Irina Tirdea
[not found] ` <1432817265-23891-9-git-send-email-irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-05-28 13:23 ` Mark Rutland
2015-05-28 14:26 ` Tirdea, Irina
2015-06-04 12:57 ` Bastien Nocera
2015-06-05 16:37 ` Tirdea, Irina
2015-06-05 16:46 ` Dmitry Torokhov
2015-06-08 14:28 ` Tirdea, Irina
2015-07-30 12:06 ` Tirdea, Irina
2015-05-28 12:47 ` [PATCH 9/9] input: goodix: use goodix_i2c_write_u8 instead of i2c_master_send Irina Tirdea
2015-06-04 13:04 ` [PATCH 0/9] Goodix touchscreen enhancements Bastien Nocera
2015-06-05 16:36 ` Tirdea, Irina
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=20150605164326.GC26708@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hadess@hadess.net \
--cc=irina.tirdea@intel.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=octavian.purdila@intel.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).