OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/pwm/Kconfig.nrf5_sw

20 lines
625 B
Plaintext
Raw Normal View History

kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 20:45:29 +08:00
# Nordic Semiconductor nRF5x s/w PWM configuration options
drivers: pwm: Add nRF5x GPIOTE based PWM driver Add support for nRF5x series GPIOTE based PWM driver implementation. Provides upto 3 pins/channels using one HF timer, two PPI channels per pin, and one GPIOTE config per pin. Change-id: I6056b199ec2cff595ba8fea9f659a0338ed4635b Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-04-11 11:08:52 +08:00
# Copyright (c) 2017 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
kconfig: Turn pointless/confusing 'menuconfig's into 'config's Defining a symbol with 'menuconfig' just tells the menuconfig to display any dependent symbols that immediately follow it in a separate menu. 'menuconfig' has no effect on symbol values. Making a symbol that doesn't have any dependent symbols after it a 'menuconfig' should be avoided, because then you end up with an empty menu, which is shown as e.g. [*] Enable foo --- This is how it would be shown if there were children but they all happened to be invisible as well. With a regular 'config', it turns into [*] Enable foo Change all pointless 'menuconfig's to 'config's. See the section on 'menuconfig' on the Kconfig - Tips and Best Practices page as well. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-10-22 07:04:04 +08:00
config PWM_NRF5_SW
drivers: pwm: Add nRF5x GPIOTE based PWM driver Add support for nRF5x series GPIOTE based PWM driver implementation. Provides upto 3 pins/channels using one HF timer, two PPI channels per pin, and one GPIOTE config per pin. Change-id: I6056b199ec2cff595ba8fea9f659a0338ed4635b Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-04-11 11:08:52 +08:00
bool "Nordic Semiconductor nRF5x series S/W PWM"
drivers: pwm: nrf: Use HW PWM by default when available Enable HW PWM driver instead of the SW one on nRF SoCs where the PWM peripheral is present. Default PWM instances are also enabled on Nordic DK boards so that it is possible to build the basic fade_led sample for them without extra adjustments. After the above changes are applied, some configuration alterations in basic samples blink_led and fade_led become no longer needed. These are removed. And the blink_led sample is corrected so that it works with the nRF HW PWM driver as well. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-02-05 20:12:43 +08:00
default y if !PWM_NRFX
drivers: pwm: pwm_nrf5_sw: Use runtime resources allocation Use nrfx_gpiote and nrfx_ppi allocators to allocate channels at runtime instead of fixed, device-tree based allocation which is harder to maintain. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2021-11-24 15:05:05 +08:00
depends on HAS_HW_NRF_PPI
select NRFX_GPIOTE
select NRFX_PPI
drivers: pwm: Add nRF5x GPIOTE based PWM driver Add support for nRF5x series GPIOTE based PWM driver implementation. Provides upto 3 pins/channels using one HF timer, two PPI channels per pin, and one GPIOTE config per pin. Change-id: I6056b199ec2cff595ba8fea9f659a0338ed4635b Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-04-11 11:08:52 +08:00
help
Enable driver to utilize PWM on the Nordic Semiconductor nRF5x series.
drivers: pwm: nrf_sw: support generating PWM based on RTC So far nRF's TIMER was used for generating PWM signal. Add support for generating PWM based on RTC, which is sourced by 32KHz low frequency crystal. This allows to use low frequency PWM with much lower power consumption, because high frequency clock path can be disabled. Don't support RTC clock prescaler, because maximum 512s period covers most use cases. This allows to adjust pulse and period cycles to the fact that CLEAR task event is generated always one LFCLK cycle after period COMPARE value is reached. Also update hal_nordic revision, as it contains updated check for PPI channels conflict when RTC is used to generate PWM. Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
2020-10-10 04:15:34 +08:00
When used with HF timer it provides up to 3 pins, utilizing two PPI
channels per pin and one GPIOTE config per pin.
When used with RTC it provides up to 3 pins, utilizing three PPI
drivers: pwm: Add nRF5x GPIOTE based PWM driver Add support for nRF5x series GPIOTE based PWM driver implementation. Provides upto 3 pins/channels using one HF timer, two PPI channels per pin, and one GPIOTE config per pin. Change-id: I6056b199ec2cff595ba8fea9f659a0338ed4635b Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-04-11 11:08:52 +08:00
channels per pin and one GPIOTE config per pin.