Re: [Gumstix-users] i2c-api call takes up an unreasonable amount of CPU power

[Andrei R. <po...@gm...>]

I2C_DEBUG_CORE is a generic debug option for i2c core.
Even with this flag enabled i2c shall perform reasonably.
IMHO it can print whatever amount of info about infrequent or
abnormal things, like initialization, mode changes, shutdown, warnings etc.
But to print something about every normal transaction there shall be a
separate flag.
Jakob would agree with me on that ;-)

On 1/23/07, Dave Hylands <dhy...@gm...> wrote:
> Hi Andrei,
>
> On 1/23/07, Andrei Rylin <po...@gm...> wrote:
> > On 1/23/07, Jesse Welling <jes...@gm...> wrote:
> > > .......at 50hrz......on a journaled file system....
> > > maybe this tidbit of info (debug is slow) should be wiki'd?
> >
> > Turning on debug option shall not produce that much noise
> > unless something goes really bad or a user explicitly wants all that noise.
>
> That particular debug causes a message to be printed for every single
> interrupt related to i2c, in addition to some other prints. You really
> only need that level of debug if you're trying to debug the i2c driver
> itself, in which case performance isn't that much of an issue.
>
> --
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>