/** * This file is part of license combination gpl version 3 license and eCos. * The corresponding license terms are below. * * gpl version 3 Licence: * * The file were developed during the student thesis "Datensammlung in Wireless * Sensor Networks fuer Autonomic Home NetworkingÒ of Thomas Kothmayr and is * included in the dissertation "Secure Data Transmission in Wireless * Sensor Networks" by Corinna Schmitt during employment at the Technische * UniversitŠt MŸnchen, Department Computer Science, Chair Network * Architectures and Services (Germany). * Copyright (C) 2013 * Authors: Thomas Kothmayr and Corinna Schmitt (schmitt[at]net.in.tum.de) * * This program is free software: you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation, version 3 of the License * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program. If not, see . * * * eCos Licence: (http://ecos.sourceware.org) * * This file is part of eCos, the Embedded Configurable Operating System. * Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, * 2007, 2008, 2009 Free Software Foundation, Inc. * * eCos is free software; you can redistribute it and/or modify it under * the terms of the GNU General Public License as published by the Free * Software Foundation; either version 3 any later version. * * eCos is distributed in the hope that it will be useful, but WITHOUT ANY * WARRANTY; without even the implied warranty of MERCHANTABILITY or * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for * more details. * * You should have received a copy of the GNU General Public License along * with eCos; if not, write to the Free Software Foundation, Inc., 51 * Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. * * As a special exception, if other files instantiate templates or use * macros or inline functions from this file, or you compile this file and * link it with other works to produce a work based on this file, this file * does not by itself cause the resulting work to be covered by the GNU * General Public License. However the source code for this file must still * be made available in accordance with section (3) of the GNU General * Public License v2. * * This exception does not invalidate any other reasons why a work based on * this file might be covered by the GNU General Public License. * */ Interface: tos.chips.rf230.Tasklet

Interface: tos.chips.rf230.Tasklet

interface Tasklet

This interface is useful in building state machines when the state transitions should be executed atomically but with interrupts enabled. All state transitions should take place in the run event handler or in blocks protected by the suspend and resume commands.

Commands
command void resume() Leaves the critical section.
command void schedule() Makes sure that the run event is called at least once more.
command void suspend() Enters a critical section of the code and meakes sure that the run event is not called while in this section.

Events
event void run() This method is executed atomically.

Commands - Details

resume

command void resume()

Leaves the critical section. This call is conly possible from task context. If there were scheduled executions of the run event, then those will be called before this command returns.

schedule

command void schedule()

Makes sure that the run event is called at least once more. If the run event is currently not executing, then it is called immediately and this command returns only after the completion of the run event. If the run event is currently executed, then this method returns at once, and makes sure that the run event is called once more when it is finished. If this method is called from a task, then by the above rules, the run event will be called from a task as well.

suspend

command void suspend()

Enters a critical section of the code and meakes sure that the run event is not called while in this section. No long running computation should be called from the critical session, and in particular no user event should be fired. This call is only possible from task context, otherwise we cannot guarantee that the run event is not currently running. The suspend calls can be nested. It is very important that the same number of resume commands must be called in all control paths, e.g. be very careful with the return and break commands.

Events - Details

run

event void run()

This method is executed atomically.