On Wed, Jan 9, 2013 at 10:28 AM, Mika Westerberg
<mika.westerberg@xxxxxxxxxxxxxxx> wrote:
> On Tue, Jan 08, 2013 at 10:55:59PM +0100, Benjamin Tissoires wrote:
>> On Tue, Jan 8, 2013 at 7:09 PM, Mika Westerberg
>> <mika.westerberg@xxxxxxxxxxxxxxx> wrote:
>> > On Tue, Jan 08, 2013 at 02:51:53PM +0100, Benjamin Tissoires wrote:
>> >> Hi Mika,
>> >>
>> >> On Tue, Jan 8, 2013 at 2:05 PM, Mika Westerberg
>> >> <mika.westerberg@xxxxxxxxxxxxxxx> wrote:
>> >> > The HID over I2C protocol specification states that when the device is
>> >> > enumerated from ACPI the HID descriptor address can be obtained by
>> >> > executing "_DSM" for the device with function 1. Enable this.
>> >>
>> >> Hehe, funny thing, I worked on the very same patch last Friday. I was
>> >> not able to send it upstream as I still don't have an ACPI 5 enabled
>> >> device...
>> >> So thanks for submitting (and testing) this!
>> >>
>> >> Before the review, I just have a quick question. All the HID/i2c
>> >> devices I saw so far present a reset line (through a GPIO). Does the
>> >> shipped device you have present this line, and if yes, how this meld
>> >> with the code (i.e. should we take this into account).
>> >
>> > Yes, there is either one or two GPIO lines. But there are also devices that
>> > don't have any GPIO lines.
>>
>> Ouch. But if they don't have any GPIO, how can they manage to send
>> information? If they are using polling, then this will require some
>> more work in i2c-hid :(
>
> Well they don't have GPIO resources because their interrupt is directly
> routed to the ioapic and exposed as an Interrupt resource.
>
>> >
>> > We probably should take this into account. I'm not too familiar with HID
>> > drivers but what if we set the hid->dev.acpi_node and let the actual HID
>> > driver to deal with the GPIO?
>>
>> Well, HID is a communication layer between the device and the kernel
>> in order to make it agnostic of the transport layer (usb, bt or i2c).
>> Even if some drivers do some transport tuning, I don't think it's a
>> good idea to ask HID drivers to do transport handling such as setting
>> up GPIOs.
>
> If they have reset GPIO or something like that, how else we should we
> handle this if not in the driver? The i2c-hid core doesn't know for what
> purpose a given GPIO line is.
But the hid protocol aims at reducing the number of drivers. The idea
is to built one driver to rule them all... :)
Some stats:
- hid-multitouch (the driver that drives multitouch screens) has a
list of ~80 registered products, most of them are USB (few are
Bluetooth). Bonus point, this list is not exhaustive because there is
an auto-detection mechanism in place which forwards unknown
mt-touchscreen to hid-multitouch. Now with i2c-hid, hid-multitouch can
also handle any Win8 certified i2c touchscreen, so I guess it will add
a lot of new devices to this list.
- hid-core registered ~240 exception -> it means that on all existing
input devices that follow the hid protocol, only 240 need special
handling.
So my point is that some of the hid drivers may know the attached
GPIOs, but the generic hid drivers (hid-multitouch, hid-generic and
hid-core then) won't.
Anyway, there may be adjustments at the beginning, but I still think
we could add a common place for i2c quirks in i2c-hid, at least at the
beginning.
The best solution would be to be able to deduce the behavior of those
GPIOs thanks to the ACPI description. Problem for me: I can't have
access to the document referred in HID over i2c specification (Windows
ACPI Design Guide for SOC Platform) while working at Red Hat...
>
> i2c-hid core can handle the GPIO interrupt if client->irq is not set (by
> converting the GPIO into interrupt number and passing it to the hid
> driver). I didn't implement that because we have the client->irq already
> set so I can't test this.
But this part of the code is already in ACPI i2c enumeration, right?
So why you want to rewrite it in i2c-hid?
>
>> The closest thing which is already in the kernel tree is the handling
>> of device specific quirks in usbhid. We may be forced to do such a
>> thing if the DSDT is not explicit enough to guess the right behavior
>> (how to trigger the reset line, etc..)
>>
>> Also, I missed one point in my previous review:
>>
>> >
>> >> Please note that I can only compare this to my patch, based on the
>> >> DSDT example Microsoft gave in its spec. So sorry if I'm asking
>> >> useless things, but I like to understand... :)
>> >> Here are a few comments:
>> >>
>> >> >
>> >> > Signed-off-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
>> >> > ---
>> >> > drivers/hid/i2c-hid/i2c-hid.c | 73 +++++++++++++++++++++++++++++++++++++++--
>> >> > 1 file changed, 71 insertions(+), 2 deletions(-)
>> >> >
>> >> > diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c
>> >> > index 9ef22244..b2eebb6 100644
>> (...snipped...)
>>
>> >> > +
>> >> > + pdata = devm_kzalloc(&client->dev, sizeof(*pdata), GFP_KERNEL);
>>
>> Here, I don't think mixing devm_* and regular allocations is a good thing.
>> I know it's a pain, but at the time I wrote the driver, the input
>> layer was not devm-ized, so I was not able to use devm allocs. Now it
>> should be feasible, but I didn't found the time to do it.
>> So I'm afraid, this allocation must use a regular kwalloc and it
>> should be freed somewhere later, until we devm-ize the whole module.
>
> Good point.
>
> I was thinking to embed the platform data in the i2c_hid structure so that
> it gets allocated at the same time as ihid and then we can handle setting
> the platform data like:
>
> if (!platform_data) {
> ret = i2c_hid_acpi_pdata(client, &ihid->pdata);
> /* handle error */
> } else {
> ihid->pdata = *platform_data;
> }
>
> Does that sound feasible to you?
yep, go for it!
Cheers,
Benjamin
>
>> >> > + if (!pdata)
>> >> > + goto fail;
>> >>
>>
>> (...snipped...)
>> >> > if (!platform_data) {
>> >> > - dev_err(&client->dev, "HID register address not provided\n");
>> >> > - return -EINVAL;
>> >> > + platform_data = i2c_hid_acpi_pdata(client);
>> >> > + if (!platform_data) {
>> >> > + dev_err(&client->dev, "HID register address not provided\n");
>> >>
>> >> You may have a line with more than 80 characters here (it's difficult
>> >> to guess thanks to my gmail client converting tabs into spaces...
>> >> grrr)
>> >
>> > Shouldn't be as checkpatch.pl didn't complain but I'll re-check.
>>
>> It's strange if it didn't complained: I count 61 chars for the
>> dev_err() message + 3 tabs * 8 chars => 85 chars in total...
>
> You are right, it is over 85 chars.
>
> I've learned that checkpatch.pl doesn't complain if the line is longer than
> 80 chars, if it contains quoted string.
>
> I'll fix it up.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
