roll: pigweed, pw_toolchain: pw_async2_epoll: Use unordered_map; silence persistent warnings

Rather than adding and removing read and write wakers to a vector, use
an unordered_map that maps a file descriptor to read and write wakers.

Also, silence unnecessary warning logs. Previously, epoll dispatcher
frequently emitted these warnings:

  WRN Received an event for registered file descriptor 4, but there is
      no task to wake

This warning would occur with every read. This is because epoll emits
both EPOLLIN and EPOLLOUT events when reading from a read/write channel,
resulting in unhandled write events, even though no tasks are trying to
write.

Retain the log as a debug-level log, and only trigger it if no tasks
were waiting for either reads or writes.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218860
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 8b8ad3820dff2e6..62da50a4f4cb9b5
Roller-URL: https://ci.chromium.org/b/8743842911817085377
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I5b07921a19ed1603c76378eaaf46e885e283e332
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218785
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 3be03a9355b3d5eec83550ffc4b5db2b033016ff
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

git clone --recursive https://pigweed.googlesource.com/pigweed/quickstart/bazel

If you already cloned but forgot to include --recursive, run git submodule update --init to pull all submodules.

TODO: b/300695111 - Don't require submodules for this example.

Building

We‘ll assume you already have Bazel on your system. If you don’t, the recommended way to get it is through Bazelisk.

To build the entire project (including building the application for both the host and the STM32 Discovery Board), run

bazel build //...

To run the application locally on your machine, run,

bazel run //src:echo

Flashing

To flash the firmware to a STM32F429 Discovery Board connected to your machine, run,

bazel run //tools:flash

Note that you don't need to build the firmware first: Bazel knows that the firmware images are needed to flash the board, and will build them for you. And if you edit the source of the firmware or any of its dependencies, it will get rebuilt when you flash.

Communicating

Run,

bazel run //tools:miniterm -- /dev/ttyACM0 --filter=debug

to communicate with the board. When you transmit a character, you should get the same character back!