public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001676] New: SPI cyg_spi_transaction_tick: Discrepancy between documentation and Date: Mon, 24 Sep 2012 09:34:00 -0000 [thread overview] Message-ID: <bug-1001676-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001676 Summary: SPI cyg_spi_transaction_tick: Discrepancy between documentation and Product: eCos Version: CVS Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: low Component: SPI AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: ilijak@siva.com.mk CC: ecos-bugs@ecos.sourceware.org Class: Advice Request There is a discrepancy between Reference Manual (RM) and implementation of most SPI drivers regarding SPI chip select behaviour during cyg_spi_tick. The SPI part of RM states (underlines by reporter): "... If the device requires additional clock ticks in the middle of a transaction without being selected, cyg_spi_transaction_tick can be used. _This_will_drop_the_device's_chip_select_if_necessary, then generate the appropriate number of ticks. The arguments are the same as for cyg_spi_tick. ..." And about cyg_spi_tick: "... These ticks must happen at the appropriate clock rate _but_no_chip_select_should_be_asserted_ and no data transfer will happen. cyg_spi_tick provides this functionality. ..." Contrary to this, most of the actual drivers do not touch the chip selects. Ilija -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-09-24 9:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-24 9:34 bugzilla-daemon [this message] 2012-09-24 9:34 bugzilla-daemon
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=bug-1001676-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.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: linkBe 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).