[roll] Roll fuchsia [kernel] InitInterrupt take enable_interrupt_callback

To match previous implementations order of operations,
InitInterrupt takes a callback that is in charge of unmasking the irq
the device is assigned to.

The main purpose is to match the legacy driver operation sequence
as much as possible. See fxbug.dev/129378 for details on a tracking
bug for revisiting this decision after migration is complete.

Original-Bug: 126785
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/854018
Original-Revision: 3d0b63e2dcd958ca8f92b6479872ac47807fa5c4
GitOrigin-RevId: 01f210549c43aa4deb8c66c4033d3ec0d083859d
Change-Id: Ia41f6973058da21225d236ec554b12387a4146be
1 file changed
tree: b99252f9fa187ad6d92343739c781edce48dc308
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.