[roll] Roll fuchsia [devicetree][i2c] Allow for multiple I2C peripheral addresses in `reg`.

Previously the devicetree visitor only supported `i2c` child nodes
with one `reg` entry. However, some devices may need access to
multiple I2C peripherals on a single bus. This change adds support
for multiple I2C peripheral addresses in the `reg` field of the
child node; The created composite device will have multiple I2C nodes,
each of which stands for an individual I2C channel.

Other OSes also support multiple I2C `reg`s in their devicetree
implementations. For example, Linux devicetree `i2c` node documentation
(https://www.kernel.org/doc/Documentation/devicetree/bindings/i2c/i2c.txt)
mentions that:

> - reg
>   One or many I2C peripheral addresses.

Original-Bug: 358395787
Test: i2c-bus-visitor-test
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1105482
Original-Revision: 71d5a3e85020d17c41c4a4447fb64c1ebb42ff9b
GitOrigin-RevId: 0cab8c85ec0697626a4a52072dbb7814310fdf95
Change-Id: Ibf0c9fcb015e40774f2ff7452303ddc3a55065e4
1 file changed
tree: a48f1678922be0fdff33b4fb0395383054c5c4dc
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.