From: Bart Veer <bartv@ecoscentric.com>
To: ecos-patches@sourceware.org
Subject: SPI subsystem update
Date: Mon, 09 Feb 2009 23:06:00 -0000 [thread overview]
Message-ID: <pniqnjdxd5.fsf@delenn.bartv.net> (raw)
A couple of the CDL descriptions mentioned the generic serial package
instead of SPI. There was a typo in the documentation. I have also
added a mention of CYG_INIT_BUS_SPI priority.
Bart
2009-02-09 Bart Veer <bartv@ecoscentric.com>
* cdl/spi.cdl: fix descriptions in the CFLAGS_ADD and
CFLAGS_REMOVE options
* doc/spi.sgml: fix typo. Mention CYG_INIT_BUS_SPI priority.
Index: doc/spi.sgml
===================================================================
RCS file: /cvs/ecos/ecos/packages/io/spi/current/doc/spi.sgml,v
retrieving revision 1.2
diff -u -p -r1.2 spi.sgml
--- doc/spi.sgml 29 Jan 2009 17:49:48 -0000 1.2
+++ doc/spi.sgml 9 Feb 2009 23:04:52 -0000
@@ -203,8 +203,8 @@ extra functions in the platform HAL.
<para>
Typically all appropriate packages will be loaded automatically when
you configure eCos for a given target. If the application does not use
-of the SPI I/O facilities, directly or indirectly, then linker garbage
-collection should eliminate all unnecessary code and data. All
+any of the SPI I/O facilities, directly or indirectly, then linker
+garbage collection should eliminate all unnecessary code and data. All
necessary initialization should happen automatically. However the
exact details may depend on the target, so the platform HAL
documentation should be checked for further details.
@@ -689,7 +689,8 @@ Create a HAL table for the devices attac
<listitem><para>
Arrange for the bus to be initialized early on during system
initialization. Typically this will happen via a prioritized static
-constructor. As part of this initialization the bus driver should
+constructor with priority <literal>CYG_INIT_BUS_SPI</literal>.
+As part of this initialization the bus driver should
invoke the <function>CYG_SPI_BUS_COMMON_INIT</function> macro on its
<structname>cyg_spi_bus</structname> field.
</para></listitem>
Index: cdl/spi.cdl
===================================================================
RCS file: /cvs/ecos/ecos/packages/io/spi/current/cdl/spi.cdl,v
retrieving revision 1.4
diff -u -p -r1.4 spi.cdl
--- cdl/spi.cdl 29 Jan 2009 17:49:48 -0000 1.4
+++ cdl/spi.cdl 9 Feb 2009 23:05:31 -0000
@@ -58,15 +58,13 @@ cdl_package CYGPKG_IO_SPI {
attached to an SPI bus. It also provides support for writing
bus drivers and for defining SPI device structures."
-
cdl_component CYGPKG_IO_SPI_OPTIONS {
display "SPI build options"
flavor none
description "
Package specific build options including control over
- compiler flags used only in building this package,
- and details of which tests are built."
-
+ compiler flags used only in building the generic SPI
+ package, and details of which tests are built."
cdl_option CYGPKG_IO_SPI_CFLAGS_ADD {
display "Additional compiler flags"
@@ -75,8 +73,8 @@ cdl_package CYGPKG_IO_SPI {
default_value { "" }
description "
This option modifies the set of compiler flags for
- building the serial device drivers. These flags are used in addition
- to the set of global flags."
+ building the generic SPI package. These flags are
+ used in addition to the set of global flags."
}
cdl_option CYGPKG_IO_SPI_CFLAGS_REMOVE {
@@ -86,8 +84,8 @@ cdl_package CYGPKG_IO_SPI {
default_value { "" }
description "
This option modifies the set of compiler flags for
- building the serial device drivers. These flags are removed from
- the set of global flags if present."
+ building the generic SPI package. These flags are
+ removed from the set of global flags if present."
}
}
}
reply other threads:[~2009-02-09 23:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pniqnjdxd5.fsf@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=ecos-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).