Vendor Interface Object

From f16c42333aa6b2de30a344dd68246d4a33d93e7d Mon Sep 17 00:00:00 2001 From: Android Partner Docs Date: Tue, 22 Aug 2017 10:41:24 -0700 Subject: Docs: Changes to source.android.com - 166080694 Devsite localized content from translation request a3d5a7... by Android Partner Docs - 166079245 Remove duplicate TOC entry to oob-users.html. by mheco - 166002955 Update builds for Oreo by Android Partner Docs - 165977566 Fixing bad conversion by hvm - 165977199 Edit links to point to public source files in AOSP. by cqn - 165962883 Add codename to CTS downloads page. by gdimino - 165955117 Integration of O branch into mainline. by gdimino - 165638251 Update July public Android security bulletin to remove QC... by Android Partner Docs - 165638198 Update June public Android security bulletin to remove QC... by Android Partner Docs - 165638174 Update May public Android security bulletin to remove QC ... by Android Partner Docs - 165638096 Update April public Android security bulletin to remove Q... by Android Partner Docs - 165528993 Update to Keymaster 2 and remove requirements language by daroberts - 165511119 Add Bluetooth verification / debug information by cqn - 165491345 Fixed link broken by file rename. by cqn - 165381648 Fixed broken image paths and renamed HCI Requirements file. by cqn - 165365185 Created high-level Bluetooth directory and added HTML ver... by cqn - 165335694 Devsite localized content from translation request 66a39c... by Android Partner Docs - 165246927 Update August 2017 bulletin with CVE-2017-0687 by daroberts PiperOrigin-RevId: 166080694 Change-Id: I2d3a8d77fa6a66c2099f13ba2e864545328fd17a --- en/devices/architecture/vintf/index.html | 113 +++++++++++++++++++++++++++++++ 1 file changed, 113 insertions(+) create mode 100644 en/devices/architecture/vintf/index.html (limited to 'en/devices/architecture/vintf/index.html') diff --git a/en/devices/architecture/vintf/index.html b/en/devices/architecture/vintf/index.html new file mode 100644 index 00000000..b0517a32 --- /dev/null +++ b/en/devices/architecture/vintf/index.html @@ -0,0 +1,113 @@ + + + Vendor Interface Object + + + + + + +

This document describes the design of the vendor interface object +(VINTF object), which aggregates relevant information about a device and makes +that information available through a queryable API.

+ + +

VINTF object design

A VINTF object gathers some of the information it needs directly from the +device. Other aspects, such as the manifests, are described statically in +XML.

+ +

Figure 1. Manifests, compatibility matrices, and +runtime-collectible information.

+ +

VINTF object design provides the following for device and framework +components:

+ + + + + + + + + + +

For the Device	For the Framework
+ + Defines a schema for the static component (the +device +manifest file). + Adds build time support for defining the device manifest file for a given +device. + Defines the +queryable +API at runtime that retrieves the device manifest file (along with the other +runtime-collectible information) and packages them into the query result. + +	+ + Defines a schema for the static component (the +framework +manifest file). + Defines the +queryable +API at runtime that retrieves the framework manifest file and packages it +into the query result. + +

+ +

The VINTF object must be reliable and provide the same complete information +regardless of when the object is requested (see +Caveats).

+ +

Manifests & matrices

Android O requires an API at runtime to query what is on the device and send +that information to the Over-the-Air +(OTA) update server and other interested parties (such as CTS +DeviceInfo). Some information is retrieved at runtime and some of +it is statically-defined.

+ +

The device manifest describes the static component of what +the device can provide to the the framework.
The framework compatibility matrix describes what the +Android framework expects from a given device. The matrix is a static entity +whose composition is determined manually during development of the next release +of the Android framework.
The framework manifest describes high-level services the +framework can provide to the device.
The device compatibility matrix describes the services the +vendor image requires of the framework. Its composition is determined manually +during the development of the device.

+ +

These two pairs of manifests and matrices must be reconciled at OTA time to +ensure a device can get framework updates that are compatible with the device's +capabilities. In general, a manifest describes what is provided and a +compatibility matrix describes what is required.

+ +

VINTF Object Data +defines the schema for the manifest, +Compatibility +Matrices defines the schema for the compatibility matrix, and +Matching Rules +defines the rules for a successful match between a compatibility matrix +and a manifest.

+ + + -- cgit v1.2.3