public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001397] I2C driver for Kinetic microcontrollers Date: Tue, 25 Dec 2012 23:38:00 -0000 [thread overview] Message-ID: <20121225233756.96A9D4680014@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001397-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001397 --- Comment #31 from Mike Jones <mjones@linear.com> 2012-12-25 23:37:55 GMT --- I think that looping on bus ready is probably ok if there is a SMBus like timeout of 25ms to 30ms, and as long as the scheduler can break in switch tasks. If the wait can't be interrupted by the scheduler it is more problematic when the bus is stuck. A worst case scenario might have a task for ALERTB and one for telemetry. The second master hogs the bus and the first master is having trouble getting in. The the ALERTB comes along and needs immediate service. The ALERTB task may flip a GPIO bit and kill power, or it may wait for the timeout and then attempt to use the bus. All that matters to me is that it the driver waits for the bus to be free, times out, and allows a higher priority task do its job while waiting. I would not want it to just return because the bus is busy and force me to write my own timeout. And I would not want it to hang forever if a second master was beating the bus to death. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2012-12-25 23:38 UTC|newest] Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-01 13:44 [Bug 1001397] New: " bugzilla-daemon 2011-12-01 15:24 ` [Bug 1001397] " bugzilla-daemon 2011-12-01 15:48 ` bugzilla-daemon 2011-12-01 15:52 ` bugzilla-daemon 2011-12-01 15:59 ` bugzilla-daemon 2011-12-13 15:32 ` bugzilla-daemon 2011-12-23 10:41 ` bugzilla-daemon 2011-12-23 13:28 ` bugzilla-daemon 2011-12-23 14:14 ` bugzilla-daemon 2011-12-23 14:15 ` bugzilla-daemon 2011-12-24 9:22 ` bugzilla-daemon 2011-12-24 11:59 ` bugzilla-daemon 2011-12-26 7:32 ` bugzilla-daemon 2012-01-01 21:29 ` bugzilla-daemon 2012-01-11 20:33 ` bugzilla-daemon 2012-01-16 14:31 ` bugzilla-daemon 2012-02-07 20:38 ` bugzilla-daemon 2012-02-08 9:12 ` bugzilla-daemon 2012-02-08 9:55 ` bugzilla-daemon 2012-02-11 0:16 ` bugzilla-daemon 2012-02-11 10:14 ` bugzilla-daemon 2012-02-12 19:11 ` bugzilla-daemon 2012-02-12 19:11 ` bugzilla-daemon 2012-02-23 16:11 ` bugzilla-daemon 2012-03-20 15:17 ` bugzilla-daemon 2012-03-31 17:17 ` bugzilla-daemon 2012-05-04 18:17 ` bugzilla-daemon 2012-12-21 20:46 ` bugzilla-daemon 2012-12-24 9:52 ` bugzilla-daemon 2012-12-24 16:53 ` bugzilla-daemon 2012-12-24 16:54 ` bugzilla-daemon 2012-12-24 16:56 ` bugzilla-daemon 2012-12-24 16:56 ` bugzilla-daemon 2012-12-24 17:14 ` bugzilla-daemon 2012-12-24 17:38 ` bugzilla-daemon 2012-12-25 21:32 ` bugzilla-daemon 2012-12-25 21:33 ` bugzilla-daemon 2012-12-25 23:38 ` bugzilla-daemon [this message] 2012-12-26 15:06 ` bugzilla-daemon 2012-12-29 14:24 ` bugzilla-daemon 2013-01-02 3:48 ` bugzilla-daemon 2013-01-02 7:07 ` bugzilla-daemon 2013-01-03 9:09 ` bugzilla-daemon 2013-01-03 9:12 ` bugzilla-daemon 2013-01-03 16:28 ` bugzilla-daemon 2013-01-06 5:47 ` bugzilla-daemon 2013-03-02 18:08 ` bugzilla-daemon 2013-03-02 18:09 ` bugzilla-daemon 2013-04-10 20:34 ` bugzilla-daemon -- strict thread matches above, loose matches on Subject: below -- 2011-12-01 13:44 [Bug 1001397] New: " bugzilla-daemon 2011-12-01 15:24 ` [Bug 1001397] " bugzilla-daemon 2011-12-01 15:48 ` bugzilla-daemon 2011-12-01 15:52 ` bugzilla-daemon 2011-12-01 15:58 ` bugzilla-daemon 2011-12-13 15:13 ` bugzilla-daemon 2011-12-23 10:40 ` bugzilla-daemon 2011-12-23 13:28 ` bugzilla-daemon 2011-12-23 14:14 ` bugzilla-daemon 2011-12-23 14:15 ` bugzilla-daemon 2011-12-24 9:22 ` bugzilla-daemon 2011-12-24 11:59 ` bugzilla-daemon 2011-12-26 7:32 ` bugzilla-daemon 2012-01-01 21:29 ` bugzilla-daemon 2012-01-10 15:40 ` bugzilla-daemon 2012-01-11 20:33 ` bugzilla-daemon 2012-01-16 14:31 ` bugzilla-daemon 2012-02-07 20:38 ` bugzilla-daemon 2012-02-08 9:12 ` bugzilla-daemon 2012-02-08 9:55 ` bugzilla-daemon 2012-02-11 0:16 ` bugzilla-daemon 2012-02-11 10:14 ` bugzilla-daemon 2012-02-12 19:11 ` bugzilla-daemon 2012-02-12 19:11 ` bugzilla-daemon 2012-02-23 16:11 ` bugzilla-daemon 2012-03-20 15:17 ` bugzilla-daemon 2012-03-31 17:17 ` bugzilla-daemon 2012-05-04 18:32 ` bugzilla-daemon 2012-12-21 20:46 ` bugzilla-daemon 2012-12-24 9:52 ` bugzilla-daemon 2012-12-24 16:53 ` bugzilla-daemon 2012-12-24 16:54 ` bugzilla-daemon 2012-12-24 16:56 ` bugzilla-daemon 2012-12-24 16:56 ` bugzilla-daemon 2012-12-24 17:14 ` bugzilla-daemon 2012-12-24 17:38 ` bugzilla-daemon 2012-12-25 21:32 ` bugzilla-daemon 2012-12-25 21:33 ` bugzilla-daemon 2012-12-25 23:38 ` bugzilla-daemon 2012-12-26 15:06 ` bugzilla-daemon 2012-12-29 14:23 ` bugzilla-daemon 2013-01-02 3:48 ` bugzilla-daemon 2013-01-02 7:07 ` bugzilla-daemon 2013-01-03 9:09 ` bugzilla-daemon 2013-01-03 9:12 ` bugzilla-daemon 2013-01-03 16:27 ` bugzilla-daemon 2013-01-06 5:47 ` bugzilla-daemon 2013-03-02 18:08 ` bugzilla-daemon 2013-03-02 18:09 ` bugzilla-daemon 2013-04-10 20:34 ` bugzilla-daemon 2013-04-10 20:54 ` bugzilla-daemon 2013-04-10 21:14 ` bugzilla-daemon 2013-04-10 21:15 ` bugzilla-daemon 2013-04-10 21:16 ` 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=20121225233756.96A9D4680014@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@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).