android_system_core/trusty/keymaster/4.0/android.hardware.keymaster@...

<manifest version="1.0" type="device">
    <hal format="hidl">
        <name>android.hardware.keymaster</name>
        <transport>hwbinder</transport>
        <fqname>@4.0::IKeymasterDevice/default</fqname>
    </hal>
</manifest>
Provide VINTF for Trusty Keymaster This makes it easier to add or remove the Trusty keymaster service from a device by providing a manifest fragment to add whenever it is enabled. Test: Keymaster VTS, Keystore CTS (sans attestation) Change-Id: Ib0f5fd7c016c0c18d77c9d2623c89f3b35ba7ad7 2019-08-26 17:47:51 +00:00			`<manifest version="1.0" type="device">`
			`<hal format="hidl">`
			`<name>android.hardware.keymaster</name>`
			`<transport>hwbinder</transport>`
Use <fqname> to avoid conflicts The newer way of specifying the interface is using <fqname> and it also has the handy side-effect of not causing conflicts when we add the strongbox implementation to devices. Test: make # check $OUT for the correct manifest Change-Id: If8333814723261c4f3de375861ee19a6d922d55f 2020-04-14 21:18:30 +00:00			`<fqname>@4.0::IKeymasterDevice/default</fqname>`
Provide VINTF for Trusty Keymaster This makes it easier to add or remove the Trusty keymaster service from a device by providing a manifest fragment to add whenever it is enabled. Test: Keymaster VTS, Keystore CTS (sans attestation) Change-Id: Ib0f5fd7c016c0c18d77c9d2623c89f3b35ba7ad7 2019-08-26 17:47:51 +00:00			`</hal>`
			`</manifest>`