linux-toradex.git, branch Colibri_T30_LinuxImageV2.1Beta2_20140206 Linux kernel for Apalis and Colibri modules video: tegra: check if framebuffer is registred 2014-02-06T17:16:02+00:00 Stefan Agner stefan.agner@toradex.com 2014-02-06T17:14:35+00:00 098fb4efc843772a3f1e5695742dd1ca02e27960 Before updating modes on HDMI hotplug, check if framebuffer is registered at all. This allows to disable framebuffers completely. 
Before updating modes on HDMI hotplug, check if framebuffer is
registered at all. This allows to disable framebuffers completely.
input: touchscreen: fusion: platform independent GPIO description 2014-02-04T09:46:13+00:00 Stefan Agner stefan.agner@toradex.com 2014-02-04T09:46:13+00:00 c300f3a605f8984449c1a5324fd3edda6f2fd8ff Use platform independent description for requested GPIOs. 
Use platform independent description for requested GPIOs.
apalis_t30: add Fusion touchscreen driver 2014-02-04T09:37:42+00:00 Stefan Agner stefan.agner@toradex.com 2014-02-04T09:37:42+00:00 54d1c20e1b2486164a7afab44fd6dff37b1b38f3 Activate Fusion touchscreen driver. Use GPIO 5/6 as pen down/reset GPIO and provide a helper function to free the GPIO before the driver requests them. 
Activate Fusion touchscreen driver. Use GPIO 5/6 as pen down/reset
GPIO and provide a helper function to free the GPIO before the
driver requests them.
Merge branch 'fusion-touchscreen' into colibri 2014-01-29T14:43:28+00:00 Stefan Agner stefan.agner@toradex.com 2014-01-29T14:43:28+00:00 81465d86db70e169edb1dc59b0d6bc7a34cd13c7 






colibri_t20/colibri_t30: use new platform data for fusion touchscreen
2014-01-29T14:41:41+00:00

Stefan Agner
stefan.agner@toradex.com

2014-01-27T13:34:11+00:00

485b5d108fcf75a1066c5de054f8adf2e6118845

Fusion touchscreen driver now uses platform data to do GPIO
initialization by itself. Make use of this by providing GPIO numbers
instead of doing initialization in the board initialization.





Fusion touchscreen driver now uses platform data to do GPIO
initialization by itself. Make use of this by providing GPIO numbers
instead of doing initialization in the board initialization.







input: touchscreen: fusion: fix error handling
2014-01-29T14:41:41+00:00

Stefan Agner
stefan.agner@toradex.com

2014-01-27T09:06:22+00:00

63b293000723e61a880470f093fbe82e86ebd81b

Fix chip reset by sleeping long enought after reset. Do proper error
handling (free GPIO on failure). Use dev_* for message logging to get
similar messages for all fusion driver related errors and warnings.





Fix chip reset by sleeping long enought after reset. Do proper error
handling (free GPIO on failure). Use dev_* for message logging to get
similar messages for all fusion driver related errors and warnings.







input: touchscreen: fusion: use new I2C PM functions
2014-01-29T14:41:41+00:00

Stefan Agner
stefan.agner@toradex.com

2014-01-27T09:17:08+00:00

9d996316a470d37fb71c521f27106b014f3f0b23

To avoid warnings use the new I2C power management function for
suspend and resume.





To avoid warnings use the new I2C power management function for
suspend and resume.







input: touchscreen: added platform data for Fusion touchscreen
2014-01-29T14:41:41+00:00

Stefan Agner
stefan.agner@toradex.com

2014-01-24T16:29:43+00:00

cb82730b70f31af3b43041ac4e47de69c18016c9

Added platform data struct to define interrupt and reset GPIO. This
allows to initialize the touchscreen controller inside the driver
rather then in each platform and use the driver as a module.





Added platform data struct to define interrupt and reset GPIO. This
allows to initialize the touchscreen controller inside the driver
rather then in each platform and use the driver as a module.







input: touchscreen: fix race condition in Fusion driver
2014-01-29T14:41:41+00:00

Stefan Agner
stefan.agner@toradex.com

2014-01-21T13:12:33+00:00

e95019a4f20b8cdfbe03658e4f73b69cdcf97540

When the next interrupt request apeares between the confirmation of
the previous (a write via I2C, fusion_F0710A_write_complete) and
the reenable of the GPIO interrupt, the driver hangs and no more
touch inputs are reported.

This patch moves the confirmation after the reenabling of the GPIO
interrupt.





When the next interrupt request apeares between the confirmation of
the previous (a write via I2C, fusion_F0710A_write_complete) and
the reenable of the GPIO interrupt, the driver hangs and no more
touch inputs are reported.

This patch moves the confirmation after the reenabling of the GPIO
interrupt.







input: touchscreen: add ABS_X/ABS_Y axis for Fusion touchscreen
2014-01-29T14:41:41+00:00

Stefan Agner
stefan.agner@toradex.com

2014-01-21T09:28:47+00:00

dda7a631ac901e4d140e8a6612c5c6b5506b6a91

Recent evdev X-Server input driver implementation complain when
only multitouch axes have been reported ("found only multitouch-axes.
That shouldn't happen."). Therefor also report the primary touch
detection with default axis.





Recent evdev X-Server input driver implementation complain when
only multitouch axes have been reported ("found only multitouch-axes.
That shouldn't happen."). Therefor also report the primary touch
detection with default axis.