media/gpu/v4l2: Support mainline Linux device paths

Upstream Linux does not use the ChromeOS-specific device path patterns
for "-dec", "-enc" etc. Add support for the respective mainline patterns
in order to improve HW de-/encoding support.

This crucially requires us to enumerate a lot of /dev/video* devices, as
it has become common for SoCs to have >100 of them - usually most of
them used for ISPs. Unfortunately enumerating many devices - even
non-existing ones, as we don't know ahead of time in sandboxed
environments - is not free. Using 256 takes roughly 30-60ms on platforms
like RK3399 or MT8390 respectively, while raising the number to e.g.
1024 would take it to >100ms, and was therefor used as solid limit.

Given that the increased time cost only applies to non-ChromeOS Linux
with `use_v4l2_codec` enabled, the tradeoff is likely justified, as
chances are high that affected platforms do support HW-decoding in a lot
of cases and profit a lot from using it.

The change here is enough to make HW video decoding work on various
stacks, with both stateful and stateless V4L2.

Note that similar places used in tests or with the experimental
`V4L2FlatStatefulVideoDecoder` feature where left out for now.

Bug: b:334110478
Change-Id: I9ea18aef05502c7796a61dcf15b13edc27845cd0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5872600
Reviewed-by: Fritz Koenig <frkoenig@chromium.org>
Reviewed-by: Ted (Chromium) Meyer <tmathmeyer@chromium.org>
Reviewed-by: Nathan Hebert <nhebert@chromium.org>
Commit-Queue: Nathan Hebert <nhebert@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1368857}
3 files changed
tree: 9ed997930e548ae19f34a06e68ad7e65fde50cf8
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. google_update/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.