Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-11-27 Thread Benjamin Tissoires
On Mon, Nov 26, 2012 at 11:54 PM, Christopher Heiny wrote: > On 11/26/2012 10:41 AM, Benjamin Tissoires wrote: >> >> Hi Christopher, >> >> On Sat, Nov 17, 2012 at 4:58 AM, Christopher Heiny >> wrote: >>> >>> rmi_bus.c implements the basic functionality of the RMI bus. This file >>> is >>> greatl

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-11-26 Thread Christopher Heiny
On 11/26/2012 10:41 AM, Benjamin Tissoires wrote: Hi Christopher, On Sat, Nov 17, 2012 at 4:58 AM, Christopher Heiny wrote: rmi_bus.c implements the basic functionality of the RMI bus. This file is greatly simplified compared to the previous patch - we've switched from "do it yourself" device

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-11-26 Thread Benjamin Tissoires
Hi Christopher, On Sat, Nov 17, 2012 at 4:58 AM, Christopher Heiny wrote: > rmi_bus.c implements the basic functionality of the RMI bus. This file is > greatly simplified compared to the previous patch - we've switched from > "do it yourself" device/driver binding to using device_type to disting

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-11-19 Thread Christopher Heiny
On 11/17/2012 01:54 PM, Greg Kroah-Hartman wrote: On Fri, Nov 16, 2012 at 07:58:50PM -0800, Christopher Heiny wrote: +static void release_rmidev_device(struct device *dev) +{ + device_unregister(dev); +} You just leaked memory here, right? Also, you already unregistered the device, othe

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-11-17 Thread Linus Walleij
On Sat, Nov 17, 2012 at 4:58 AM, Christopher Heiny wrote: > rmi_bus.c implements the basic functionality of the RMI bus. This file is > greatly simplified compared to the previous patch - we've switched from > "do it yourself" device/driver binding to using device_type to distinguish > between t

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-11-17 Thread Greg Kroah-Hartman
On Fri, Nov 16, 2012 at 07:58:50PM -0800, Christopher Heiny wrote: > +static void release_rmidev_device(struct device *dev) > +{ > + device_unregister(dev); > +} You just leaked memory here, right? Also, you already unregistered the device, otherwise this function would have never been called

[RFC PATCH 02/06] input/rmi4: Core files

2012-11-16 Thread Christopher Heiny
rmi_bus.c implements the basic functionality of the RMI bus. This file is greatly simplified compared to the previous patch - we've switched from "do it yourself" device/driver binding to using device_type to distinguish between the two kinds of devices on the bus (sensor devices and function spec

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-23 Thread Christopher Heiny
On 10/23/2012 05:11 PM, Dmitry Torokhov wrote: On Tuesday, October 23, 2012 04:46:28 PM Christopher Heiny wrote: On 10/11/2012 01:13 AM, Dmitry Torokhov wrote: On Thu, Oct 11, 2012 at 04:15:56AM +, Christopher Heiny wrote: On Thursday, October 11, 2012 02:21:53 AM you wrote: On Sat, Oct 6

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-23 Thread Dmitry Torokhov
On Tuesday, October 23, 2012 04:46:28 PM Christopher Heiny wrote: > On 10/11/2012 01:13 AM, Dmitry Torokhov wrote: > > On Thu, Oct 11, 2012 at 04:15:56AM +, Christopher Heiny wrote: > >> On Thursday, October 11, 2012 02:21:53 AM you wrote: > >>> On Sat, Oct 6, 2012 at 6:09 AM, Christopher Heiny

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-23 Thread Christopher Heiny
On 10/11/2012 01:13 AM, Dmitry Torokhov wrote: On Thu, Oct 11, 2012 at 04:15:56AM +, Christopher Heiny wrote: On Thursday, October 11, 2012 02:21:53 AM you wrote: On Sat, Oct 6, 2012 at 6:09 AM, Christopher Heiny wrote: + +/** This is here because all those casts made for some ugly co

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-22 Thread Christopher Heiny
On 10/10/2012 08:06 PM, Joe Perches wrote: On Thu, 2012-10-11 at 02:49 +, Christopher Heiny wrote: Joe Perches wrote: [] + list_for_each_entry(entry, &data->rmi_functions.list, list) + if (entry->irq_mask) + process_one_interrupt(entry, irq_status, +

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-11 Thread Linus Walleij
On Thu, Oct 11, 2012 at 6:15 AM, Christopher Heiny wrote: > On Thursday, October 11, 2012 02:21:53 AM I wrote: >> > +union pdt_properties { >> > + struct { >> > + u8 reserved_1:6; >> > + u8 has_bsr:1; >> > + u8 reserved_2:1; >> > + } __attribu

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-11 Thread Dmitry Torokhov
On Thu, Oct 11, 2012 at 04:15:56AM +, Christopher Heiny wrote: > On Thursday, October 11, 2012 02:21:53 AM you wrote: > > On Sat, Oct 6, 2012 at 6:09 AM, Christopher Heiny > > wrote: > > > > > > + > > > +/** This is here because all those casts made for some ugly code. > > > + */ > > > +sta

RE: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-10 Thread Christopher Heiny
On Thursday, October 11, 2012 02:21:53 AM you wrote: > On Sat, Oct 6, 2012 at 6:09 AM, Christopher Heiny > wrote: > > rmi_bus.c implements the basic functionality of the RMI bus. This file is > > greatly simplified compared to the previous patch - we've switched from > > "do it yourself" device/

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-10 Thread Joe Perches
On Thu, 2012-10-11 at 02:49 +, Christopher Heiny wrote: > Joe Perches wrote: [] > > > + list_for_each_entry(entry, &data->rmi_functions.list, list) > > > + if (entry->irq_mask) > > > + process_one_interrupt(entry, irq_status, > > > +

RE: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-10 Thread Christopher Heiny
Joe Perches wrote: > On Fri, 2012-10-05 at 21:09 -0700, Christopher Heiny wrote: > [] > > Just some trivial comments: Thanks - see below for responses. > > diff --git a/drivers/input/rmi4/rmi_driver.c > > b/drivers/input/rmi4/rmi_driver.c > [] > > > @@ -0,0 +1,1529 @@ > > [] > > > +static ssi

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-09 Thread Linus Walleij
On Sat, Oct 6, 2012 at 6:09 AM, Christopher Heiny wrote: > rmi_bus.c implements the basic functionality of the RMI bus. This file is > greatly simplified compared to the previous patch - we've switched from > "do it yourself" device/driver binding to using device_type to distinguish > between th

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-06 Thread devendra.aaru
On Sat, Oct 6, 2012 at 9:06 AM, devendra.aaru wrote: > On Sat, Oct 6, 2012 at 8:19 AM, Joe Perches wrote: >> On Fri, 2012-10-05 at 21:09 -0700, Christopher Heiny wrote: >> [] >> >> Just some trivial comments: >> >>> diff --git a/drivers/input/rmi4/rmi_driver.c >>> b/drivers/input/rmi4/rmi_driver

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-06 Thread devendra.aaru
On Sat, Oct 6, 2012 at 8:19 AM, Joe Perches wrote: > On Fri, 2012-10-05 at 21:09 -0700, Christopher Heiny wrote: > [] > > Just some trivial comments: > >> diff --git a/drivers/input/rmi4/rmi_driver.c >> b/drivers/input/rmi4/rmi_driver.c > [] >> @@ -0,0 +1,1529 @@ > [] >> +static ssize_t delay_wri

Re: [RFC PATCH 02/06] input/rmi4: Core files

2012-10-06 Thread Joe Perches
On Fri, 2012-10-05 at 21:09 -0700, Christopher Heiny wrote: [] Just some trivial comments: > diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4/rmi_driver.c [] > @@ -0,0 +1,1529 @@ [] > +static ssize_t delay_write(struct file *filp, const char __user *buffer, > +