v2023110000.0.6

What's Changed

• Relax report length requirements @joschock (#455)
  
  Change Details

    ## Description

  This PR brings in two fixes to support a wider variety of devices, some of which might not be completely self-consistent:

  • Allow report lengths that don't match the report descriptor. Reports that are shorter than the Report Descriptor specifies will be processed for whatever fields are fully present. Reports that are longer than the Report descriptor specifies will simply ignore the extra bytes in the report.
  • Move away from using signal_event to force keyboard layout initialization, and install call the layout change routine directly. This avoids introducing sequencing issues based on the TPL that the keyboard is being initialized at, resulting in more deterministic behavior.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  Rust unit tests updated to cover new functionality all pass. Functional testing on hardware with the changes also passes.

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

📖 Documentation Updates

• Moving the global variable from header file into library instances @kuqin12 (#473)
  
  Change Details

    ## Description

  The current implementation of instantiating global variables will make each c file that includes this header to carry a copy of such variable, which is space redundant.

  This change removed the variable into the single module that uses it and removed the structure it defines. The function descriptions are also updated.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  This is a non-functional change.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023110000.0.5...v2023110000.0.6