Fix STM32 F2/F4 SDIO clocking; Clean-up files in sched/ directory

git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4940 7fd9a85b-ad96-42d3-883c-3090e2eb8679
This commit is contained in:
patacongo
2012-07-14 19:30:31 +00:00
parent 876ffbd29f
commit 4ea9aa3ff1
204 changed files with 2197 additions and 1635 deletions
+19 -25
View File
@@ -2,7 +2,7 @@
* sched/pthread_keycreate.c
*
* Copyright (C) 2007-2009 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <spudmonkey@racsa.co.cr>
* Author: Gregory Nutt <gnutt@nuttx.org>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
@@ -70,45 +70,39 @@
****************************************************************************/
/****************************************************************************
* Function: pthread_key_create
* Name: pthread_key_create
*
* Description:
* This function creates a thread-specific data key visible
* to all threads in the system. Although the same key value
* may be used by different threads, the values bound to
* the key by pthread_setspecific() are maintained on a
* per-thread basis and persist for the life of the calling
* This function creates a thread-specific data key visible to all threads
* in the system. Although the same key value may be used by different
* threads, the values bound to the key by pthread_setspecific() are
* maintained on a per-thread basis and persist for the life of the calling
* thread.
*
* Upon key creation, the value NULL will be associated with
* the new key in all active threads. Upon thread
* creation, the value NULL will be associated with all
* defined keys in the new thread.
* Upon key creation, the value NULL will be associated with the new key
* in all active threads. Upon thread creation, the value NULL will be
* associated with all defined keys in the new thread.
*
* Parameters:
* key = A pointer to the key to create.
* destructor = An optional destructor() function that may
* be associated with each key that is invoked when a
* thread exits. However, this argument is ignored in
* the current implementation.
* destructor = An optional destructor() function that may be associated
* with each key that is invoked when a thread exits. However, this
* argument is ignored in the current implementation.
*
* Return Value:
* If successful, the pthread_key_create() function will
* store the newly created key value at *key and return
* zero (OK). Otherwise, an error number will be
* returned to indicate the error:
* If successful, the pthread_key_create() function will store the newly
* created key value at *key and return zero (OK). Otherwise, an error
* number will bereturned to indicate the error:
*
* EAGAIN - The system lacked sufficient resources
* to create another thread-specific data key, or the
* system-imposed limit on the total number of keys
* pers process {PTHREAD_KEYS_MAX} has been exceeded
* EAGAIN - The system lacked sufficient resources to create another
* thread-specific data key, or the system-imposed limit on the total
* number of keys pers process {PTHREAD_KEYS_MAX} has been exceeded
* ENONMEM - Insufficient memory exists to create the key.
*
* Assumptions:
*
* POSIX Compatibility:
* - The present implementation ignores the destructor
* argument.
* - The present implementation ignores the destructor argument.
*
****************************************************************************/