msm: add gpiomux api for gpio multiplex & configuration.
Add the 'gpiomux' api, which addresses the following shortcomings
of existing tlmm api:
- gpio power-collapse, which is managed by a peripheral processor on
other targets, must be managed by the application processor on the 8x60.
- The enable/disable flag of the legacy gpio_tlmm_config api
is not applicable on the 8x60, and causes confusion.
- The gpio 'direction' bits are meaningless for all func_sel
configurations except for generic-gpio mode (func_sel 0), in which
case the gpio_direction_* functions should be used. Having these
bits in the tlmm api leads to confusion and misuse of the gpiolib
api, and they have been removed in gpiomux.
- The functional api of the legacy system ran contrary to the typical
use-case, which is a single massive configuration at boot. Rather
than forcing hundreds of 'config' function calls, the new api
allows data to be configured with a single table.
gpiomux_get and gpiomux_put are meant to be called automatically
when gpio_request and gpio_free are called, giving automatic
gpiomux/tlmm control to those drivers/lines with simple
power profiles - in the simplest cases, an entry in the gpiomux table
and the correct usage of gpiolib is all that is required to get proper
gpio power control.
Signed-off-by: Gregory Bean <gbean@codeaurora.org>
Signed-off-by: Daniel Walker <dwalker@codeaurora.org>
2010-08-28 11:05:44 -06:00
|
|
|
/*
|
|
|
|
* Copyright (C) 2007 Google, Inc.
|
2011-01-07 11:20:49 -07:00
|
|
|
* Copyright (c) 2008-2011, Code Aurora Forum. All rights reserved.
|
msm: add gpiomux api for gpio multiplex & configuration.
Add the 'gpiomux' api, which addresses the following shortcomings
of existing tlmm api:
- gpio power-collapse, which is managed by a peripheral processor on
other targets, must be managed by the application processor on the 8x60.
- The enable/disable flag of the legacy gpio_tlmm_config api
is not applicable on the 8x60, and causes confusion.
- The gpio 'direction' bits are meaningless for all func_sel
configurations except for generic-gpio mode (func_sel 0), in which
case the gpio_direction_* functions should be used. Having these
bits in the tlmm api leads to confusion and misuse of the gpiolib
api, and they have been removed in gpiomux.
- The functional api of the legacy system ran contrary to the typical
use-case, which is a single massive configuration at boot. Rather
than forcing hundreds of 'config' function calls, the new api
allows data to be configured with a single table.
gpiomux_get and gpiomux_put are meant to be called automatically
when gpio_request and gpio_free are called, giving automatic
gpiomux/tlmm control to those drivers/lines with simple
power profiles - in the simplest cases, an entry in the gpiomux table
and the correct usage of gpiolib is all that is required to get proper
gpio power control.
Signed-off-by: Gregory Bean <gbean@codeaurora.org>
Signed-off-by: Daniel Walker <dwalker@codeaurora.org>
2010-08-28 11:05:44 -06:00
|
|
|
* Author: Brian Swetland <swetland@google.com>
|
|
|
|
*
|
|
|
|
* This software is licensed under the terms of the GNU General Public
|
|
|
|
* License version 2, as published by the Free Software Foundation, and
|
|
|
|
* may be copied, distributed, and modified under those terms.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
*
|
|
|
|
* The MSM peripherals are spread all over across 768MB of physical
|
|
|
|
* space, which makes just having a simple IO_ADDRESS macro to slide
|
|
|
|
* them into the right virtual location rough. Instead, we will
|
|
|
|
* provide a master phys->virt mapping for peripherals here.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef __ASM_ARCH_MSM_IOMAP_8X60_H
|
|
|
|
#define __ASM_ARCH_MSM_IOMAP_8X60_H
|
|
|
|
|
|
|
|
/* Physical base address and size of peripherals.
|
|
|
|
* Ordered by the virtual base addresses they will be mapped at.
|
|
|
|
*
|
|
|
|
* MSM_VIC_BASE must be an value that can be loaded via a "mov"
|
|
|
|
* instruction, otherwise entry-macro.S will not compile.
|
|
|
|
*
|
|
|
|
* If you add or remove entries here, you'll want to edit the
|
|
|
|
* msm_io_desc array in arch/arm/mach-msm/io.c to reflect your
|
|
|
|
* changes.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
2011-01-04 12:02:59 -07:00
|
|
|
#define MSM8X60_QGIC_DIST_PHYS 0x02080000
|
|
|
|
#define MSM8X60_QGIC_DIST_SIZE SZ_4K
|
2010-01-06 15:55:24 -07:00
|
|
|
|
2011-01-04 12:02:59 -07:00
|
|
|
#define MSM8X60_QGIC_CPU_PHYS 0x02081000
|
|
|
|
#define MSM8X60_QGIC_CPU_SIZE SZ_4K
|
2010-01-06 15:55:24 -07:00
|
|
|
|
|
|
|
#define MSM_ACC_BASE IOMEM(0xF0002000)
|
|
|
|
#define MSM_ACC_PHYS 0x02001000
|
|
|
|
#define MSM_ACC_SIZE SZ_4K
|
|
|
|
|
|
|
|
#define MSM_GCC_BASE IOMEM(0xF0003000)
|
|
|
|
#define MSM_GCC_PHYS 0x02082000
|
|
|
|
#define MSM_GCC_SIZE SZ_4K
|
|
|
|
|
msm: add gpiomux api for gpio multiplex & configuration.
Add the 'gpiomux' api, which addresses the following shortcomings
of existing tlmm api:
- gpio power-collapse, which is managed by a peripheral processor on
other targets, must be managed by the application processor on the 8x60.
- The enable/disable flag of the legacy gpio_tlmm_config api
is not applicable on the 8x60, and causes confusion.
- The gpio 'direction' bits are meaningless for all func_sel
configurations except for generic-gpio mode (func_sel 0), in which
case the gpio_direction_* functions should be used. Having these
bits in the tlmm api leads to confusion and misuse of the gpiolib
api, and they have been removed in gpiomux.
- The functional api of the legacy system ran contrary to the typical
use-case, which is a single massive configuration at boot. Rather
than forcing hundreds of 'config' function calls, the new api
allows data to be configured with a single table.
gpiomux_get and gpiomux_put are meant to be called automatically
when gpio_request and gpio_free are called, giving automatic
gpiomux/tlmm control to those drivers/lines with simple
power profiles - in the simplest cases, an entry in the gpiomux table
and the correct usage of gpiolib is all that is required to get proper
gpio power control.
Signed-off-by: Gregory Bean <gbean@codeaurora.org>
Signed-off-by: Daniel Walker <dwalker@codeaurora.org>
2010-08-28 11:05:44 -06:00
|
|
|
#define MSM_TLMM_BASE IOMEM(0xF0004000)
|
|
|
|
#define MSM_TLMM_PHYS 0x00800000
|
|
|
|
#define MSM_TLMM_SIZE SZ_16K
|
|
|
|
|
2010-01-06 15:55:24 -07:00
|
|
|
#define MSM_SHARED_RAM_BASE IOMEM(0xF0100000)
|
|
|
|
#define MSM_SHARED_RAM_SIZE SZ_1M
|
|
|
|
|
2011-01-07 11:20:49 -07:00
|
|
|
#define MSM8X60_TMR_PHYS 0x02000000
|
|
|
|
#define MSM8X60_TMR_SIZE SZ_4K
|
2010-12-02 13:05:12 -07:00
|
|
|
|
2011-01-07 11:20:49 -07:00
|
|
|
#define MSM8X60_TMR0_PHYS 0x02040000
|
|
|
|
#define MSM8X60_TMR0_SIZE SZ_4K
|
2010-10-05 16:23:57 -06:00
|
|
|
|
msm: add gpiomux api for gpio multiplex & configuration.
Add the 'gpiomux' api, which addresses the following shortcomings
of existing tlmm api:
- gpio power-collapse, which is managed by a peripheral processor on
other targets, must be managed by the application processor on the 8x60.
- The enable/disable flag of the legacy gpio_tlmm_config api
is not applicable on the 8x60, and causes confusion.
- The gpio 'direction' bits are meaningless for all func_sel
configurations except for generic-gpio mode (func_sel 0), in which
case the gpio_direction_* functions should be used. Having these
bits in the tlmm api leads to confusion and misuse of the gpiolib
api, and they have been removed in gpiomux.
- The functional api of the legacy system ran contrary to the typical
use-case, which is a single massive configuration at boot. Rather
than forcing hundreds of 'config' function calls, the new api
allows data to be configured with a single table.
gpiomux_get and gpiomux_put are meant to be called automatically
when gpio_request and gpio_free are called, giving automatic
gpiomux/tlmm control to those drivers/lines with simple
power profiles - in the simplest cases, an entry in the gpiomux table
and the correct usage of gpiolib is all that is required to get proper
gpio power control.
Signed-off-by: Gregory Bean <gbean@codeaurora.org>
Signed-off-by: Daniel Walker <dwalker@codeaurora.org>
2010-08-28 11:05:44 -06:00
|
|
|
#endif
|