[roll] Roll fuchsia [usb-keys] Add driver level stubs for security keys

Checking in hid-driver if HID device has any security key capabilities.
If it does, hid-driver will expose the fuchsia.hid.SecurityKey bind
property causing the ctaphid driver to bind. If not, hid-driver will
expose fuchsia.hid.SecurityKey bind property as false and will bind to
hid-input-report driver.

Add ctaphid driver which surfaces to /dev/class/ctap. Functions in
ctaphid.cc need to be filled out. Tests should be written in test.cc.

Original-Bug:100522

Test: tested that HID devices still work on Atlas
      tested that security key shows up on Atlas as /dev/class/ctap

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/686368
Original-Revision: 29e8761ac7f473e9a5af32787a0689fc5a760380
GitOrigin-RevId: 8b7fcfe927b0706b7f340b989a0d99166ca4857c
Change-Id: I55fc8a5e6d46ebe2e59ff4ac6db8b3f1c25b184f
1 file changed
tree: 382e21b4e528fb0a2c625c58365adcdc20c96a43
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.