Hello Nick,
On 09/02/2014 03:46 PM, Nick Dyer wrote:
On 27/08/14 15:22, Javier Martinez Canillas wrote:
If there was a BTN_NONE or KEY_UNUSED it would had been better but I think
that making a distinction between these two cases (reserved pin vs GPIO
available but not used) is useful.
Maybe
On 27/08/14 15:22, Javier Martinez Canillas wrote:
If there was a BTN_NONE or KEY_UNUSED it would had been better but I think
that making a distinction between these two cases (reserved pin vs GPIO
available but not used) is useful.
Maybe Nick can comment here.
Yes, this is probably useful
Hello Andreas,
On 08/27/2014 12:53 AM, Andreas Färber wrote:
+hsi2c_8 {
+status = okay;
+clock-frequency = 333000;
+
+trackpad@4b {
+compatible=atmel,maxtouch;
+reg=0x4b;
+interrupt-parent=gpx1;
+interrupts=1
Hi Javier,
Am 27.08.2014 09:13, schrieb Javier Martinez Canillas:
On 08/27/2014 12:53 AM, Andreas Färber wrote:
+hsi2c_8 {
+ status = okay;
+ clock-frequency = 333000;
+
+ trackpad@4b {
+ compatible=atmel,maxtouch;
+ reg=0x4b;
+
Hello Andreas,
On 08/27/2014 03:11 PM, Andreas Färber wrote:
Hi Javier,
+ trackpad@4b {
+ compatible = atmel,maxtouch;
+ reg = 0x4b;
+ interrupt-parent = gpx1;
+ interrupts = 2 IRQ_TYPE_NONE;
+ pinctrl-names = default;
+
From: Sjoerd Simons sjoerd.sim...@collabora.co.uk
The Peach Pit board has an Atmel maXTouch trackpad device.
Add the needed Device Tree nodes to support it.
This Device Tree change is based on the Chrome OS 3.8 tree
but adapted to use the mainline Atmel maXTouch DT binding.
Signed-off-by:
Hi Javier,
Am 26.08.2014 17:28, schrieb Javier Martinez Canillas:
From: Sjoerd Simons sjoerd.sim...@collabora.co.uk
The Peach Pit board has an Atmel maXTouch trackpad device.
Add the needed Device Tree nodes to support it.
This Device Tree change is based on the Chrome OS 3.8 tree
but
