Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@samtertzakian I created this PR to keep track of my feedback.
HID definition refactoring
I think the HID definitions can be shared between the HID mini module and the VHF module (f9fdf98)
Timer code in generic module
I'm not sure the timer code is needed in the generic
Dmf_VirtualHidDeviceMini
module. The timer is used to simulate incoming data, and other drivers would have their own data generation.From the sample intro documentation:
Personally I would move that timer logic to the sample module, and only have a function like
GenerateInputReport
that roughly looks like below in the genericDmf_VirtualHidDeviceMini
module. That function can then probably be called from the sample module?If both the timer logic (to cleanup outstanding queue requests?) and a manual report generation function are needed, then it is my misunderstanding.