Hi,

> To better understand this - can you elaborate on what influences these
> properties in Murphy? By that I mean what trigger events push each of
> these properties into their various states?

For the two properties I mentioned, both do have algorithms for the
calculation of the values from the basic properties. At the moment the
algorithms are simple -- NightMode, for instance, is calculated based on
an exterior brightness threshold value. However, in finalized products,
the algorithm can be much more complex. For example NightMode needs some
sort of hysteresis to prevent oscillation of the mode in case the
vehicle is driving under street lighting or other variable lighting
conditions. The algorithm may also take into account car interior
lighting and possibly even vehicle position and current time.

> Can you elaborate on the boot sequence order here? 
> Will AMB be fully functional before Murphy awakes? 
> 
> An example - if I park my vehicle last night (NightMode = true),
> and I return in the morning at day-break, does Murphy need to be
> up and running, observe the correct Nightmode value, pass it to
> AMB, which then raises the state change for the HMI to correctly
> adjust the user backlighting experience ]

AMB and Murphy startups are not depending of each other -- both
components will notice when one goes away and comes back up. Murphy will
fetch the properties it is interested in and tell AMB the current
statuses of the properties it controls when it notices AMB coming back
online. It goes without saying that if AMB is not running, no AMB
properties can be delivered, and if Murphy is not running, it cannot
calculate values for the properties it controls. In that sense the
dependency between the two components is very weak.

> Finally - could you explain the concurrency model in AMB - I'd like
> to understand the threading model better, specifically around having
> multiple clients delivering inbound events at various frequencies,
> normalising these to a standard interface and then potentially delivering
> these to  various consumers... 

I haven't looked into these parts of AMB code, so I can't really comment
on this.

-- 
Ismo Puustinen <[email protected]>
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi

Reply via email to