Hello Alexandre,
On Wed, Nov 19, 2014 at 05:33:42PM +0900, Alexandre Courbot wrote:
> On Mon, Nov 17, 2014 at 6:09 PM, Uwe Kleine-König
> wrote:
> > Hello,
> >
> > On Wed, Feb 13, 2013 at 04:03:00PM +0900, Alexandre Courbot wrote:
> >> From: Alexandre Courbot
> >>
> >> Constify descriptor
Add read firmware image function supported for gen5 trackpad device,
it can be used through debugfs read_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.h | 1 +
drivers/input/mouse/cyapa_gen5.c | 155 +++
Add acpi device tree supported.
acpi device id "CYAP" is for old gen3 trackpad devices.
acpi device id "CYAP0001" is for new gen5 trackpad devices.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 13 +
1 file changed, 13 insertions(+)
diff
Add read raw data function supported for gen5 trackpad device,
it can be used through debugfs raw_data interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen5.c | 138 +++
1 file changed, 138 insertions(+)
diff --git
Add read firmware image function supported for gen3 trackpad device,
it can be used through debugfs read_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 67
1 file changed, 67 insertions(+)
diff
Add read sensors' raw data from trackpad device interface supported in cyapa
driver through debugfs raw_data interface.
Through this interface, user can read difference count map of each sensors
directly from trackpad device (some customers want). And it's useful to help
users to find out the root
Add read firmware image from trackpad device interface supported in cyapa
driver through debugfs read_fw interface.
Through this interface user can read out, check and backup the firmware image
of the trackpad device before any firmware update, or can use the backed image
to do firmware image
Add force re-calibrate function supported for gen5 trackpad device,
it can be used through sysfs calibrate interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen5.c | 65
1 file changed, 65 insertions(+)
diff
Add read baseline function supported for gen5 trackpad device,
it can be used through sysfs baseline interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.h | 2 +
drivers/input/mouse/cyapa_gen5.c | 621 +++
2
Add firmware image update function supported for gen5 trackpad device,
it can be used through sysfs update_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/Kconfig | 2 +-
drivers/input/mouse/cyapa_gen5.c | 290
Add force re-calibrate function supported for gen3 trackpad device,
it can be used through sysfs calibrate interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 58
1 file changed, 58 insertions(+)
diff
Add device's basic control and features supported in cyapa driver through
sysfs file system interfaces. These interfaces are commonly used in
pre- and after production, for trackpad device state checking, managing
and firmware image updating.
These interfaces including mode, firmware_version and
Add read baseline function supported for gen3 trackpad device,
it can be used through sysfs baseline interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 71
1 file changed, 71 insertions(+)
diff --git
Add runtime_suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the runtime power
management strategy of trackpad device as their requirements.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 167
Add firmware image update function supported for gen3 trackpad device,
it can be used through sysfs update_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 284 +++
1 file changed, 284 insertions(+)
diff
Hi Mike,
On Wed, Nov 19, 2014 at 12:12 AM, Mike Turquette wrote:
> Quoting Geert Uytterhoeven (2014-11-12 06:02:29)
>> This is my first pull request from renesas-drivers.
>> If there's anything that can be improved, please let me know.
>> Thanks!
>
> Hurray for new pull requests! They simplify
This patch modified the code to fix the patch check warning issue with latest
checkpatch.sh tool, and also changed the return variable name from "ret" to
"error" when there is only one error path to follow code style.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
In order to support multiple different chipsets and communication protocols
trackpad devices in one cyapa driver, the new cyapa driver is re-designed
with one cyapa driver core and multiple device specific functions component.
The cyapa driver core is contained in this patch, it supplies basic
Add suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the power management
strategy of trackpad device as their requirements.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 105
Based on the cyapa core, add the gen5 trackpad device's basic functions
supported, so gen5 trackpad device can work with kernel input system.
And also based on the state parse interface, the cyapa driver can
automatically determine the attached is gen3 or gen5 protocol trackpad
device, then set
V11 patches have below main updates compared with v10 patches:
1) Add add acpi device id supported for old gen3 and new gen5 trackpad devices.
2) Fix the unable to update firmware issue when cyapa_open is not called
which means the irq for firwmare update process is not enabled. This fix
by
Remove cyapa_remove() method, add cyapa_open() and cyapa_close() methods for
input interface, also modified together with driver's memory and IRQ resource
allocations to support device resource management infrastructure to reduce
the mistakes of resource management.
TEST=test on Chromebooks.
On Wednesday 19 November 2014 13:35:44 Benjamin Herrenschmidt wrote:
> On Wed, 2014-11-19 at 10:39 +1100, Jeremy Kerr wrote:
> > Hi Rob,
> >
> > >> diff --git a/drivers/base/core.c b/drivers/base/core.c
> > >> index 20da3ad..8c7b607 100644
> > >> --- a/drivers/base/core.c
> > >> +++
On Mon, Nov 17, 2014 at 6:09 PM, Uwe Kleine-König
wrote:
> Hello,
>
> On Wed, Feb 13, 2013 at 04:03:00PM +0900, Alexandre Courbot wrote:
>> From: Alexandre Courbot
>>
>> Constify descriptor parameter of gpiod_* functions for those that
>> should obviously not modify it. This includes value or
Based on Arnds review comments here https://lkml.org/lkml/2014/11/13/161, update
the miphy365 phy driver to access sysconfig register offsets via syscfg dt
property.
This is because the reg property should not be mixing address spaces like it
does
currently for miphy365. This change then also
This patch adds the dt nodes for the usb2 picophy found on the stih407
device family. It is used on stih407 by the dwc3 usb3 controller when
controlling usb2/1.1 devices.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-family.dtsi | 9 +
1 file changed, 9 insertions(+)
diff
This patch adds the dt nodes for the extra usb2 picophys found on the stih410.
These two picophys are used in conjunction with the extra ehci/ohci usb
controllers also found on the stih410.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih410.dtsi | 18 ++
1 file changed,
This patch adds the DT nodes for the extra ehci and ohci usb controllers
on the stih410 SoC.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih410.dtsi | 52 ++
1 file changed, 52 insertions(+)
diff --git a/arch/arm/boot/dts/stih410.dtsi
Based on Arnds review comments here https://lkml.org/lkml/2014/11/13/161,
we should not be mixing address spaces in the reg property like this driver
currently does. This patch updates the driver, dt docs and also the existing
dt nodes to pass the sysconfig offset in the syscon dt property.
This
This patch enables the picoPHY usb phy which is used by
the usb2 and usb3 host controllers when controlling usb2/1.1
devices. It is found in stih407 family SoC's from STMicroelectronics.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file
Hi,
Following on from Arnds comments about the picophy driver here
https://lkml.org/lkml/2014/11/13/161, this series fixes the
remaining upstreamed drivers for STI, which are mixing address spaces
in the reg property. We do this in a way similar to the keystone
and bcm7445 platforms, by having
Based on Arnds review comments here https://lkml.org/lkml/2014/11/13/161, update
the phy driver to not use the reg property to access the sysconfig register
offsets.
This is because other phy's (miphy28, miphy365) have a combination of memory
mapped
registers and sysconfig control regs, and we
Hi Eduardo,
> Different drivers request API extensions in of-thermal. For this
> reason, additional callbacks are required to fit the new drivers
> needs.
>
> The current API implementation expects the registering sensor driver
> to provide a get_temp and get_trend callbacks as function
Hi
On 11/19/2014 03:09 AM, Johan Hedberg wrote:
Hi Kirill,
On Tue, Nov 18, 2014, Kirill A. Shutemov wrote:
On Fri, Nov 07, 2014 at 11:27:54AM +0200, Johan Hedberg wrote:
Chan-yeol Park (1):
Bluetooth: Fix hci_sync missing wakeup interrupt
Look like this commit causes problem for me:
On Wed, Nov 19, 2014 at 2:59 AM, Al Viro wrote:
> On Tue, Nov 18, 2014 at 03:28:03PM +0100, Miklos Szeredi wrote:
>
>> So from mainline we need two things:
>>
>> - when mounting distinguish between old and new format.
>>
>> - userspace can detect which formats are supported by the kernel.
>>
Hi All
On 11/19/2014 03:09 AM, Johan Hedberg wrote:
Hi Kirill,
On Tue, Nov 18, 2014, Kirill A. Shutemov wrote:
On Fri, Nov 07, 2014 at 11:27:54AM +0200, Johan Hedberg wrote:
Chan-yeol Park (1):
Bluetooth: Fix hci_sync missing wakeup interrupt
Look like this commit causes problem for
Hi Steve,
On Tue, 18 Nov 2014 22:33:33 -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Stack traces that happen from function tracing check if the address
> on the stack is a __kernel_text_address(). That is, is the address
> kernel code. This calls core_kernel_text() which
Hey,
On 19-11-14 07:43, Michael Marineau wrote:
> On 3.18-rc kernel's I have been intermittently experiencing GPU
> lockups shortly after startup, accompanied with one or both of the
> following errors:
>
> nouveau E[ PFIFO][:01:00.0] read fault at 0x000734a000 [PTE]
> from PBDMA0/HOST_CPU
On Wed, Nov 05, 2014 at 04:49:51PM +0200, Kirill A. Shutemov wrote:
> The patch updates Documentation/vm/transhuge.txt to reflect changes in
> THP design.
>
> Signed-off-by: Kirill A. Shutemov
> ---
> Documentation/vm/transhuge.txt | 84
> +++---
> 1 file
On Tue, Nov 18, 2014 at 11:25 PM, Joe Stringer wrote:
> On 18 November 2014 22:09, Pravin Shelar wrote:
>>
>> On Tue, Nov 18, 2014 at 10:54 AM, Joe Stringer
>> wrote:
>> > When userspace doesn't provide a mask, OVS datapath generates a fully
>> > unwildcarded mask for the flow. This is done by
Patch is from Sonny Rao
We need to claim the clock which is driving the codec so that when we enable
clock gating, we continue to clock the codec when needed. I make this an
optional clock since there might be some applications where we don't need it
but can still use the I2S block.
On 11/13/14 17:45, Javier Martinez Canillas wrote:
> Hello Kukjin,
>
Hi Javier,
> On Tue, Oct 28, 2014 at 12:06 PM, Kukjin Kim wrote:
>> Javier Martinez Canillas wrote:
>>> Commit 6e80e3d87549 ("ARM: exynos_defconfig: Enable MAX77802")
>>> enabled support for the max77802 regulators but the
Add an property "i2s_clk_out", which enables to output clock to outside
of rockchip SoCs. Let's make it optional since not each board needs it.
Signed-off-by: Jianqun Xu
---
changes since v1:
- make "i2s_clk_out" optional, suggested by Sonny
On Thu, Oct 23, 2014 at 3:22 PM, Geert Uytterhoeven
wrote:
> Currently the error message is needlessly splitted across two lines.
>
> Signed-off-by: Geert Uytterhoeven
> Cc: Rafael J. Wysocki
> ---
> drivers/cpufreq/cpufreq-dt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
On Tue, Nov 18, 2014 at 11:39 PM, Eduardo Valentin wrote:
> Different drivers request API extensions in of-thermal. For this reason,
> additional callbacks are required to fit the new drivers needs.
>
> The current API implementation expects the registering sensor driver
> to provide a get_temp
On 11/13/14 17:56, amit daniel kachhap wrote:
> On Sat, Nov 8, 2014 at 6:46 PM, Amit Daniel Kachhap
> wrote:
>> This patch series[1 - 6] performs,
>>
>> 1) Moves pmu driver to driver/soc/samsung folder. Some discussion happened
>> about
>>this in the v1 version. Finally adding it in
On 2014/11/19 14:57, Yun Wu (Abel) wrote:
> On 2014/11/18 22:32, Thomas Gleixner wrote:
>
>> On Tue, 18 Nov 2014, Yun Wu (Abel) wrote:
>>
>> Can you please trim the messages when you're replying?
>>
>>> The above you described is absolutely right, but not the things I want
>>> to know. :)
>>>
On 2014/11/19 14:57, Yun Wu (Abel) wrote:
On 2014/11/18 22:32, Thomas Gleixner wrote:
On Tue, 18 Nov 2014, Yun Wu (Abel) wrote:
Can you please trim the messages when you're replying?
The above you described is absolutely right, but not the things I want
to know. :)
Take GICv3 ITS for
On 11/13/14 17:56, amit daniel kachhap wrote:
On Sat, Nov 8, 2014 at 6:46 PM, Amit Daniel Kachhap
amit.dan...@samsung.com wrote:
This patch series[1 - 6] performs,
1) Moves pmu driver to driver/soc/samsung folder. Some discussion happened
about
this in the v1 version. Finally adding it
On Thu, Oct 23, 2014 at 3:22 PM, Geert Uytterhoeven
geert+rene...@glider.be wrote:
Currently the error message is needlessly splitted across two lines.
Signed-off-by: Geert Uytterhoeven geert+rene...@glider.be
Cc: Rafael J. Wysocki r...@rjwysocki.net
---
drivers/cpufreq/cpufreq-dt.c | 2 +-
On Tue, Nov 18, 2014 at 11:39 PM, Eduardo Valentin edubez...@gmail.com wrote:
Different drivers request API extensions in of-thermal. For this reason,
additional callbacks are required to fit the new drivers needs.
The current API implementation expects the registering sensor driver
to
Add an property i2s_clk_out, which enables to output clock to outside
of rockchip SoCs. Let's make it optional since not each board needs it.
Signed-off-by: Jianqun Xu jay...@rock-chips.com
---
changes since v1:
- make i2s_clk_out optional, suggested by Sonny
On 11/13/14 17:45, Javier Martinez Canillas wrote:
Hello Kukjin,
Hi Javier,
On Tue, Oct 28, 2014 at 12:06 PM, Kukjin Kim kg...@kernel.org wrote:
Javier Martinez Canillas wrote:
Commit 6e80e3d87549 (ARM: exynos_defconfig: Enable MAX77802)
enabled support for the max77802 regulators but the
Patch is from Sonny Rao sonny...@chromium.org
We need to claim the clock which is driving the codec so that when we enable
clock gating, we continue to clock the codec when needed. I make this an
optional clock since there might be some applications where we don't need it
but can still use the
On Tue, Nov 18, 2014 at 11:25 PM, Joe Stringer joestrin...@nicira.com wrote:
On 18 November 2014 22:09, Pravin Shelar pshe...@nicira.com wrote:
On Tue, Nov 18, 2014 at 10:54 AM, Joe Stringer joestrin...@nicira.com
wrote:
When userspace doesn't provide a mask, OVS datapath generates a fully
On Wed, Nov 05, 2014 at 04:49:51PM +0200, Kirill A. Shutemov wrote:
The patch updates Documentation/vm/transhuge.txt to reflect changes in
THP design.
Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com
---
Documentation/vm/transhuge.txt | 84
Hey,
On 19-11-14 07:43, Michael Marineau wrote:
On 3.18-rc kernel's I have been intermittently experiencing GPU
lockups shortly after startup, accompanied with one or both of the
following errors:
nouveau E[ PFIFO][:01:00.0] read fault at 0x000734a000 [PTE]
from PBDMA0/HOST_CPU on
Hi Steve,
On Tue, 18 Nov 2014 22:33:33 -0500, Steven Rostedt wrote:
From: Steven Rostedt (Red Hat) rost...@goodmis.org
Stack traces that happen from function tracing check if the address
on the stack is a __kernel_text_address(). That is, is the address
kernel code. This calls
Hi All
On 11/19/2014 03:09 AM, Johan Hedberg wrote:
Hi Kirill,
On Tue, Nov 18, 2014, Kirill A. Shutemov wrote:
On Fri, Nov 07, 2014 at 11:27:54AM +0200, Johan Hedberg wrote:
Chan-yeol Park (1):
Bluetooth: Fix hci_sync missing wakeup interrupt
Look like this commit causes problem for
On Wed, Nov 19, 2014 at 2:59 AM, Al Viro v...@zeniv.linux.org.uk wrote:
On Tue, Nov 18, 2014 at 03:28:03PM +0100, Miklos Szeredi wrote:
So from mainline we need two things:
- when mounting distinguish between old and new format.
- userspace can detect which formats are supported by the
Hi
On 11/19/2014 03:09 AM, Johan Hedberg wrote:
Hi Kirill,
On Tue, Nov 18, 2014, Kirill A. Shutemov wrote:
On Fri, Nov 07, 2014 at 11:27:54AM +0200, Johan Hedberg wrote:
Chan-yeol Park (1):
Bluetooth: Fix hci_sync missing wakeup interrupt
Look like this commit causes problem for me:
Hi Eduardo,
Different drivers request API extensions in of-thermal. For this
reason, additional callbacks are required to fit the new drivers
needs.
The current API implementation expects the registering sensor driver
to provide a get_temp and get_trend callbacks as function parameters.
Based on Arnds review comments here https://lkml.org/lkml/2014/11/13/161, update
the phy driver to not use the reg property to access the sysconfig register
offsets.
This is because other phy's (miphy28, miphy365) have a combination of memory
mapped
registers and sysconfig control regs, and we
Hi,
Following on from Arnds comments about the picophy driver here
https://lkml.org/lkml/2014/11/13/161, this series fixes the
remaining upstreamed drivers for STI, which are mixing address spaces
in the reg property. We do this in a way similar to the keystone
and bcm7445 platforms, by having
Based on Arnds review comments here https://lkml.org/lkml/2014/11/13/161,
we should not be mixing address spaces in the reg property like this driver
currently does. This patch updates the driver, dt docs and also the existing
dt nodes to pass the sysconfig offset in the syscon dt property.
This
This patch enables the picoPHY usb phy which is used by
the usb2 and usb3 host controllers when controlling usb2/1.1
devices. It is found in stih407 family SoC's from STMicroelectronics.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
Acked-by: Lee Jones lee.jo...@linaro.org
---
This patch adds the DT nodes for the extra ehci and ohci usb controllers
on the stih410 SoC.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
arch/arm/boot/dts/stih410.dtsi | 52 ++
1 file changed, 52 insertions(+)
diff --git
This patch adds the dt nodes for the usb2 picophy found on the stih407
device family. It is used on stih407 by the dwc3 usb3 controller when
controlling usb2/1.1 devices.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
arch/arm/boot/dts/stih407-family.dtsi | 9 +
1 file
This patch adds the dt nodes for the extra usb2 picophys found on the stih410.
These two picophys are used in conjunction with the extra ehci/ohci usb
controllers also found on the stih410.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
arch/arm/boot/dts/stih410.dtsi | 18
Based on Arnds review comments here https://lkml.org/lkml/2014/11/13/161, update
the miphy365 phy driver to access sysconfig register offsets via syscfg dt
property.
This is because the reg property should not be mixing address spaces like it
does
currently for miphy365. This change then also
On Mon, Nov 17, 2014 at 6:09 PM, Uwe Kleine-König
u.kleine-koe...@pengutronix.de wrote:
Hello,
On Wed, Feb 13, 2013 at 04:03:00PM +0900, Alexandre Courbot wrote:
From: Alexandre Courbot acour...@nvidia.com
Constify descriptor parameter of gpiod_* functions for those that
should obviously
On Wednesday 19 November 2014 13:35:44 Benjamin Herrenschmidt wrote:
On Wed, 2014-11-19 at 10:39 +1100, Jeremy Kerr wrote:
Hi Rob,
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 20da3ad..8c7b607 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -493,6
Remove cyapa_remove() method, add cyapa_open() and cyapa_close() methods for
input interface, also modified together with driver's memory and IRQ resource
allocations to support device resource management infrastructure to reduce
the mistakes of resource management.
TEST=test on Chromebooks.
Add suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the power management
strategy of trackpad device as their requirements.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa.c |
Based on the cyapa core, add the gen5 trackpad device's basic functions
supported, so gen5 trackpad device can work with kernel input system.
And also based on the state parse interface, the cyapa driver can
automatically determine the attached is gen3 or gen5 protocol trackpad
device, then set
V11 patches have below main updates compared with v10 patches:
1) Add add acpi device id supported for old gen3 and new gen5 trackpad devices.
2) Fix the unable to update firmware issue when cyapa_open is not called
which means the irq for firwmare update process is not enabled. This fix
by
This patch modified the code to fix the patch check warning issue with latest
checkpatch.sh tool, and also changed the return variable name from ret to
error when there is only one error path to follow code style.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
In order to support multiple different chipsets and communication protocols
trackpad devices in one cyapa driver, the new cyapa driver is re-designed
with one cyapa driver core and multiple device specific functions component.
The cyapa driver core is contained in this patch, it supplies basic
Add runtime_suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the runtime power
management strategy of trackpad device as their requirements.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
Add firmware image update function supported for gen3 trackpad device,
it can be used through sysfs update_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa_gen3.c | 284 +++
1 file changed,
Hi Mike,
On Wed, Nov 19, 2014 at 12:12 AM, Mike Turquette mturque...@linaro.org wrote:
Quoting Geert Uytterhoeven (2014-11-12 06:02:29)
This is my first pull request from renesas-drivers.
If there's anything that can be improved, please let me know.
Thanks!
Hurray for new pull requests!
Add device's basic control and features supported in cyapa driver through
sysfs file system interfaces. These interfaces are commonly used in
pre- and after production, for trackpad device state checking, managing
and firmware image updating.
These interfaces including mode, firmware_version and
Add read baseline function supported for gen3 trackpad device,
it can be used through sysfs baseline interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa_gen3.c | 71
1 file changed, 71
Add force re-calibrate function supported for gen3 trackpad device,
it can be used through sysfs calibrate interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa_gen3.c | 58
1 file changed, 58
Add force re-calibrate function supported for gen5 trackpad device,
it can be used through sysfs calibrate interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa_gen5.c | 65
1 file changed, 65
Add read baseline function supported for gen5 trackpad device,
it can be used through sysfs baseline interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa.h | 2 +
drivers/input/mouse/cyapa_gen5.c | 621
Add firmware image update function supported for gen5 trackpad device,
it can be used through sysfs update_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/Kconfig | 2 +-
drivers/input/mouse/cyapa_gen5.c | 290
Add read sensors' raw data from trackpad device interface supported in cyapa
driver through debugfs raw_data interface.
Through this interface, user can read difference count map of each sensors
directly from trackpad device (some customers want). And it's useful to help
users to find out the root
Add read firmware image from trackpad device interface supported in cyapa
driver through debugfs read_fw interface.
Through this interface user can read out, check and backup the firmware image
of the trackpad device before any firmware update, or can use the backed image
to do firmware image
Add read firmware image function supported for gen5 trackpad device,
it can be used through debugfs read_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa.h | 1 +
drivers/input/mouse/cyapa_gen5.c | 155
Add acpi device tree supported.
acpi device id CYAP is for old gen3 trackpad devices.
acpi device id CYAP0001 is for new gen5 trackpad devices.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa.c | 13 +
1 file changed, 13
Add read raw data function supported for gen5 trackpad device,
it can be used through debugfs raw_data interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa_gen5.c | 138 +++
1 file changed, 138
Add read firmware image function supported for gen3 trackpad device,
it can be used through debugfs read_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du dudley.duli...@gmail.com
---
drivers/input/mouse/cyapa_gen3.c | 67
1 file changed,
Hello Alexandre,
On Wed, Nov 19, 2014 at 05:33:42PM +0900, Alexandre Courbot wrote:
On Mon, Nov 17, 2014 at 6:09 PM, Uwe Kleine-König
u.kleine-koe...@pengutronix.de wrote:
Hello,
On Wed, Feb 13, 2013 at 04:03:00PM +0900, Alexandre Courbot wrote:
From: Alexandre Courbot
This patch adds the ahci_st.c driver found on STMicroelectronics
stih41x consumer electronics SoC's into the STI arch section
of the maintainers file.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS
On 11/18/2014 11:04 PM, Will Deacon wrote:
On Tue, Nov 18, 2014 at 01:10:34AM +, AKASHI Takahiro wrote:
+ if (((int)regs-syscallno == -1) (orig_syscallno == -1)) {
+ /*
+* user-issued syscall(-1):
+* RESTRICTION: We always return ENOSYS
On Wednesday 19 November 2014 11:17:15 Ding Tianhong wrote:
On 2014/11/18 2:09, Catalin Marinas wrote:
On Mon, Nov 17, 2014 at 12:18:42PM +, Arnd Bergmann wrote:
On Monday 17 November 2014 19:56:27 Ding Tianhong wrote:
The commit 3690951fc6d42f3a0903987677d0e592c49dd8db(arm64:
On Tue, Nov 18, 2014 at 09:45:41PM +0100, SF Markus Elfring wrote:
From: Markus Elfring elfr...@users.sourceforge.net
Date: Tue, 18 Nov 2014 21:41:26 +0100
The ipcomp_free_tfms() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not
On Tue, Nov 18, 2014 at 4:21 PM, Seth Forshee
seth.fors...@canonical.com wrote:
I asked around a bit, and it turns out there are use cases for nested
containers (i.e. a container within a container) where the rootfs for
the outer container mounts a filesystem containing the rootfs for the
On Wed, 19 Nov 2014, Peter Griffin wrote:
Based on Arnds review comments here https://lkml.org/lkml/2014/11/13/161,
we should not be mixing address spaces in the reg property like this driver
currently does. This patch updates the driver, dt docs and also the existing
dt nodes to pass the
1201 - 1300 of 2494 matches
Mail list logo
