patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity
zephyr/drivers/serial/Kconfig.mcux_lpuart

42 lines
666 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 13:45:29 +01:00
# MCUXpresso SDK LPUART
serial: Introduce new mcux lpuart shim driver Adds a shim layer around the mcux lpuart driver to adapt it to the Zephyr serial interface. NXP has multiple uart hardware blocks that implement different features and have different register maps. The k64 has a uart block called 'uart', while the kw41 has a uart block called 'lpuart' (low power uart). The MCUXpresso SDK provides separate drivers for each type of uart block but with similar software interfaces. As a result, there are also separate shim drivers in Zephyr. There is a 1:1:1 relationship between hardware block, mcux driver, and mcux shim driver. Because we now have two mcux shim drivers for the uart interface, a new naming convention is created: <interface>_mcux_<hw block> Where <interface> is the name of the Zephyr interface, in this case 'uart'. This convention is not new. <hw block> is the name of the NXP hardware block, in this case 'lpuart'. This is the new part, and distinguishes different hardware blocks for the same interface. Change-Id: I3a80b9bffa116bbb2b02ee950d4bdd79a19a4edc Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-01-18 12:54:58 +01:00
# Copyright (c) 2017, NXP
# SPDX-License-Identifier: Apache-2.0
menuconfig UART_MCUX_LPUART
bool "MCUX LPUART driver"
serial: Refactor mcux lpuart shim driver to use clock control interface Refactors the mcux lpuart shim driver to use the clock control interface instead of calling CLOCK_GetFreq() directly. This will allow SoCs with different clock architectures to reuse this driver. Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-08-26 23:18:28 +02:00
depends on HAS_MCUX_LPUART && CLOCK_CONTROL
serial: Introduce new mcux lpuart shim driver Adds a shim layer around the mcux lpuart driver to adapt it to the Zephyr serial interface. NXP has multiple uart hardware blocks that implement different features and have different register maps. The k64 has a uart block called 'uart', while the kw41 has a uart block called 'lpuart' (low power uart). The MCUXpresso SDK provides separate drivers for each type of uart block but with similar software interfaces. As a result, there are also separate shim drivers in Zephyr. There is a 1:1:1 relationship between hardware block, mcux driver, and mcux shim driver. Because we now have two mcux shim drivers for the uart interface, a new naming convention is created: <interface>_mcux_<hw block> Where <interface> is the name of the Zephyr interface, in this case 'uart'. This convention is not new. <hw block> is the name of the NXP hardware block, in this case 'lpuart'. This is the new part, and distinguishes different hardware blocks for the same interface. Change-Id: I3a80b9bffa116bbb2b02ee950d4bdd79a19a4edc Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-01-18 12:54:58 +01:00
select SERIAL_HAS_DRIVER
serial: introduce SERIAL_SUPPORT_INTERRUPT Kconfig option As not all drivers support interrupts we don't have a means to know if we can allow UART_INTERRUPT_DRIVEN to be enabled and thus various Kconfig options that select UART_INTERRUPT_DRIVEN. Some drivers have a interrupts, however not all do. So introduce a Kconfig option to let us know what the driver actually supports. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-06-22 18:26:58 +02:00
select SERIAL_SUPPORT_INTERRUPT
serial: Introduce new mcux lpuart shim driver Adds a shim layer around the mcux lpuart driver to adapt it to the Zephyr serial interface. NXP has multiple uart hardware blocks that implement different features and have different register maps. The k64 has a uart block called 'uart', while the kw41 has a uart block called 'lpuart' (low power uart). The MCUXpresso SDK provides separate drivers for each type of uart block but with similar software interfaces. As a result, there are also separate shim drivers in Zephyr. There is a 1:1:1 relationship between hardware block, mcux driver, and mcux shim driver. Because we now have two mcux shim drivers for the uart interface, a new naming convention is created: <interface>_mcux_<hw block> Where <interface> is the name of the Zephyr interface, in this case 'uart'. This convention is not new. <hw block> is the name of the NXP hardware block, in this case 'lpuart'. This is the new part, and distinguishes different hardware blocks for the same interface. Change-Id: I3a80b9bffa116bbb2b02ee950d4bdd79a19a4edc Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-01-18 12:54:58 +01:00
help
Enable the MCUX LPUART driver.
if UART_MCUX_LPUART
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 UART_MCUX_LPUART_0
serial: Introduce new mcux lpuart shim driver Adds a shim layer around the mcux lpuart driver to adapt it to the Zephyr serial interface. NXP has multiple uart hardware blocks that implement different features and have different register maps. The k64 has a uart block called 'uart', while the kw41 has a uart block called 'lpuart' (low power uart). The MCUXpresso SDK provides separate drivers for each type of uart block but with similar software interfaces. As a result, there are also separate shim drivers in Zephyr. There is a 1:1:1 relationship between hardware block, mcux driver, and mcux shim driver. Because we now have two mcux shim drivers for the uart interface, a new naming convention is created: <interface>_mcux_<hw block> Where <interface> is the name of the Zephyr interface, in this case 'uart'. This convention is not new. <hw block> is the name of the NXP hardware block, in this case 'lpuart'. This is the new part, and distinguishes different hardware blocks for the same interface. Change-Id: I3a80b9bffa116bbb2b02ee950d4bdd79a19a4edc Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-01-18 12:54:58 +01:00
bool "UART 0"
help
Enable UART 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 UART_MCUX_LPUART_1
serial: Add another instance to the mcux lpuart driver Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-08-28 16:27:19 +02:00
bool "UART 1"
help
Enable UART 1.
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 UART_MCUX_LPUART_2
drivers: serial: Add instances to mcux lpuart shim driver Adds instances 2 and 3 to the mcux lpuart shim driver. Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2018-09-24 18:12:57 +02:00
bool "UART 2"
help
Enable UART 2.
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 UART_MCUX_LPUART_3
drivers: serial: Add instances to mcux lpuart shim driver Adds instances 2 and 3 to the mcux lpuart shim driver. Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2018-09-24 18:12:57 +02:00
bool "UART 3"
help
Enable UART 3.
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 UART_MCUX_LPUART_4
drivers: serial: add config for uart 4 - Add config for uart 4 Signed-off-by: Ryan QIAN <jianghao.qian@nxp.com>
2019-03-21 10:14:16 +01:00
bool "UART 4"
help
Enable UART 4.
serial: Introduce new mcux lpuart shim driver Adds a shim layer around the mcux lpuart driver to adapt it to the Zephyr serial interface. NXP has multiple uart hardware blocks that implement different features and have different register maps. The k64 has a uart block called 'uart', while the kw41 has a uart block called 'lpuart' (low power uart). The MCUXpresso SDK provides separate drivers for each type of uart block but with similar software interfaces. As a result, there are also separate shim drivers in Zephyr. There is a 1:1:1 relationship between hardware block, mcux driver, and mcux shim driver. Because we now have two mcux shim drivers for the uart interface, a new naming convention is created: <interface>_mcux_<hw block> Where <interface> is the name of the Zephyr interface, in this case 'uart'. This convention is not new. <hw block> is the name of the NXP hardware block, in this case 'lpuart'. This is the new part, and distinguishes different hardware blocks for the same interface. Change-Id: I3a80b9bffa116bbb2b02ee950d4bdd79a19a4edc Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-01-18 12:54:58 +01:00
endif # UART_MCUX_LPUART
Reference in a new issue Copy permalink