zephyr/drivers/gpio/Kconfig.mmio32

#
# Copyright (c) 2017 Linaro Ltd.
#
# SPDX-License-Identifier: Apache-2.0
#

config GPIO_MMIO32
	bool
	default n
	help
	  This is a driver for accessing a simple, fixed purpose, 32-bit
	  memory-mapped i/o register using the same APIs as GPIO drivers. This
	  is useful when an SoC or board has registers that aren't part of a
	  GPIO IP block and these registers are used to control things that
	  Zephyr normaly expects to be specified using a GPIO pin, e.g. for
	  driving an LED, or chip-select line for an SPI device.
gpio: Add gpio_mmio32 driver to access basic 32-bit i/o registers It is envisaged that this will be used by SoC or board code to make available fixed purpose memory-mapped i/o registers to the rest of the system which normally expects to use GPIO devices, e.g. for driving chip select lines, LEDs or reading button states. As such, the driver code doesn't provide a kconfig based configuration mechanism, instead SoC/board code can hard-wire the devices it wants with something simple like: GPIO_MMIO32_INIT(misc_reg1, "MISC1", 0x12345678, 0xffffffffu) Then, for example, if bit N of the register at 0x12345678 is wired up as an SPI device chip select line, the SPI driver could be configured to use pin N of the "MISC1" GPIO driver and not need any other board specific code. Change-Id: Ib02fcbab73fcf9637e25834db060fb3108626f47 Signed-off-by: Jon Medhurst <tixy@linaro.org> 2016-12-21 00:55:41 +08:00			`#`
			`# Copyright (c) 2017 Linaro Ltd.`
			`#`
			`# SPDX-License-Identifier: Apache-2.0`
			`#`

			`config GPIO_MMIO32`
			`bool`
			`default n`
			`help`
			`This is a driver for accessing a simple, fixed purpose, 32-bit`
			`memory-mapped i/o register using the same APIs as GPIO drivers. This`
			`is useful when an SoC or board has registers that aren't part of a`
			`GPIO IP block and these registers are used to control things that`
			`Zephyr normaly expects to be specified using a GPIO pin, e.g. for`
			`driving an LED, or chip-select line for an SPI device.`