[jira] [Commented] (MYNEWT-329) Make hal cputime more efficient when 1 MHz clock or 32.768 kHz crystal is used.

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MYNEWT-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358194#comment-15358194 ] 

ASF subversion and git services commented on MYNEWT-329:
--------------------------------------------------------

Commit bcfe3fd05384ca07d65352bbfcbf02ce3195b383 in incubator-mynewt-core's branch refs/heads/develop from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=bcfe3fd ]

MYNEWT-329: More efficient cputime when using 1MHZ clock

You can now define a target variable named HAL_CPUTIME_1MHZ. If you include
this in your target the cputime will assume a 1MHZ clock is being used
and the routines for converting usecs to ticks (and vice versa) will
basically become "no-ops".


> Make hal cputime more efficient when 1 MHz clock or 32.768 kHz crystal is used.
> -------------------------------------------------------------------------------
>
>                 Key: MYNEWT-329
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-329
>             Project: Mynewt
>          Issue Type: Improvement
>          Components: HAL, Nimble
>    Affects Versions: v0_9_0
>            Reporter: William San Filippo
>            Assignee: William San Filippo
>             Fix For: v0_10_0
>
>
> We can make hal cputime be more efficient if we assume a 1 MHz or 32.768 kHz crystal as the timebase for hal cputime. Note that choosing these two values and not making other values generic seems reasonable as many low power timers are driven by 32.768 kHz crystals, and having a 1MHz clock for applications that dont care about power provides a fine enough resolution and makes converting from usecs to clock ticks simple.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)