On some BCM5301x ARM devices, user space still needs to control some
system GPIO pins for which no driver exists. This is a lot easier to do
with a predictable GPIO base.
Signed-off-by: Felix Fietkau n...@openwrt.org
---
drivers/bcma/driver_gpio.c | 19 ++-
1 file changed, 10
On 15 April 2015 at 15:07, Felix Fietkau n...@openwrt.org wrote:
@@ -235,16 +235,17 @@ int bcma_gpio_init(struct bcma_drv_cc *cc)
}
/*
-* On MIPS we register GPIO devices (LEDs, buttons) using absolute
GPIO
-* pin numbers. We don't have Device Tree there and
On 15 April 2015 at 16:36, Felix Fietkau n...@openwrt.org wrote:
On 2015-04-15 16:33, Rafał Miłecki wrote:
Anyway, I'm OK with this patch.
I don't think I need it, and I didn't want this change to produce
conflicts on multi-arch builds, so I limited it to the SoC bus only.
OK, thanks.
--
On 2015-04-15 16:33, Rafał Miłecki wrote:
On 15 April 2015 at 15:07, Felix Fietkau n...@openwrt.org wrote:
@@ -235,16 +235,17 @@ int bcma_gpio_init(struct bcma_drv_cc *cc)
}
/*
-* On MIPS we register GPIO devices (LEDs, buttons) using absolute
GPIO
-* pin
