Hi,
On 27-08-15 17:00, Alexis Jeandet wrote:
Hi,
I saw in drivers/input/touchscreen/sun4i-ts.c that A20 have a similar TC
controller but at the end:
===========================================
static const struct of_device_id sun4i_ts_of_match[] = {
{ .compatible = "allwinner,sun4i-a10-ts", },
{ .compatible = "allwinner,sun5i-a13-ts", },
{ .compatible = "allwinner,sun6i-a31-ts", },
{ /* sentinel */ }
};
===========================================
Does that means that I can't load it on A20, is there any hack to use it on
A20, then is there any dts entry to add, I'm quite lost?
arch/arm/boot/dts/sun7i-a20.dtsi already has an entry for it:
rtp: rtp@01c25000 {
compatible = "allwinner,sun5i-a13-ts";
reg = <0x01c25000 0x100>;
interrupts = <GIC_SPI 29 IRQ_TYPE_LEVEL_HIGH>;
#thermal-sensor-cells = <0>;
};
Note that this is for *resisitive* touchscreens only, capacative
touchscreens always come with their own controller on A20
based devices.
If you've a resistive touchscreen read:
Documentation/devicetree/bindings/input/touchscreen/sun4i.txt
Specifically at a minimum you will need to set allwinner,ts-attached
in the rtp node:
&rtp {
allwinner,ts-attached;
};
The touchscreen controller is always enabled since it contains the
only thermal sensor in the SoC, allwinner,ts-attached actually makes
it read the resisitive touchscreen pins and register itself as an
input device.
Regards,
Hans
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
