Hi Vipul,
On Tue, Oct 09, 2018 at 12:01:46PM -0700, Vipul Rahane wrote:
> Sorry for the late reply.
No problem!
> I really like the idea. Thank you for doing this Chris. A much needed
> feature. A possible use case just came to my mind.
>
> One module might have to be shutdown before shutting
Hey,
Sorry for the late reply. I really like the idea. Thank you for doing this
Chris. A much needed feature. A possible use case just came to my mind.
One module might have to be shutdown before shutting down others for example:
Sensors using I2C/SPI would have to be shut down before shutting
Hi Martin,
On Fri, Sep 28, 2018 at 04:30:17PM -0700, Martin Turon wrote:
> +1 for graceful shutdown.
>
> It could also be useful for coarse, multi-protocol use cases such as using
> BLE for commissioning, shutting down that stack, and then starting a 15.4
> stack such as Thread.
>
> In general,
+1 to the idea of being able to handle this at the module/package level to
subscribe to 'shutdown' or 'sleep' events. The package level is the right
place to handle this since the package itself is aware of the transport
being used for drivers (I2C/SPI/etc.), and the pins that can be switched to
Hi Chris,
The overall idea looks good to me. I just have some suggestions as below.
On Sat, Sep 29, 2018 at 1:37 AM Christopher Collins
wrote:
> On Fri, Sep 28, 2018 at 04:18:08PM -0700, will sanfilippo wrote:
> > Some comments:
> >
> > 1) Are there are any other cases you can see for a
On Fri, Sep 28, 2018 at 04:18:08PM -0700, will sanfilippo wrote:
> Some comments:
>
> 1) Are there are any other cases you can see for a controlled shutdown? I get
> the reset command. I am trying to think of others.
I think the newtmgr reset command is the main use case (as well as the
shell
+1 for graceful shutdown.
It could also be useful for coarse, multi-protocol use cases such as using
BLE for commissioning, shutting down that stack, and then starting a 15.4
stack such as Thread.
In general, it would be great if nimble could support high level stack
start / stop commands such
Some comments:
1) Are there are any other cases you can see for a controlled shutdown? I get
the reset command. I am trying to think of others.
2) I am curious: how do you know how many of these functions, or which ones,
return in progress? Curious to know how you were going to implement that