michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/drivers/pwm/Kconfig.mcux_ftm

21 lines
456 B
Text
Raw Permalink 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 13:45:29 +01:00
# MCUXpresso SDK FTM PWM
pwm: Introduce new mcux ftm shim driver Adds a shim layer around the mcux ftm driver to adapt it to the Zephyr pwm interface. Jira: ZEP-2025 Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-07-17 15:14:20 -05:00
# Copyright (c) 2017, NXP
# 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 01:04:04 +02:00
config PWM_MCUX_FTM
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 16:19:20 +02:00
bool "MCUX FTM PWM driver"
drivers: pwm: Update drivers to use devicetree Kconfig symbol Update pwm drivers to use DT_HAS_<compat>_ENABLED Kconfig symbol to expose the driver and enable it by default based on devicetree. We remove 'depend on' Kconfig for symbols that would be implied by the devicetree node existing. Signed-off-by: Kumar Gala <galak@kernel.org>
2022-07-21 16:13:45 -05:00
default y
dts: bindings: rename nxp,kinetis-ftm-pwm compatible Rename "nxp,kinetis-ftm-pwm" compatible to "nxp,ftm-pwm" to remove the device family from its name. Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com>
2024-11-24 14:44:57 +07:00
depends on DT_HAS_NXP_FTM_PWM_ENABLED
drivers: pwm: Enable pinctrl for kinetis ftm PWM driver Enable pinctrl for kinetis ftm PWM driver Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
2022-03-07 10:37:14 -06:00
select PINCTRL
pwm: Introduce new mcux ftm shim driver Adds a shim layer around the mcux ftm driver to adapt it to the Zephyr pwm interface. Jira: ZEP-2025 Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-07-17 15:14:20 -05:00
help
dts: bindings: rename nxp,kinetis-ftm-pwm compatible Rename "nxp,kinetis-ftm-pwm" compatible to "nxp,ftm-pwm" to remove the device family from its name. Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com>
2024-11-24 14:44:57 +07:00
Enable support for MCUX FTM PWM driver.
drivers: pwm: mcux_ftm: add PWM capure support Add PWM capture support to the NXP MCUX FlexTimer driver. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2020-12-18 10:25:20 +01:00
config PWM_CAPTURE_MCUX_FTM_FILTER_VALUE
int "MCUX FTM PWM capture filter value"
depends on PWM_MCUX_FTM && PWM_CAPTURE
range 0 15
default 0
help
PWM capture filter value for channels 0 and 2.
Copy permalink