[roll] Roll fuchsia [fdf][i2c] Migrate i2c clients to service capability

The i2c core driver already exports both the service capability as well
as the protocol capability. This change switches clients to go through
the service capability instead. Because most clients go through the
ddk::I2cChannel class to connect, most drivers don't require any code
changes, only component manifest updates to reflect the new service they
require, and unit test update for connecting to the parent's i2c
protocol.

Additionally all drivers using the i2c protocol were updated to no
longer colocate with their parent.

Tested: device-enumeration-test
Original-Bug: 116476
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/783827
Original-Revision: 9079fef7f8c9cc6b550feb40bd527c4a5502084b
GitOrigin-RevId: 6016952edfe307e66cd325c4844444b58a308245
Change-Id: Ia8269d459a291578bac097e688867ca766aa9c4a
1 file changed
tree: 773d970540ec2543d7a3c7b052c78cb804728e65
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.