From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14659 invoked by alias); 25 Dec 2012 21:33:52 -0000 Received: (qmail 14488 invoked by uid 22791); 25 Dec 2012 21:33:50 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 25 Dec 2012 21:33:43 +0000 Received: by mail.ecoscentric.com (Postfix, from userid 48) id 86FDF468001A; Tue, 25 Dec 2012 21:33:42 +0000 (GMT) From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001397] I2C driver for Kinetic microcontrollers X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Patches and contributions X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ilijak@siva.com.mk X-Bugzilla-Status: NEEDINFO X-Bugzilla-Priority: low X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: References: X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Tue, 25 Dec 2012 21:33:00 -0000 Message-Id: <20121225213340.D5065468000E@mail.ecoscentric.com> Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-bugs-owner@sourceware.org X-SW-Source: 2012/txt/msg01386.txt.bz2 Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001397 --- Comment #30 from Ilija Kocho 2012-12-25 21:33:38 GMT --- Hi Mike, thank you for your considerations. (In reply to comment #28) > I can make a couple of comments based on my experience with K60 and the > Freescale POSIX I2C driver and a real application. > > First is the issue of using the interrupt driver vs polling driver. I use the > interrupt driver so that other tasks can operate while waiting. My application > is PMBus, and clock stretching can slow things down, so I figure I don't want > to be in a polling loop. Polling is not an issue with eCos I2C driver. It is interrupt driven indeed. My question is about the macro WAIT_BUS_READY() and my concern is for multi-master system since, in a single master system it is returns immediately. Perhaps you could give it a try in your environment. Any feedback is appreciated. Ilija -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.