What does this particular "flag" do in the mesh example?

RE: What does this particular "flag" do in the mesh example?

Hung Bui — Tue, 28 Nov 2017 14:55:51 GMT

You are correct. Mainly, when we don't want to execute a function immediately, for example if we are in high priority context (handler of high priority interrupt) we don't want to do time consuming operation (flash operation for example) or if it that operation should be executed in lower priority context, we will just set the flag on. And it will be executed later when handle_events() is called, in lower priority context.

RE: What does this particular "flag" do in the mesh example?

Mitch996 — Tue, 28 Nov 2017 01:55:29 GMT

Thanks Hung. Although not 100%, I think I know what it does.

You have a series of events that comes with 2 critical components (among other components): one of them is callbacks (of course), which will perform specific tasks based on the nature of the event.

Another critical component is flag. This flag will be set to a specific value to decide whether its corresponding event will be executed or when and how etc. it will be executed.

In other words, sometimes an event has been added, but we do not want to respond to it immediately, we look at its flag to decide what to do with it.

Is that how it works?

I'm not planning on doing anything about it hehe, I just want to know exactly how it works.

RE: What does this particular "flag" do in the mesh example?

Hung Bui — Mon, 27 Nov 2017 13:02:44 GMT

Hi Mitch,

What exactly do you plan do to with the flags ?

The flags used in our stack is kind of event flags. So a module can register an event handler and set a flag to trygger the event handler asynchronously. Something similar to this.

We use it in several modules: scanner.c , flash_manager.c

The flags have been set will be executed inside handle_events() in bearer_event.c one by one.