Hello Fabio,
On 08/07/2014 03:35 AM, Fabio Estevam wrote:
> On Wed, Aug 6, 2014 at 10:08 PM, Javier Martinez Canillas
> wrote:
>
>> +&hsi2c_8 {
>> + status = "okay";
>> + clock-frequency = <333000>;
>
> Doesn't it work at the more standard 400kHz i2c frequency?
>
Most bits of this
Fabio,
On Wed, Aug 6, 2014 at 6:35 PM, Fabio Estevam wrote:
> On Wed, Aug 6, 2014 at 10:08 PM, Javier Martinez Canillas
> wrote:
>
>> +&hsi2c_8 {
>> + status = "okay";
>> + clock-frequency = <333000>;
>
> Doesn't it work at the more standard 400kHz i2c frequency?
I'm pretty sure tha
If the device data is not accessible for some reason, returning 0 will cause
the call to be
continuously called again as none of the string has been 'consumed'.
---
drivers/hid/hid-lg4ff.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hid/hid-lg4ff.c b/drivers/hi
From: Fabio Estevam
There is no need to first get a platform_device structure in the suspend/resume
functions.
Make the code simpler by calling dev_get_drvdata() directly.
Signed-off-by: Fabio Estevam
---
drivers/input/keyboard/imx_keypad.c | 10 --
1 file changed, 4 insertions(+), 6
On Thu, Aug 07, 2014 at 03:47:24AM +0200, Javier Martinez Canillas wrote:
> Hello Tomasz,
>
> Thanks a lot for your feedback.
>
> On 08/07/2014 03:14 AM, Tomasz Figa wrote:
> > Hi Javier,
> >
> >
> > Have you observed an actual failure due to this? I believe that
>
> Yes, I found this issue si
Hi Fabio,
On Thu, Aug 07, 2014 at 01:40:57AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam
>
> There is no need to first get a platform_device structure in the
> suspend/resume
> functions.
>
> Make the code simpler by calling dev_get_drvdata() directly.
I actually believe that we should
On Wed, Aug 06, 2014 at 07:47:25PM +, Murphy, Dan wrote:
> Bump
>
> On 07/31/2014 02:14 PM, Murphy, Dan wrote:
> > Add the TI drv260x haptics/vibrator driver.
> > This device uses the input force feedback
> > to produce a wave form to driver an
> > ERM or LRA actuator device.
> >
> > The init
On Sun, Jul 20, 2014 at 06:20:49PM -0700, Dmitry Torokhov wrote:
> Wire up support for EVIOC{G|S}KEYCODE to allow users change key mappings
> from userspace.
>
> Signed-off-by: Dmitry Torokhov
> ---
>
> Just compiled, not tested.
*ping* Any chance you could give it a try? Thanks!
>
> drivers
On Wed, Aug 06, 2014 at 04:28:26PM -0700, Christopher Heiny wrote:
> [I sent this last Thursday, but it never showed up on the input
> list. I'm assuming nobody else saw it.]
>
>
> On 07/31/2014 02:58 PM, Dmitry Torokhov wrote:
> >On Thu, Jul 31, 2014 at 02:43:47PM -0700, Christopher Heiny wrote:
Hi Dmitry,
On 08/07/2014 08:20 AM, Dmitry Torokhov wrote:
> On Sun, Jul 20, 2014 at 06:20:49PM -0700, Dmitry Torokhov wrote:
>> Wire up support for EVIOC{G|S}KEYCODE to allow users change key mappings
>> from userspace.
>>
>> Signed-off-by: Dmitry Torokhov
>> ---
>>
>> Just compiled, not tested.
Can I talk to you, I will be very glad if you permit me to talk to you for an
important deal.
Regards,
KM.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-i
Hi Michael,
On Tue, Aug 05, 2014 at 12:06:40PM -0500, Michael Welling wrote:
> The TSC2004 driver has yet to appear in the mainline kernel. We have
> been using the driver referenced here as provided by TI:
>
> https://www.mail-archive.com/linux-omap@vger.kernel.org/msg22018.html
>
> Are there a
Bump
On 07/31/2014 02:14 PM, Murphy, Dan wrote:
> Add the TI drv260x haptics/vibrator driver.
> This device uses the input force feedback
> to produce a wave form to driver an
> ERM or LRA actuator device.
>
> The initial driver supports the devices
> real time playback mode. But the device
> ha
On 6 August 2014 21:37, Dmitry Torokhov wrote:
> Hi Michael,
>
> On Tue, Aug 05, 2014 at 12:06:40PM -0500, Michael Welling wrote:
>> The TSC2004 driver has yet to appear in the mainline kernel. We have
>> been using the driver referenced here as provided by TI:
>>
>> https://www.mail-archive.com/l
On Fri, Aug 01, 2014 at 07:28:24AM -0700, Dexuan Cui wrote:
> With this patch, we can press a key to wake up the VM after the VM executes
> "echo freeze > /sys/power/state".
>
> This addresses part of https://bugzilla.redhat.com/show_bug.cgi?id=1086100
I am sorry but this bug is not open to the p
On Aug 05 2014 or thereabouts, Ping Cheng wrote:
> On Tue, Aug 5, 2014 at 2:34 PM, Benjamin Tissoires
> wrote:
> > Hi Ping,
> >
> > On Aug 05 2014 or thereabouts, Ping Cheng wrote:
> >> Thank you Benjamin for updating the ABI docs. My comments are inline.
> >>
> >> With those lines updated, this p
Currently rmi_probe will return -EIO if the device doesn't report that it has
F11.
This would indicate that something happened and the device is in the bootloader.
We can recover the device using a userspace firmware update tool, but it needs
access to the device through the hidraw device file. If
On Wed, Aug 06, 2014 at 04:44:08PM -0400, Benjamin Tissoires wrote:
> On Aug 05 2014 or thereabouts, Ping Cheng wrote:
> > On Tue, Aug 5, 2014 at 2:34 PM, Benjamin Tissoires
> > wrote:
> > > Hi Ping,
> > >
> > > On Aug 05 2014 or thereabouts, Ping Cheng wrote:
> > >> Thank you Benjamin for updatin
On Wed, Aug 06, 2014 at 10:33:18PM +0200, Joachim Eastwood wrote:
> On 6 August 2014 21:37, Dmitry Torokhov wrote:
> > Hi Michael,
> >
> > On Tue, Aug 05, 2014 at 12:06:40PM -0500, Michael Welling wrote:
> >> The TSC2004 driver has yet to appear in the mainline kernel. We have
> >> been using the
On Aug 06 2014 or thereabouts, Dmitry Torokhov wrote:
> On Wed, Aug 06, 2014 at 04:44:08PM -0400, Benjamin Tissoires wrote:
> > On Aug 05 2014 or thereabouts, Ping Cheng wrote:
> > > On Tue, Aug 5, 2014 at 2:34 PM, Benjamin Tissoires
> > > wrote:
> > > > Hi Ping,
> > > >
> > > > On Aug 05 2014 or
On Wed, Aug 06, 2014 at 05:29:02PM -0400, Benjamin Tissoires wrote:
> On Aug 06 2014 or thereabouts, Dmitry Torokhov wrote:
> > On Wed, Aug 06, 2014 at 04:44:08PM -0400, Benjamin Tissoires wrote:
> > > On Aug 05 2014 or thereabouts, Ping Cheng wrote:
> > > > On Tue, Aug 5, 2014 at 2:34 PM, Benjamin
On Wed, Aug 6, 2014 at 4:16 PM, Dmitry Torokhov
wrote:
> On Wed, Aug 06, 2014 at 10:33:18PM +0200, Joachim Eastwood wrote:
>> On 6 August 2014 21:37, Dmitry Torokhov wrote:
>> > Hi Michael,
>> >
>> > On Tue, Aug 05, 2014 at 12:06:40PM -0500, Michael Welling wrote:
>> >> The TSC2004 driver has yet
Hi,
On Wed, Aug 06, 2014 at 05:13:19PM -0500, Michael Welling wrote:
> The tsc2005 still needs devicetree conversion, so it is at least 2
> patches away from where I can use it.
TSC2005 DT support has been added in 3.16:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a
On Wed, Aug 6, 2014 at 5:28 PM, Sebastian Reichel wrote:
> Hi,
>
> On Wed, Aug 06, 2014 at 05:13:19PM -0500, Michael Welling wrote:
>> The tsc2005 still needs devicetree conversion, so it is at least 2
>> patches away from where I can use it.
>
> TSC2005 DT support has been added in 3.16:
>
> http
[I sent this last Thursday, but it never showed up on the input list.
I'm assuming nobody else saw it.]
On 07/31/2014 02:58 PM, Dmitry Torokhov wrote:
On Thu, Jul 31, 2014 at 02:43:47PM -0700, Christopher Heiny wrote:
On 07/31/2014 02:19 PM, Dmitry Torokhov wrote:
On Thu, Jul 31, 2014 at 02:
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: Thursday, August 7, 2014 4:34 AM
> To: Dexuan Cui
> On Fri, Aug 01, 2014 at 07:28:24AM -0700, Dexuan Cui wrote:
> > With this patch, we can press a key to wake up the VM after the VM
> executes
> > "echo
On Wed, Aug 6, 2014 at 5:19 PM, Dexuan Cui wrote:
>
> > -Original Message-
> > From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> > Sent: Thursday, August 7, 2014 4:34 AM
> > To: Dexuan Cui
> > On Fri, Aug 01, 2014 at 07:28:24AM -0700, Dexuan Cui wrote:
> > > With this patch, we ca
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Dmitry Torokhov
> > Hi Dmitry,
> > Sorry, I didn't realize it's not public... :-)
> >
> > I'll remove the line and re-send the patch.
> >
>
> No need to resend, I alr
The Atmel maXTouch driver allows to dynamically define the
event keycodes set that the device is capable of. This may
not be evident when reading the DT binding document so add
an example to make it easier to understand how this works.
Also, the current documentation says that the array limit
is f
The Atmel maXTouch driver assumed that the IRQ type flags will
always be passed using platform data but this is not true when
booting using Device Trees. In these setups the interrupt type
was ignored by the driver when requesting an IRQ.
This means that it will fail if a machine specified other t
From: Sjoerd Simons
The Peach Pit and Pi boards have an Atmel maXTouch device.
Add the needed Device Tree nodes to support it.
Signed-off-by: Sjoerd Simons
[javier.martinez: added linux,gpio-keymap property and changed IRQ type]
Signed-off-by: Javier Martinez Canillas
---
With only this patch
Hi Javier,
On 07.08.2014 02:48, Javier Martinez Canillas wrote:
> The Atmel maXTouch driver assumed that the IRQ type flags will
> always be passed using platform data but this is not true when
> booting using Device Trees. In these setups the interrupt type
> was ignored by the driver when reques
On Wed, Aug 6, 2014 at 10:08 PM, Javier Martinez Canillas
wrote:
> +&hsi2c_8 {
> + status = "okay";
> + clock-frequency = <333000>;
Doesn't it work at the more standard 400kHz i2c frequency?
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a me
Hello Tomasz,
Thanks a lot for your feedback.
On 08/07/2014 03:14 AM, Tomasz Figa wrote:
> Hi Javier,
>
>
> Have you observed an actual failure due to this? I believe that
Yes, I found this issue since the driver was not taking into account the value
defined in the edge/level type cells from t
34 matches
Mail list logo
