[roll] Roll fuchsia [board][vim3-devicetree] Add I2C child node for vim3 MCU

Add a single I2C child node so that the I2C core driver is able to
initialize. Use the vim3 MCU I2C device, as it has no dependencies on
other drivers.

Also add pinctrl properties to set the pinmux functions for I2C pins,
similar to what is done manually in the regular vim3 board driver. This
allows aml-i2c to bind.

Test: device-enumeration-test
Cq-Include-Trybots: luci.fuchsia.try:bringup.vim3-devicetree-debug
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1014601
Original-Revision: 894633f89618e50fa21f3715cbf48d6c7438d07d
GitOrigin-RevId: 9f1796be412f08e1b2344ac0a7f3d7f0c1c6e2b5
Change-Id: Ibf1676f698f78981d641e1c34e88f6992d385465
1 file changed
tree: 82dd387b3206fbb9ba1ed778c2905cb6e0df4cf4
  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.