On Fri, 22 May 2015, Dmitry Torokhov wrote:
> The STMPE MFD is only used with device tree configured systems (and STMPE
> MFD core depends on OF), so force the configuration to come from device
> tree only.
>
> Signed-off-by: Dmitry Torokhov
> ---
>
> Not tested as no device, please give it a s
On Tue, 28 Apr 2015, Antonio Ospite wrote:
> Most of the entries are aligned with TABs, fix those which are not.
>
> Signed-off-by: Antonio Ospite
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to ma
On 22 May 2015 at 16:39, Russell King - ARM Linux
wrote:
> On Fri, May 22, 2015 at 04:37:12PM +0200, Ulf Hansson wrote:
>> On 14 April 2015 at 12:41, Ulf Hansson wrote:
>> > The legacy system PM support has long time ago been dropped from the
>> > AMBA bus. Align to that by converting to the mode
On Tue, 19 May 2015, S Twiss wrote:
> From: Steve Twiss
>
> Add MFD support for the DA9063 OnKey driver
>
> The function da9063_clear_fault_log() is added to mitigate the case of a
> hardware power-cut after a long-long OnKey press. Although there is no
> software intervention in this case (by
On Tue, 19 May 2015, S Twiss wrote:
> From: Steve Twiss
>
> Add device tree bindings for the DA9063 OnKey driver
>
> Acked-by: Lee Jones
>
> Signed-off-by: Steve Twiss
>
> ---
> Version History
>
> Changes in V4
> - No change
>
> Changes in V3
> - No change
>
> Changes in V2
> - Remov
On 26 May 2015 14:58 Lee Jones wrote:
> To: Opensource [Steve Twiss]
> Cc: Samuel Ortiz; DT; David Dajun Chen; Dmitry Torokhov; INPUT; Ian
> Campbell; Kumar Gala; LKML; Mark Rutland; Pawel Moll; Rob Herring;
> Support Opensource
> Subject: Re: [RESEND PATCH V4 3/3] mfd: da9063: MFD support for On
On Tue, 19 May 2015, S Twiss wrote:
> From: S Twiss
>
> Add MFD core driver support for DA9062
>
>
> Signed-off-by: Steve Twiss
>
> ---
> Changes in V3:
> - Removed references to the RTC and OnKey in the mfd_cell definition.
>
> Changes in V2:
> - Copyright headers GPL v2 (and later) matc
From: Frank Li
Tested old and new dts in imx6sx platform.
Change from v5 to v6
- use dev_warn and dev_err
- use phandle regmap
- update document and dts for phandle regmap
- use data variable in rtc-snvs.c
Change from v3 to v4
- fix align
- change to pr_warn
Change from v2 to v3
- Keep
From: Frank Li
snvs included rtc, on/off key, power-off module
change to syscon to access register
Signed-off-by: Frank Li
---
drivers/rtc/rtc-snvs.c | 132 +
1 file changed, 67 insertions(+), 65 deletions(-)
diff --git a/drivers/rtc/rtc-snvs.c
From: Frank Li
snvs is MFP device. Change dts to use syscon to allocate register resource.
snvs power off also switch to common syscon-poweroff
Signed-off-by: Frank Li
---
arch/arm/boot/dts/imx6qdl.dtsi | 21 +++--
arch/arm/boot/dts/imx6sl.dtsi | 21 +++--
arch
From: Frank Li
The snvs-pwrkey is designed to enable POWER key function which controlled
by SNVS ONOFF. the driver can report the status of POWER key and wakeup
system if pressed after system suspend.
Signed-off-by: Frank Li
Signed-off-by: Robin Gong
---
.../devicetree/bindings/crypto/fsl-sec
From: Robin Gong
add snvs power key driver.
It work in imx chips after i.mx6sx
ON/OFF key used power on/off whole system.
This driver make it wakeup from suspend state when short press
ON/OFF key.
Long time press will trig SNVS power off chip without software
intervention.
Signed-off-by: Robin
From: Frank Li
snvs actually is multi fucntion driver.
Change to use syscon to access register.
Change snvs parent interrupt to option because single function
may have seperated irq number.
Signed-off-by: Frank Li
---
.../devicetree/bindings/crypto/fsl-sec4.txt| 42 +++-
From: Frank Li
enable snvs ONOFF power key support
Signed-off-by: Frank Li
---
arch/arm/boot/dts/imx6sx.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx.dtsi b/arch/arm/boot/dts/imx6sx.dtsi
index f8f0819..e391d63 100644
--- a/arch/arm/boot/dts/imx6sx.d
On Mon, May 25, 2015 at 02:41:38PM +0300, Dmitry Eremin-Solenikov wrote:
> As LoCoMo is switching to new device model, adapt keyboard driver to
> support new locomo core driver.
>
> Signed-off-by: Dmitry Eremin-Solenikov
Acked-by: Dmitry Torokhov
> ---
> drivers/input/keyboard/Kconfig |
On Mon, May 25, 2015 at 02:41:39PM +0300, Dmitry Eremin-Solenikov wrote:
> There are two Enter keys on collie/poodle keyboards. Make one of them to
> generate KEY_KPENTER rather than just KEY_ENTER.
>
> Signed-off-by: Dmitry Eremin-Solenikov
Acked-by: Dmitry Torokhov
> ---
> drivers/input/key
On Sun, May 24, 2015 at 02:43:28PM +0900, Krzysztof Kozlowski wrote:
> This prepares for merging some of the drivers between max77693 and
> max77843 so the child MFD driver can be attached to any parent MFD main
> driver.
>
> Move the state container to common header file. Additionally add
> consi
On Sun, May 24, 2015 at 02:43:29PM +0900, Krzysztof Kozlowski wrote:
> Switch to the same definition of state container as in MAX77693 drivers.
> This will allow usage of one regulator driver in both devices: MAX77693
> and MAX77843.
>
> Signed-off-by: Krzysztof Kozlowski
For input:
Acked-by: D
Greetings,
I have been porting Linux to a new AM3554 based SoM and have found issues
with the touchscreen reporting touch releases repeatedly to userspace
without actually touching the screen when running ts_calibrate, ts_test
or other graphical touchscreen applications.
This started happening af
Hi,
On Tue, May 26, 2015 at 01:11:57PM -0500, Michael Welling wrote:
> Greetings,
>
> I have been porting Linux to a new AM3554 based SoM and have found issues
> with the touchscreen reporting touch releases repeatedly to userspace
> without actually touching the screen when running ts_calibrate,
On Mon, May 25, 2015 at 10:30:04PM +0530, Shailendra Verma wrote:
> The return type of the function samsung_keypad_report() is bool but we are
> returning the unsigned int value.So changing the unsigned int to bool type
> and initializing with false.
>
> Signed-off-by: Shailendra Verma
> ---
> d
On Tue, May 26, 2015 at 01:37:13PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Tue, May 26, 2015 at 01:11:57PM -0500, Michael Welling wrote:
> > Greetings,
> >
> > I have been porting Linux to a new AM3554 based SoM and have found issues
> > with the touchscreen reporting touch releases repeatedly to
Hi Jiri,
I think I have given my input on what should be done with the code.
I'll leave it up to you to decide whether to accept the patch or not.
Please do let me know if you have any questions you want to ask me.
I would recommend that Nicholas change the 0x07dd to PRO though, as
they might
> -Original Message-
> From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of Michael
> Welling
> Sent: Tuesday, May 26, 2015 3:53 PM
> To: Balbi, Felipe
> Cc: Cooper Jr., Franklin; dmitry.torok...@gmail.com; R, Vignesh; Griffis,
> Brad; ji...@kernel.org; w...@the-dreams.de; lin
Dmitry Eremin-Solenikov writes:
> Convert poodle to use new mfd-based LoCoMo driver.
>
> Signed-off-by: Dmitry Eremin-Solenikov
> Reviewed-by: Linus Walleij
Acked-by: Robert Jarzmik
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a m
On Tue, May 26, 2015 at 09:15:53PM +, Cooper Jr., Franklin wrote:
> Michael,
>
> Can you send me the output of ts_test_raw after you done a 5 or so touch down
> and touch up events? In the output let me know at which point in the log that
> the issue you observed has occurred. Please try to
> -Original Message-
> From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of Michael
> Welling
> Sent: Tuesday, May 26, 2015 4:29 PM
> To: Cooper Jr., Franklin
> Cc: Balbi, Felipe; dmitry.torok...@gmail.com; R, Vignesh; Griffis, Brad;
> ji...@kernel.org; w...@the-dreams.de; lin
> -Original Message-
> From: Cooper Jr., Franklin
> > -Original Message-
> > From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of
> > Michael Welling
> > Sent: Tuesday, May 26, 2015 4:29 PM
> > To: Cooper Jr., Franklin
> > Cc: Balbi, Felipe; dmitry.torok...@gmail.com; R
On Tue, May 26, 2015 at 09:34:10PM +, Cooper Jr., Franklin wrote:
>
>
> > -Original Message-
> > From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of Michael
> > Welling
> > Sent: Tuesday, May 26, 2015 4:29 PM
> > To: Cooper Jr., Franklin
> > Cc: Balbi, Felipe; dmitry.toro
On Mon, May 25, 2015 at 10:41:28PM +0530, Shailendra Verma wrote:
> The variable psmouse_smartscroll is bool type so assigning true
> instead of 1.
>
> Signed-off-by: Shailendra Verma
Applied, thank you.
> ---
> drivers/input/mouse/psmouse-base.c |2 +-
> 1 file changed, 1 insertion(+), 1
On Mon, May 25, 2015 at 11:03:04PM +0530, Shailendra Verma wrote:
> The function synaptics_i2c_get_input() has bool return type.
> So use bool value flase instead of 0 to return.
>
> Signed-off-by: Shailendra Verma
Folded all 3 patches together and applied.
Thank you.
> ---
> drivers/input/mo
On Mon, May 25, 2015 at 11:11:17PM +0530, Shailendra Verma wrote:
>
> Signed-off-by: Shailendra Verma
There were a few more typos, I fixed those up as well and applied.
> ---
> drivers/input/mouse/cyapa_gen5.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/dri
On Tue, May 26, 2015 at 09:36:57PM +, Griffis, Brad wrote:
>
> > -Original Message-
> > From: Cooper Jr., Franklin
> > > -Original Message-
> > > From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of
> > > Michael Welling
> > > Sent: Tuesday, May 26, 2015 4:29 PM
> >
> -Original Message-
> From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of Michael
> Welling
>
> It seems to have something to do with the characteristic of the touchscreen
> as this does not happen on my 7" display.
>
> Looking at the datasheet these pin are dedicated analog
> -Original Message-
> From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of Michael
> Welling
> Sent: Tuesday, May 26, 2015 4:51 PM
> To: Griffis, Brad
> Cc: Cooper Jr., Franklin; Balbi, Felipe; dmitry.torok...@gmail.com; R,
> Vignesh; ji...@kernel.org; w...@the-dreams.de; lin
On Tue, May 26, 2015 at 10:25:01PM +, Griffis, Brad wrote:
> > -Original Message-
> > From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of Michael
> > Welling
> >
> > It seems to have something to do with the characteristic of the touchscreen
> > as this does not happen on
On Tue, May 26, 2015 at 10:31:32PM +, Cooper Jr., Franklin wrote:
>
>
> > -Original Message-
> > From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of Michael
> > Welling
> > Sent: Tuesday, May 26, 2015 4:51 PM
> > To: Griffis, Brad
> > Cc: Cooper Jr., Franklin; Balbi, Feli
> On May 26, 2015, at 6:07 PM, Michael Welling wrote:
>
>> On Tue, May 26, 2015 at 10:31:32PM +, Cooper Jr., Franklin wrote:
>>
>>
>>> -Original Message-
>>> From: Michael Welling [mailto:mwellin...@gmail.com] On Behalf Of Michael
>>> Welling
>>> Sent: Tuesday, May 26, 2015 4:51
Hi Michael,
On Wednesday 27 May 2015 04:36 AM, Michael Welling wrote:
> On Tue, May 26, 2015 at 10:31:32PM +, Cooper Jr., Franklin wrote:
>>
[snip]
>
> Perhaps there is coupling between the LCD lines and the ADC lines?
On Beaglebone Black with BB-View 4.3" Cape from Farnell, the LCD lines
39 matches
Mail list logo
