<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/input/touchscreen/ili210x.c, branch dev-5.8</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.8</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.8'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2020-02-10T18:00:22+00:00</updated>
<entry>
<title>Input: ili210x - add ili2120 support</title>
<updated>2020-02-10T18:00:22+00:00</updated>
<author>
<name>Luca Weiss</name>
<email>luca@z3ntu.xyz</email>
</author>
<published>2020-02-09T22:43:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=d0c5e7d4f5e5b76eeb53d098157d5b1f62ebb407'/>
<id>urn:sha1:d0c5e7d4f5e5b76eeb53d098157d5b1f62ebb407</id>
<content type='text'>
This adds support for the Ilitek ili2120 touchscreen found in the
Fairphone 2 smartphone.

Signed-off-by: Luca Weiss &lt;luca@z3ntu.xyz&gt;
Link: https://lore.kernel.org/r/20200209151904.661210-1-luca@z3ntu.xyz
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - fix return value of is_visible function</title>
<updated>2020-02-10T18:00:01+00:00</updated>
<author>
<name>Luca Weiss</name>
<email>luca@z3ntu.xyz</email>
</author>
<published>2020-02-09T22:42:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=fbd1ec000213c8b457dd4fb15b6de9ba02ec5482'/>
<id>urn:sha1:fbd1ec000213c8b457dd4fb15b6de9ba02ec5482</id>
<content type='text'>
The is_visible function expects the permissions associated with an
attribute of the sysfs group or 0 if an attribute is not visible.

Change the code to return the attribute permissions when the attribute
should be visible which resolves the warning:

  Attribute calibrate: Invalid permissions 01

Fixes: cc12ba1872c6 ("Input: ili210x - optionally show calibrate sysfs attribute")
Signed-off-by: Luca Weiss &lt;luca@z3ntu.xyz&gt;
Reviewed-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt;
Link: https://lore.kernel.org/r/20200209145628.649409-1-luca@z3ntu.xyz
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - optionally show calibrate sysfs attribute</title>
<updated>2019-11-12T23:53:33+00:00</updated>
<author>
<name>Sven Van Asbroeck</name>
<email>thesven73@gmail.com</email>
</author>
<published>2019-11-12T23:44:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=cc12ba1872c6bf05b5f177fae5082bcbea335f2b'/>
<id>urn:sha1:cc12ba1872c6bf05b5f177fae5082bcbea335f2b</id>
<content type='text'>
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.

Signed-off-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt;
Link: https://lore.kernel.org/r/20191112210148.3535-2-TheSven73@gmail.com
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - add resolution to chip operations structure</title>
<updated>2019-11-12T23:53:32+00:00</updated>
<author>
<name>Sven Van Asbroeck</name>
<email>thesven73@gmail.com</email>
</author>
<published>2019-11-12T23:40:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=b32fbeaec52d387004dd7fa15877b8adf7b396c3'/>
<id>urn:sha1:b32fbeaec52d387004dd7fa15877b8adf7b396c3</id>
<content type='text'>
Optionally allow the touch screen resolution to be set by adding
it to the chip operations structure. If it is omitted (left zero),
the resolution defaults to 64K. Which is the previously hard-coded
value.

Set the ili2117 resolution to 2048, as indicated in its datasheet.

Signed-off-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt;
Link: https://lore.kernel.org/r/20191112210148.3535-1-TheSven73@gmail.com
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - do not retrieve/print chip firmware version</title>
<updated>2019-11-12T23:53:30+00:00</updated>
<author>
<name>Sven Van Asbroeck</name>
<email>thesven73@gmail.com</email>
</author>
<published>2019-11-12T23:40:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c7dded5b2980de9811f47a1a576e0596a5a775ce'/>
<id>urn:sha1:c7dded5b2980de9811f47a1a576e0596a5a775ce</id>
<content type='text'>
The driver's method to retrieve the firmware version on ili2117/
ili2118 chip flavours is incorrect. The firmware version register
address and layout are wrong.

The firmware version is not actually used anywhere inside or
outside this driver. There is a dev_dbg() print, but that is
only visible when the developer explicitly compiles in debug
support.

Don't make the code more complicated to preserve a feature that
no-one is using. Remove all code associated with chip firmware
version.

Signed-off-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt;
Link: https://lore.kernel.org/r/20191112164429.11225-1-TheSven73@gmail.com
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - remove unneeded suspend and resume handlers</title>
<updated>2019-11-12T00:12:26+00:00</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2019-11-04T23:30:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=a5fdf7d02656e71071d1a13ab887f94e58651baf'/>
<id>urn:sha1:a5fdf7d02656e71071d1a13ab887f94e58651baf</id>
<content type='text'>
When I2C client is instantiated with I2C_CLIENT_WAKE flag (either via
"wakeup-source" device property, or via board info flag), it will mark the
main IRQ line as wakeup IRQ, which will ensure that it will be enabled for
wakeup when system transitions to suspend state. Since our suspend/resume
handlers were only managing IRQ wakeup state, they are no longer needed,
and can be removed.

Tested-by: Adam Ford &lt;aford173@gmail.com&gt; #imx6q-logicpd
Tested-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt; # ILI2118A variant
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - do not unconditionally mark touchscreen as wakeup source</title>
<updated>2019-11-12T00:12:19+00:00</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2019-11-04T23:27:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=172bb5f34c0dd5e94eb877edb3e8721d1ebd5c75'/>
<id>urn:sha1:172bb5f34c0dd5e94eb877edb3e8721d1ebd5c75</id>
<content type='text'>
I2C devices that are supposed to be wakeup sources should be instantiated
with I2C_CLIENT_WAKE flag (which can be either set by in board info, or
retrieved from "wakeup-source" property); individual drivers should not be
marking devices as wakeup sources unconditionally.

Tested-by: Adam Ford &lt;aford173@gmail.com&gt; #imx6q-logicpd
Tested-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt; # ILI2118A variant
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - define and use chip operations structure</title>
<updated>2019-11-12T00:12:13+00:00</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2019-02-07T06:33:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=ef536abd3afd1e3cbddf04c724db793f12ab9c44'/>
<id>urn:sha1:ef536abd3afd1e3cbddf04c724db793f12ab9c44</id>
<content type='text'>
Instead of doing if/else if/else on the chip's model number let's define
chip operations structure and use it to perform indirect calls. With number
of protocols supported by the driver growing, this makes it better
maintainable.

This change includes fixes to checks whether the driver should continue
polling the controller by Sven Van Asbroeck &lt;thesven73@gmail.com&gt;.

Tested-by: Adam Ford &lt;aford173@gmail.com&gt; #imx6q-logicpd
Tested-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt; # ILI2118A variant
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - do not set parent device explicitly</title>
<updated>2019-11-12T00:12:01+00:00</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2019-11-04T23:20:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=efda86a49553bc7e44b3f7254208577bff2da932'/>
<id>urn:sha1:efda86a49553bc7e44b3f7254208577bff2da932</id>
<content type='text'>
We are using devm_input_allocate_device() that set's up the parent for
us, no need to do it ourselves.

Tested-by: Adam Ford &lt;aford173@gmail.com&gt; #imx6q-logicpd
Tested-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt; # ILI2118A variant
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
<entry>
<title>Input: ili210x - handle errors from input_mt_init_slots()</title>
<updated>2019-11-12T00:11:53+00:00</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2019-11-04T18:39:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=43f06a4c639de8ee89fc348a9a3ecd70320a04dd'/>
<id>urn:sha1:43f06a4c639de8ee89fc348a9a3ecd70320a04dd</id>
<content type='text'>
input_mt_init_slots() may fail and we need to handle such failures.

Tested-by: Adam Ford &lt;aford173@gmail.com&gt; #imx6q-logicpd
Tested-by: Sven Van Asbroeck &lt;TheSven73@gmail.com&gt; # ILI2118A variant
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
</feed>
