tree 52420e772d1b1f3c363571ef5246b5244ccf8246
parent d0405c3555427c03b231c8d52958f8689b3fa114
author Manojkiran Eda <manojkiran.eda@gmail.com> 1646291214 +0530
committer Manojkiran Eda <manojkiran.eda@gmail.com> 1646291659 +0530

Allow OEM Effecters & Sensors leverage json infrastructure

In the current flow, if the entity type is in the OEM range,
then in both the getStateSensorReadings & setStateEffecter handler
flow, we would trigger the oem functions rather than the generic
functions (which handles the PDR's in json format) - while this gives
a seperated infrastructure, this would also limit us from using the
json infrastructure for OEM entities.

This fix would basically allow defining the OEM entities in the standard
PDR json files, and also allow us to seperate out a new 11.json & 4.json
into the oem/ configuration folders.

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I41c771f07b0cc7879488cb9c475d90cdb845ed4c