From 6d9146901cd9503180ec272f5b3af12e08553277 Mon Sep 17 00:00:00 2001 From: gdisirio Date: Mon, 1 Jun 2009 19:50:42 +0000 Subject: git-svn-id: svn://svn.code.sf.net/p/chibios/svn/trunk@1007 35acf78f-673a-0410-8e92-d51de3d6d3f4 --- docs/src/main.dox | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/src') diff --git a/docs/src/main.dox b/docs/src/main.dox index d62ebda3e..f38920462 100644 --- a/docs/src/main.dox +++ b/docs/src/main.dox @@ -359,7 +359,7 @@ * @brief Abstract digital I/O ports. * @details This module defines an abstract interface for digital I/O ports. * Note that no code is present, I/O ports are just a set of macros that must - * be implemented by a low level I/O port driver.
+ * be implemented by an @ref IOPortsLLD.
* Currently the I/O ports interface does not handle physical port programming * like direction, pull up/down resistors etc. The interface only allows input * and output operations but this may change in future releases. @@ -367,10 +367,10 @@ * independent from the implementation logic. * *

Implementation Rules

- * In implementing an I/O port low level driver there are some rules that + * In implementing an @ref IOPortsLLD there are some rules/behaviors that * should be respected. * - *

Write on input pads

+ *

Writing on input pads

* The behavior is not specified but there are implementations better than * others, this is the list of possible implementations, preferred options * are on top: @@ -381,7 +381,7 @@ * pull up/down resistors or changing the pad direction. This scenario is * discouraged, please try to avoid this scenario. * . - *

Read from output pads

+ *

Reading from output pads

* The behavior is not specified but there are implementations better than * others, this is the list of possible implementations, preferred options * are on top: -- cgit v1.2.3