From: Benjamin Tissoires <benjamin.tissoires@gmail.com>
To: David Barksdale <dbarksdale@uplogix.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jkosina@suse.cz>,
David Herrmann <dh.herrmann@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] HID: cp2112: remove the last hid_output_raw_report() call
Date: Wed, 5 Mar 2014 16:09:36 -0500 [thread overview]
Message-ID: <CAN+gG=FOzo90DbMqp-Dh-OF4oCuBzXC-nwODPkNk62CV_usDxQ@mail.gmail.com> (raw)
In-Reply-To: <ba12abe9-5f40-4351-8dc0-76008931fc0d@email.android.com>
On Wed, Mar 5, 2014 at 1:11 PM, David Barksdale <dbarksdale@uplogix.com> wrote:
> Sorry for the delay, hid_hw_output_report() is the correct function.
No worries and thanks for the tests.
This saves me some time!
Sending the v2 right away.
Cheers,
Benjamin
>
>
> On March 4, 2014 8:18:38 AM CST, Benjamin Tissoires
> <benjamin.tissoires@redhat.com> wrote:
>>
>> On Mar 04 2014 or thereabouts, Jiri Kosina wrote:
>>>
>>> On Fri, 28 Feb 2014, Benjamin Tissoires wrote:
>>>
>>>>
>>>> I don't have access to the device, so I copied/pasted the code
>>>> from hidraw.
>>>>
>>>> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
>>>> ---
>>>> drivers/hid/hid-cp2112.c | 16 +++++++++++++++-
>>>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/hid/hid-cp2112.c b/drivers/hid/hid-cp2112.c
>>>> index 860db694..c4f87bd 100644
>>>> --- a/drivers/hid/hid-cp2112.c
>>>> +++ b/drivers/hid/hid-cp2112.c
>>>> @@ -290,7 +290,21 @@ static int cp2112_hid_output(struct hid_device
>>>> *hdev, u8 *data, size_t count,
>>>> if (!buf)
>>>> return -ENOMEM;
>>>>
>>>> - ret = hdev->hid_output_raw_report(hdev, buf, count, report_type);
>>>> + /* Fixme: test which function is actually called for output reports
>>>> */
>>>
>>>
>>> I don't completely understand this Fixme (oh, and please spell it as
>>> 'FIXME:' so that we are consistent with all the other instances), could
>>> you please elaborate?
>>
>>
>> Well, sorry:
>> As I said, this part is a copy/paste of what is in hidraw. However, this
>> just reflect that we don't know how the device actually behave, which is
>> not very elegant. I have currently no clues of which function will be
>> actually called for output reports: hid_hw_output_report() or
>> hid_hw_raw_request(). Once we got the confirmation of which function is
>> called, we could make the path more straightforward.
>>
>> I bought one of these (it may help debugging some Synaptics devices),
>> and I'll receive it by the end of the week. So by next week, we should
>> get the actual code path and remove this FIXME.
>>
>> I need to send a v2 of hid-sony in any cases, so I guess you should not
>> pull these 4 patches right away. If you prefer having this in linux-next,
>> the sooner, I can also send the v2 right away, and we will fix this
>> cp2112 driver next week.
>>
>> Cheers,
>> Benjamin
>>
>>>
>>> Thanks,
>>>
>>> --
>>> Jiri Kosina
>>> SUSE Labs
>
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2014-03-05 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 0:20 [PATCH 0/4] HID: ll transport cleanup: final round Benjamin Tissoires
2014-03-01 0:20 ` [PATCH 1/4] HID: cp2112: remove various hid_out_raw_report calls Benjamin Tissoires
2014-03-01 0:20 ` [PATCH 2/4] HID: cp2112: remove the last hid_output_raw_report() call Benjamin Tissoires
2014-03-04 13:46 ` Jiri Kosina
2014-03-04 14:18 ` Benjamin Tissoires
2014-03-04 14:21 ` Jiri Kosina
[not found] ` <ba12abe9-5f40-4351-8dc0-76008931fc0d@email.android.com>
2014-03-05 21:09 ` Benjamin Tissoires [this message]
2014-03-01 0:20 ` [PATCH 3/4] HID: sony: do not rely on hid_output_raw_report Benjamin Tissoires
2014-03-01 12:16 ` Antonio Ospite
2014-03-03 14:28 ` Benjamin Tissoires
2014-03-01 0:20 ` [PATCH 4/4] HID: remove hid_output_raw_report transport implementations Benjamin Tissoires
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN+gG=FOzo90DbMqp-Dh-OF4oCuBzXC-nwODPkNk62CV_usDxQ@mail.gmail.com' \
--to=benjamin.tissoires@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dbarksdale@uplogix.com \
--cc=dh.herrmann@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).