Answer by Anil Sagar @ Google
·
Jun 22, 2015 at 11:57 AM
Dear @rashmi badadale ,
A zetta custom device driver / zetta device driver can be defined as follows,
Zetta drivers can be contributed back to the community, those drivers are called as Contributed Zetta Device Drivers. If a zetta driver for a specific platform is not available in the community then you will write a driver yourself for your needs, those drivers can be called as custom zetta device drivers.
For more information related to zetta driver see articles Anatomy of a Zetta Driver and Zetta Device Reference Docs.
Cheers,
Anil Sagar
Hi @Anil Sagar ,
Thanks for the detailed explanation.
Can I say the Zetta Driver will expose the "core" capabilities of the device as APIs ?
With specifically LED Driver, I was expecting only "on" and "off" operations exposed by drivers keeping the duration as additional configurable param. The Apps may create other combinations as per their requirements anyway.
So, my targeted question is -- Do we provide more featureful drivers or keep it to the core of the devices only ?
@Ravi Shah , That's correct. You can provide more featureful drivers not only specific to the core of the devices. For Example, You can provide features like pulse, turn-on-alternative, flash as additional APIs on top of simple on-off for an LED.
You can implement additional features along with core features in a device driver and expose same as an API.