Go to file
Daniel DeGrasse f3a35c58d8 drivers: timer: mcux_gpt_timer: rewrite timer to use free run mode
GPT timer driver previously used "restart mode", where the timer would
count to a given value, then rollover. In this mode,  "Any write access
to the Compare register of Channel 1 will reset the GPT counter". Since
a write to the compare register takes affect after 1 cycle of the
module's bus clock, and the bus clock is not synchonized with the GPT
module's low frequency counter clock, writing to the compare register
will induce a counter reset, and can cause the GPT to lose time
synchronization. This can induce time drift over time.

To fix this, rework the GPT driver to use "free run" mode. Note that
free run mode is not used directly, rather the GPT is configured to
reset on a tick boundary at boot, and then the second compare register
is used to set capture points. This way, the GPT interrupt will always
fire at a tick boundary, and no calculations are needed to handle
the counter rollover.

Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
2023-03-30 09:51:04 +02:00
.github ci: backport_issue_check: Use ubuntu-22.04 virtual environment 2023-03-22 02:49:03 +09:00
arch arch: arm: cortex_a_r: implement cache API 2023-03-29 09:03:37 +02:00
boards boards: mec172xevb_assy6906: support remote flashing 2023-03-29 17:44:06 -04:00
cmake linker: ld: include crt{begin,end}.o if LIBGCC_DIR is defined 2023-03-29 19:48:47 -04:00
doc doc: pm: device_runtime: document new devicetree flag 2023-03-29 12:21:13 -04:00
drivers drivers: timer: mcux_gpt_timer: rewrite timer to use free run mode 2023-03-30 09:51:04 +02:00
dts pm: device_runtime: add zephyr,pm-device-runtime-auto 2023-03-29 12:21:13 -04:00
include/zephyr pm: device_runtime: add zephyr,pm-device-runtime-auto 2023-03-29 12:21:13 -04:00
kernel pm: device_runtime: add zephyr,pm-device-runtime-auto 2023-03-29 12:21:13 -04:00
lib libc: share time() between minimal libc and armclang libc 2023-03-27 09:49:40 +02:00
misc
modules modules: hal_infineon: Added support of BT controller fw blobs 2023-03-22 16:40:55 +01:00
samples samples: boards: stm32: pm: standby_shutdown: use hwinfo_get_reset_cause() 2023-03-30 09:50:55 +02:00
scripts toolchain: move CONFIG_LLVM_USE_LD into cmake/toolchain/llvm 2023-03-29 19:48:47 -04:00
share cmake: sysbuild PRE_CMAKE, POST_CMAKE, PRE_DOMAINS, POST_DOMAINS hooks 2023-03-11 19:53:40 +01:00
snippets snippets: add cdc-acm-console 2023-03-26 16:12:41 +02:00
soc drivers: wdt: Add wdt_intel_adsp driver 2023-03-29 09:45:49 -04:00
submanifests
subsys pm: device_runtime: add zephyr,pm-device-runtime-auto 2023-03-29 12:21:13 -04:00
tests tests: pm: device_runtime: test zephyr,pm-device-runtime-auto 2023-03-29 12:21:13 -04:00
.checkpatch.conf
.clang-format clang-format: Add CHECKIF to IfMacros 2023-02-27 10:47:11 -08:00
.codecov.yml yamllint: fix all yamllint comments errors 2023-01-04 01:16:45 +09:00
.editorconfig
.gitattributes
.gitignore gitignore: Ignore new bsim tests build folders 2023-03-07 08:33:38 +01:00
.gitlint
.mailmap mailmap: add two fixes for bad commits 2023-03-17 08:08:16 -04:00
.yamllint scripts: compliance: add support for YAMLLint 2023-01-04 17:29:23 +01:00
CMakeLists.txt cmake: linker: make passing -no-pie configurable 2023-03-29 19:48:47 -04:00
CODE_OF_CONDUCT.md
CODEOWNERS smbus: Update CODEOWNERS and MAINTAINERS files 2023-03-22 08:16:23 -04:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr toolchain: move CONFIG_LLVM_USE_LD into cmake/toolchain/llvm 2023-03-29 19:48:47 -04:00
LICENSE
MAINTAINERS.yml MAINTAINERS: add collaborators for openthread related repos. 2023-03-29 09:46:19 -04:00
README.rst
VERSION VERSION: Bump to 3.3.99 2023-02-19 20:34:26 +09:00
version.h.in
west.yml manifest: Update to Mbed TLS 3.3.0 2023-03-29 14:41:18 +02:00
zephyr-env.cmd
zephyr-env.sh

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <picture>
         <source media="(prefers-color-scheme: dark)" srcset="doc/_static/images/logo-readme-dark.svg">
         <source media="(prefers-color-scheme: light)" srcset="doc/_static/images/logo-readme-light.svg">
         <img src="doc/_static/images/logo-readme-light.svg">
       </picture>
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <a
   href="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml?query=branch%3Amain">
   <img
   src="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml/badge.svg?event=push"></a>


The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM (Cortex-A,
Cortex-R, Cortex-M), Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V,
SPARC, MIPS, and a large number of `supported boards`_.

.. below included in doc/introduction/introduction.rst


Getting Started
***************

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

.. start_include_here

Community Support
*****************

Community support is provided via mailing lists and Discord; see the Resources
below for details.

.. _project-resources:

Resources
*********

Here's a quick summary of resources to help you find your way around:

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://github.com/zephyrproject-rtos/zephyr/releases
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI nightly build results.
* **Chat**: Real-time chat happens in Zephyr's Discord Server. Use
  this `Discord Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Discord Invite: https://chat.zephyrproject.org
.. _supported boards: http://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/develop/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/develop/getting_started/index.html#asking-for-help