linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Marco Morandini <marco.morandini@polimi.it>,
	Peter Hutterer <peter.hutterer@who-t.net>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] HID: Add introduction about HID for non-kernel programmers
Date: Fri, 23 Jun 2023 08:16:15 -0700	[thread overview]
Message-ID: <f53e756f-7c81-1c79-23ea-b9009fdd2ef4@infradead.org> (raw)
In-Reply-To: <45d68dcb-7625-8592-fde6-60c9fbd5eaca@polimi.it>

Hi Marco,

On 6/23/23 03:45, Marco Morandini wrote:

>>> +The format of HID report descriptors is described by two documents,
>>> +available from the `USB Implementers Forum <https://www.usb.org/>`_
>>> +at `this <https://www.usb.org/hid>`_ addresses:
>>
>>        these
> 
> Not sure about this.
> "this" here was meant to be https://www.usb.org/hid , while the two documents are listed below.
> 
> Would 
> 
> The format of HID report descriptors is described by two documents,
> available from the `USB Implementers Forum <https://www.usb.org/>`_
> `HID web page <https://www.usb.org/hid>`_:
> 
> be ok?

Yes, that's good.

>>> +    # 0x81, 0x02, 		     //	Input (Data,Var,Abs)		   24
>>> + it's actual Data (not constant padding), they represent 
>>
>>     its
>> ?
>> "its" is possessive. "it's" means "it is".
>>
> 
> -> these bits are actual data 
> 
> ok?

Yes.

>>> + This time the data is Relative (Rel), i.e. it represent 
>>
>>                                                   represents
>>
>>> +An HID devices can have Input Reports, like
>>
>>    A HID device
>>
> 
> -> HID devices that are not ....
> 
> as suggested by Peter
> Ok?

Sure.


thanks.
-- 
~Randy

  reply	other threads:[~2023-06-23 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22 20:39 [PATCH v2] HID: Add introduction about HID for non-kernel programmers Marco Morandini
2023-06-23  4:32 ` Randy Dunlap
2023-06-23 10:45   ` Marco Morandini
2023-06-23 15:16     ` Randy Dunlap [this message]
2023-06-27  6:04 ` Peter Hutterer
2023-06-28 13:37   ` Marco Morandini
2023-07-10  2:10     ` Peter Hutterer
2023-07-13 14:36       ` Marco Morandini
2023-07-17  0:15         ` Peter Hutterer
2023-07-17 16:38           ` Marco Morandini

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=f53e756f-7c81-1c79-23ea-b9009fdd2ef4@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=corbet@lwn.net \
    --cc=jikos@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=marco.morandini@polimi.it \
    --cc=peter.hutterer@who-t.net \
    /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).