Go to file
Thomas Stranger 5a475d7cc2 drivers/dma: stm32: add support for stm32g0 series
Update the existing driver to support STM32G0 series.
It enables the DMA_STM32_SHARED_IRQS flag for g0 series, such that
all interrupts are handled in a shared isr to avoid irq conflicts.
The shared isr is extended to be able to handle irqs from more than one
dma instance.

Furthermore the config_irq function of instance 1, which connects to the
irqs, was reworked to avoid irq conflicts when 2 dma instances on
stm32f0, or stm32g0 are enabled:
While dma1 has one exclusive irq for channel 1, and one irq for dma1
channels 2 and 3, all other channels share the same irq.
Therefore it is currently not possible to enable dma2 without enabling
dma1 at the same time, without getting an build errror due to an irq
conflict.

Signed-off-by: Thomas Stranger <thomas.stranger@outlook.com>
2021-04-26 14:16:03 -04:00
.buildkite ci: Cleanup files on exit 2021-04-21 08:53:26 -04:00
.github actions: bsim: fix typo 2021-04-26 17:38:48 +02:00
arch arch: select HAS_DTS for SPARC 2021-04-26 13:42:10 +02:00
boards board: arm: add support for the nucleo_f031k6 board 2021-04-26 09:49:52 -05:00
cmake cmake: llvm: llvm has no newlib 2021-04-22 07:42:58 -04:00
doc net: Remove support for CONFIG_NET_CONTEXT_TIMESTAMP option 2021-04-26 10:46:43 +03:00
drivers drivers/dma: stm32: add support for stm32g0 series 2021-04-26 14:16:03 -04:00
dts dts: arm: stm32g0: Add dma1, dma2, and dmamux1 2021-04-26 14:16:03 -04:00
include init: tweak Zephyr .init* section name conflicting with toolchain 2021-04-26 14:15:43 -04:00
kernel kernel: add an architecture specific structs header 2021-04-21 09:03:47 -04:00
lib lib: gui: lvgl: Fix logging macro usage 2021-04-22 15:29:15 -05:00
misc toolchain: add GEN_ABSOLUTE_SYM_KCONFIG() 2021-02-02 09:23:45 -05:00
modules modules: Add OS timer support 2021-04-21 20:40:24 -04:00
samples samples: nrf: system_off: Remove unnecessary sleep 2021-04-26 08:21:30 -04:00
scripts ci: remove bsim from buildkit execution 2021-04-23 21:40:10 -04:00
share cmake: using MD5_INFILE variable instead of ZephyrPackagePath.txt 2021-02-23 19:34:27 +01:00
soc dts: arm: st: Add SOC support for STM32G483 2021-04-26 17:40:01 +02:00
subsys logging: Increase thread stack size when net backend in use 2021-04-26 14:14:34 -04:00
tests tests: power_states_api: Test exit-latency-us 2021-04-26 08:21:30 -04:00
.checkpatch.conf checkpatch: ignore linux specific ENOSYS warning 2021-03-30 10:50:14 -05:00
.clang-format clang-format: Update with latest FOR_EACH macro list 2020-05-02 11:23:13 -04:00
.codecov.yml
.editorconfig editorconfig: indent Kconfig files with tabs 2020-07-08 21:30:38 -04:00
.gitattributes
.gitignore gitignore: add common Python venv directories 2021-04-20 11:30:40 -05:00
.gitlint
.mailmap
.uncrustify.cfg
CMakeLists.txt cmake: DTS post-processing of ELF file depends on CONFIG_HAS_DTS 2021-04-26 13:42:10 +02:00
CODE_OF_CONDUCT.md
CODEOWNERS include: Move emul.h to drivers/emul.h 2021-04-22 12:51:01 -04:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr cmake: gcc/clang: enable colour diagnostics in terminal output 2021-04-22 17:23:12 -04:00
LICENSE
MAINTAINERS.yml codeowner: path updates 2021-04-20 08:45:05 -04:00
README.rst doc: remove references to shippable 2021-03-04 07:14:11 -06:00
VERSION release: Update patch level to 99 after the 2.5.0 release 2021-02-14 11:52:38 -05:00
version.h.in
west.yml CMakeLists.txt: Add support for running PSA tests 2021-04-20 16:13:40 +02:00
zephyr-env.cmd
zephyr-env.sh

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <a href="https://buildkite.com/zephyr/zephyr">
   <img
   src="https://badge.buildkite.com/f5bd0dc88306cee17c9b38e78d11bb74a6291e3f40e7d13f31.svg?branch=master"></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-M,
Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of
`supported boards`_.

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

.. start_include_here

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.

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

Community support is provided via mailing lists and Slack; 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
  (buildkite) nightly build results.
* **Chat**: Zephyr's Slack workspace is https://zephyrproject.slack.com.  Use
  this `Slack 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

.. _Slack Invite: https://tinyurl.com/y5glwylp
.. _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/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/guides/getting-help.html