hi all:
I try to cat hid events through debugfs but in vain.
My environment is:
1. kernel 3.10.30
2. insert below kos
usbhid
hid_generic
hid
evdev
usb_storage
ehci_hcd
xhci_hcd
usbcore
usb_common
3. mount debugfs as below
#mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatim
The core temperature sensor now supports thermal zones. Add a thermal
zone mapping for the cpus with passive cooling (cpufreq throttling).
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun4i-a10.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/a
This patch adds the regulator nodes for the axp209 by including
the axp209 dtsi. As the inputs of these regulators are from the
axp209's PS output, which is basically just a mux over the 2
inputs, it is considered to be unregulated. Thus we do not provide
input supply properties for them.
The regu
This patch enables TOUCHSCREEN_SUN4I and CPU_THERMAL to enable cpufreq
support with passive cpu cooling (thermal throttling) on sunxi by default.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/multi_v7_de
This patch adds the regulator nodes for the axp209 by including
the axp209 dtsi. As the inputs of these regulators are from the
axp209's PS output, which is basically just a mux over the 2
inputs, it is considered to be unregulated. Thus we do not provide
input supply properties for them.
The regu
This patch adds the regulator nodes for the axp209 by including
the axp209 dtsi. As the inputs of these regulators are from the
axp209's PS output, which is basically just a mux over the 2
inputs, it is considered to be unregulated. Thus we do not provide
input supply properties for them.
The regu
This patch adds the regulator nodes for the axp209 by including
the axp209 dtsi. As the inputs of these regulators are from the
axp209's PS output, which is basically just a mux over the 2
inputs, it is considered to be unregulated. Thus we do not provide
input supply properties for them.
The regu
This patch enables TOUCHSCREEN_SUN4I, CPUFREQ_DT, and CPU_THERMAL to
enable cpufreq support with passive cpu cooling (thermal throttling)
by default.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/configs/sunxi_defconfig | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/ar
The core temperature sensor now supports thermal zones. Add a thermal
zone mapping for the cpus with passive cooling (cpufreq throttling).
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun5i-a13.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/a
The cpu core is clocked from the "cpu" clock. Add a reference to it
in the first cpu node. Also add "cpu0" label to the node.
The operating points were taken from the A10 FEX files in the
sunxi-boards repository. All FEX files have the same settings.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boo
On sun[45678]i, we have one cluster of identical cores sharing a
clock, which is ideal for using cpufreq-dt. Register a platform
device for cpufreq-dt.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/mach-sunxi/sunxi.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/mach-sunxi/
The AXP209 PMIC is used with some Allwinner SoCs. This patch adds
a dtsi file listing all the regulator nodes. The regulators are
initialized based on their device node names.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/axp209.dtsi | 87 +++
1 file c
The cpu core is clocked from the "cpu" clock. Add a reference to it
in the first cpu node. Also add "cpu0" label to the node.
The operating points were taken from the A20 FEX files in the
sunxi-boards repository. Not all boards have the same settings. The
settings in this patch are the most generi
The cpu core is clocked from the "cpu" clock. Add a reference to it
in the first cpu node. Also add "cpu0" label to the node.
The operating points were taken from the A13 FEX files in the
sunxi-boards repository. All FEX files have the same settings.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boo
Now that the resistive touchpanel driver supports thermal sensors,
add the "#thermal-sensor-cells" property as required by the thermal
framework.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun4i-a10.dtsi | 1 +
arch/arm/boot/dts/sun5i-a10s.dtsi | 1 +
arch/arm/boot/dts/sun5i-a13.dtsi |
Hi everyone,
This series adds support cpufreq support for sun[457]i using cpufreq-dt.
This also supports passive cpu cooling (thermal throttling) using thermal
zones with the temperature sensor in the SoC.
The operating points for the supported platforms were taken from the
linux-sunxi FEX files
The touchscreen controller has a temperature sensor embedded in the SoC,
which already has hwmon support in the driver.
Add DT thermal zone support so we can use it with cpufreq for thermal
throttling.
Signed-off-by: Chen-Yu Tsai
---
.../bindings/input/touchscreen/sun4i.txt | 1 +
dr
The cpu clock on sunxi machines is just a mux clock, which is normally
fed by the main PLL, but can be muxed to the main or low power oscillator.
Make the mux clock propagate rate changes to its parent, so we can
change the clock rate of the PLL, and thus actually implement rate
changing on the cp
The core temperature sensor now supports thermal zones. Add a thermal
zone mapping for the cpus with passive cooling (cpufreq throttling).
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun7i-a20.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/a
On Mon, Jan 5, 2015 at 1:32 PM, Benjamin Tissoires
wrote:
> Bamboo Pads are using the generic processing but their report descriptors
> differ from the ISDv* line. The pen fields are marked with the .physical
> as Digitizer_Pen, which makes also sense.
>
> Add this field to the checks and enable f
The pressure values retrieved from secondary packets was incorrectly
shifted, making them lower than what they actually were.
Since this only happened with secondary packets, the values reported
when only one finger was present on the touchpad were correct.
Signed-off-by: Gabriele Mazzotta
---
d
The minimum value these sensors can report is 4, so this should be the
value used when W is not reporting the width.
Signed-off-by: Gabriele Mazzotta
---
drivers/input/mouse/synaptics.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/mouse/synaptics.c b/drivers/
Despite claiming to report finger widths, semi-mt touchpads were not
doing it. Make them report widths using ABS_MT_TOUCH_MAJOR instead
of ABS_TOOL_WIDTH.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=77161
Signed-off-by: Gabriele Mazzotta
---
drivers/input/mouse/synaptics.c | 11 +--
Make image sensors and cr48 sensors report widths and fix the
calculation of width and pressure values in some cases.
Changes since v1:
- Rebased on 35393dcb2ed3
- Get widths from AGM packets too
- Include support for cr48 sensors
- Fix pressure values on image sensors
Gabriele Mazzotta (4):
When multiple fingers are on the touchpad, W reports the finger
count rather than the width. Retrieve the correct value that is
encoded in X, Y and Z of AGM and SGM packets.
The minimum width reported is 8 rather than 4 in this case, while the
maximum remains 15.
Signed-off-by: Gabriele Mazzotta
On Mon, Jan 5, 2015 at 5:00 PM, Gabriele Mazzotta
wrote:
> On Monday 05 January 2015 14:24:30 Benjamin Tissoires wrote:
>> Hi Gabriele,
>>
>> [Adding Peter and Hans as this change will impact both
>> xf86-input-synaptics and libinput]
>>
>> On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
>> wr
On Monday 05 January 2015 14:24:30 Benjamin Tissoires wrote:
> Hi Gabriele,
>
> [Adding Peter and Hans as this change will impact both
> xf86-input-synaptics and libinput]
>
> On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
> wrote:
> > Despite claiming to be able to report ABS_TOOL_WIDTH, im
Bamboo Pads are using the generic processing but their report descriptors
differ from the ISDv* line. The pen fields are marked with the .physical
as Digitizer_Pen, which makes also sense.
Add this field to the checks and enable for free Bamboo Pads.
Reported-by: Josep Sanchez Ferreres
Signed-of
We introduced nice macros in wacom_wac.c to check whether a field is
a pen or a touch one.
wacom_usage_mapping() still uses it's own tests, which are not in sync with
the wacom_wac tests (.application is not checked).
That means that some legitimate fields might be filtered out from the
usage map
Hi Josep,
On Mon, Dec 8, 2014 at 5:04 PM, Benjamin Tissoires
wrote:
> Thanks for the logs (both way arrived in my mailbox, attached file or
> pastebin).
>
> I'll try to have a look at them on Wednesday.
Actually, it's nearly been a month. Thanks for the reminder. (However,
it's easier to track
On Monday 05 January 2015 21:13:09 Gabriele Mazzotta wrote:
> On Monday 05 January 2015 14:24:30 Benjamin Tissoires wrote:
> > Hi Gabriele,
> >
> > [Adding Peter and Hans as this change will impact both
> > xf86-input-synaptics and libinput]
> >
> > On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzo
On Monday 05 January 2015 14:24:30 Benjamin Tissoires wrote:
> Hi Gabriele,
>
> [Adding Peter and Hans as this change will impact both
> xf86-input-synaptics and libinput]
>
> On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
> wrote:
> > Despite claiming to be able to report ABS_TOOL_WIDTH, im
On Mon, Jan 5, 2015 at 2:15 PM, Gabriele Mazzotta
wrote:
> On Monday 05 January 2015 11:04:07 Dmitry Torokhov wrote:
>> On January 5, 2015 10:42:13 AM PST, Benjamin Tissoires
>> wrote:
>> >On Mon, Jan 5, 2015 at 1:37 PM, Gabriele Mazzotta
>> > wrote:
>> >> On Monday 05 January 2015 13:25:38 Benj
Hi Gabriele,
[Adding Peter and Hans as this change will impact both
xf86-input-synaptics and libinput]
On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
wrote:
> Despite claiming to be able to report ABS_TOOL_WIDTH, image sensors
> were not doing it. Make them report widths and use ABS_MT_TOUCH
On Monday 05 January 2015 11:04:07 Dmitry Torokhov wrote:
> On January 5, 2015 10:42:13 AM PST, Benjamin Tissoires
> wrote:
> >On Mon, Jan 5, 2015 at 1:37 PM, Gabriele Mazzotta
> > wrote:
> >> On Monday 05 January 2015 13:25:38 Benjamin Tissoires wrote:
> >>> Hi Gabriele,
> >>>
> >>> On Sat, Dec
On Mon, Jan 5, 2015 at 2:04 PM, Dmitry Torokhov
wrote:
> On January 5, 2015 10:42:13 AM PST, Benjamin Tissoires
> wrote:
>>On Mon, Jan 5, 2015 at 1:37 PM, Gabriele Mazzotta
>> wrote:
>>> On Monday 05 January 2015 13:25:38 Benjamin Tissoires wrote:
Hi Gabriele,
On Sat, Dec 27, 2014
On January 5, 2015 10:42:13 AM PST, Benjamin Tissoires
wrote:
>On Mon, Jan 5, 2015 at 1:37 PM, Gabriele Mazzotta
> wrote:
>> On Monday 05 January 2015 13:25:38 Benjamin Tissoires wrote:
>>> Hi Gabriele,
>>>
>>> On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
>>> wrote:
>>> > When two or more
On Mon, Jan 5, 2015 at 1:37 PM, Gabriele Mazzotta
wrote:
> On Monday 05 January 2015 13:25:38 Benjamin Tissoires wrote:
>> Hi Gabriele,
>>
>> On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
>> wrote:
>> > When two or more fingers are on the touchpad, the 'w' slot holds the
>> > finger count ra
On Monday 05 January 2015 13:25:38 Benjamin Tissoires wrote:
> Hi Gabriele,
>
> On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
> wrote:
> > When two or more fingers are on the touchpad, the 'w' slot holds the
> > finger count rather than the width. Retrieve the correct value encoded
> > in th
Hi Gabriele,
On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
wrote:
> When two or more fingers are on the touchpad, the 'w' slot holds the
> finger count rather than the width. Retrieve the correct value encoded
> in the lower bits of 'x', 'y' and 'z'.
>
> The minimum width reported is 8 rathe
From: Anshul Garg
As input_pass_values function is called everytime when EV_SYN is sent
from input driver or input event buffer becomes full.
So in case of regular handler event filter code should not run so added
check whether handler supports filter or not.
Signed-off-by: Anshul Garg
---
dri
From: Anshul Garg
As input_pass_values function is called everytime when EV_SYN is sent
from input driver or input event buffer becomes full. So avoid running
auto repeat code if input device doesn't support EV_KEY and EV_REP
event type.
Signed-off-by: Anshul Garg
---
drivers/input/input.c |
Dear Mr Dimtry ,
Thanks for the suggestions.
I will send you the updated patch soon.
On Mon, Jan 5, 2015 at 4:27 AM, Dmitry Torokhov
wrote:
> On Tue, Dec 30, 2014 at 11:19:53AM +0530, anshu...@samsung.com wrote:
>> From: Anshul Garg
>>
>> As input_pass_values function is called everytime when
On Dec 29 2014 or thereabouts, Dmitry Torokhov wrote:
> Instead of having various protocols provide _supported()
> functions, let's use IS_ENABLED() macro that works well in "if" statements.
>
> Signed-off-by: Dmitry Torokhov
> ---
Reviewed-by: Benjamin Tissoires
Cheers,
Benjamin
> drivers/i
On Dec 29 2014 or thereabouts, Dmitry Torokhov wrote:
> According to Synaptics devices with ForcePads use SYN300D and SYN3014 as
> PNP IDs, so let's switch from DMI-bases detection scheme to PNP-based
> one, which should be more reliable.
>
> Suggested-by: Hans de Goede
> Signed-off-by: Dmitry To
Hi Dmitry,
On Dec 29 2014 or thereabouts, Dmitry Torokhov wrote:
> Hi Benjamin,
>
> On Mon, Dec 08, 2014 at 01:01:28PM -0500, Benjamin Tissoires wrote:
> > On Thu, Nov 20, 2014 at 2:42 PM, Benjamin Tissoires
> > wrote:
> > > On Fri, Oct 31, 2014 at 12:51 PM, Dmitry Torokhov
> > > wrote:
> > >>
Hello Folks & Dmitry,
Further to the previous patch, here is the current version (against
mainline) updated with the DMI info of another laptop model where this
fix had helped a user.
Can you please review it & give some feedback? If it looks good as it
is, then on behalf of all affected users (i
Hi Geert,
On Thursday 18 December 2014 21:23:46 Laurent Pinchart wrote:
> On Thursday 18 December 2014 14:03:18 Geert Uytterhoeven wrote:
> > On Thu, Dec 18, 2014 at 1:49 PM, Laurent Pinchart wrote:
> > > There are three compatible strings defined for the ADXL345 and ADXL346
> > > in Documentation
48 matches
Mail list logo
