<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/input/touchscreen/eeti_ts.c, branch linux-5.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2018-07-04T16:08:05Z</updated>
<entry>
<title>Input: eeti - fix link to documentation and email address in header</title>
<updated>2018-07-04T16:08:05Z</updated>
<author>
<name>Daniel Mack</name>
<email>daniel@zonque.org</email>
</author>
<published>2018-07-04T15:46:55Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=fd8135b6f80a4d2ea2e398fb33e38ec255037111'/>
<id>urn:sha1:fd8135b6f80a4d2ea2e398fb33e38ec255037111</id>
<content type='text'>
Keep the documentation link up-to-date in case anybody need to dive into it
again, and update email address while at it.

Signed-off-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</content>
</entry>
<entry>
<title>Input: eeti - drop module parameters, parse DT properties</title>
<updated>2018-07-04T16:08:01Z</updated>
<author>
<name>Daniel Mack</name>
<email>daniel@zonque.org</email>
</author>
<published>2018-07-04T15:46:22Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a114cbd00afe7afa3a6403fb025632ba6b47b443'/>
<id>urn:sha1:a114cbd00afe7afa3a6403fb025632ba6b47b443</id>
<content type='text'>
The only user of this driver in mainline does not make use of the module
parameters, so let's remove them. All properties for this driver should be
set through DT or pdata.

Use touchscreen_parse_properties() to automatically set some of the common
touchscreen properties and derive the axis inversion through that.

And finally, use touchscreen_report_pos() to handle the DT properties
automatically instead of doing the inversion ourselves.

Signed-off-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</content>
</entry>
<entry>
<title>Input: eeti - add device tree matching table</title>
<updated>2018-07-04T16:07:56Z</updated>
<author>
<name>Daniel Mack</name>
<email>daniel@zonque.org</email>
</author>
<published>2018-07-04T15:45:47Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=e32d7f1b246c1aef7b2d4f9fe0ce8863ac21128c'/>
<id>urn:sha1:e32d7f1b246c1aef7b2d4f9fe0ce8863ac21128c</id>
<content type='text'>
Provide a match table so that the driver can be used in devicetree setups.
More properties are added in a later patch.

Signed-off-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</content>
</entry>
<entry>
<title>Input: eeti_ts - switch to gpiod API</title>
<updated>2017-04-05T15:52:33Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2017-02-20T01:21:56Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d99caa472c0a28dc95dd9b98c30ee46f9755181f'/>
<id>urn:sha1:d99caa472c0a28dc95dd9b98c30ee46f9755181f</id>
<content type='text'>
gpiod API allows standard way of specifying GPIO polarity and takes it into
account when reading or setting GPIO state. It also allows us to switch to
common way of obtaining GPIO descriptor and away form legacy platform data.

Reviewed-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: eeti_ts - expect platform code to set interrupt trigger</title>
<updated>2017-04-05T15:52:13Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2017-02-20T00:22:13Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d422be5f62ef7986d00afa4cd31eda5534ab7991'/>
<id>urn:sha1:d422be5f62ef7986d00afa4cd31eda5534ab7991</id>
<content type='text'>
Instead of keying interrupt trigger off GPIO polarity, let's rely on
platform code to set it up properly for us.

Reviewed-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: eeti_ts - switch to using threaded interrupt</title>
<updated>2017-04-03T23:24:34Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2017-02-20T01:23:47Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=0378008a99243fc492e7f0c3aabfeee69a78398c'/>
<id>urn:sha1:0378008a99243fc492e7f0c3aabfeee69a78398c</id>
<content type='text'>
Instead of having standard interrupt handler and manually firing work item
to perform I2C reads, let's switch to threaded interrupts, which were
designed specifically for this purpose.

Reviewed-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</content>
</entry>
<entry>
<title>Input: eeti_ts - use gpio_get_value_cansleep</title>
<updated>2017-04-03T23:24:33Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2017-02-21T07:13:45Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=173e4d81f76c948acbb49f3900f3ca3f279c5c2a'/>
<id>urn:sha1:173e4d81f76c948acbb49f3900f3ca3f279c5c2a</id>
<content type='text'>
We are reading GPIO state in a non-atomic context (workqueue), so we can
use "cansleep" variant, and thus make the driver available on systems where
GPIO controllers require sleeping when reading GPIO state.

Reviewed-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</content>
</entry>
<entry>
<title>Input: eeti_ts - respect interrupt set in client structure</title>
<updated>2017-04-03T23:24:33Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2017-02-20T01:14:33Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=2d3884998945cf3f995e9c2e0f157b59f4ec3e86'/>
<id>urn:sha1:2d3884998945cf3f995e9c2e0f157b59f4ec3e86</id>
<content type='text'>
Instead of expecting that GPIO is always interrupt source, let's use
interrupt specified in I2C client.

Reviewed-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</content>
</entry>
<entry>
<title>Input: eeti_ts - switch to using managed resources</title>
<updated>2017-04-03T23:24:32Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2017-02-17T23:54:22Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6f9fab69a21d47ac68e78a8a5c613a2a6156bbb7'/>
<id>urn:sha1:6f9fab69a21d47ac68e78a8a5c613a2a6156bbb7</id>
<content type='text'>
Using devm_* APIs simpifies error handling and device teardown.

Reviewed-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</content>
</entry>
<entry>
<title>Input: eeti_ts - use input_set_capability()</title>
<updated>2017-04-03T23:24:32Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2017-02-21T05:53:51Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=42e02a6a0db5499d036ff05710fe7370f9a8683a'/>
<id>urn:sha1:42e02a6a0db5499d036ff05710fe7370f9a8683a</id>
<content type='text'>
Use input_set_capability() instead of manipulating evbit/keybit
masks directly.

Reviewed-by: Daniel Mack &lt;daniel@zonque.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</content>
</entry>
</feed>
