Author: rmilecki Date: 2015-05-09 19:38:48 +0200 (Sat, 09 May 2015) New Revision: 45652
Added: trunk/target/linux/generic/patches-3.18/028-bcma-from-4.2.patch trunk/target/linux/generic/patches-4.0/022-bcma-from-4.2.patch Removed: trunk/target/linux/bcm53xx/patches-3.18/180-bcma_set_gpio_base.patch trunk/target/linux/bcm53xx/patches-3.18/181-bcma-ngpio-bcm4707.patch Log: kernel: backport first bcma patches from 4.2 Signed-off-by: Rafa?\197?\130 Mi?\197?\130ecki <[email protected]> Deleted: trunk/target/linux/bcm53xx/patches-3.18/180-bcma_set_gpio_base.patch =================================================================== --- trunk/target/linux/bcm53xx/patches-3.18/180-bcma_set_gpio_base.patch 2015-05-09 08:58:12 UTC (rev 45651) +++ trunk/target/linux/bcm53xx/patches-3.18/180-bcma_set_gpio_base.patch 2015-05-09 17:38:48 UTC (rev 45652) @@ -1,17 +0,0 @@ -Subject: [PATCH] bcma: set gpio chip->base for CONFIG_ARCH_BCM_5301X like on 47xx - -This makes system GPIOs easier to deal with, e.g. for user space scripts. - -Signed-off-by: Felix Fietkau <[email protected]> ---- ---- a/drivers/bcma/driver_gpio.c -+++ b/drivers/bcma/driver_gpio.c -@@ -240,7 +240,7 @@ int bcma_gpio_init(struct bcma_drv_cc *c - * relative (per chip) numbers. - * So let's use predictable base for BCM47XX and "random" for all other. - */ --#if IS_BUILTIN(CONFIG_BCM47XX) -+#if IS_BUILTIN(CONFIG_BCM47XX) || IS_BUILTIN(CONFIG_ARCH_BCM_5301X) - chip->base = bus->num * BCMA_GPIO_MAX_PINS; - #else - chip->base = -1; Deleted: trunk/target/linux/bcm53xx/patches-3.18/181-bcma-ngpio-bcm4707.patch =================================================================== --- trunk/target/linux/bcm53xx/patches-3.18/181-bcma-ngpio-bcm4707.patch 2015-05-09 08:58:12 UTC (rev 45651) +++ trunk/target/linux/bcm53xx/patches-3.18/181-bcma-ngpio-bcm4707.patch 2015-05-09 17:38:48 UTC (rev 45652) @@ -1,17 +0,0 @@ -From: Felix Fietkau <[email protected]> -Subject: [PATCH] bcma: enable 32 GPIO pins for BCM4707+ - -At least one BCM4709 device uses GPIO pins > 16. - -Signed-off-by: Felix Fietkau <[email protected]> ---- ---- a/drivers/bcma/driver_gpio.c -+++ b/drivers/bcma/driver_gpio.c -@@ -226,6 +226,7 @@ int bcma_gpio_init(struct bcma_drv_cc *c - chip->of_node = cc->core->dev.of_node; - #endif - switch (bus->chipinfo.id) { -+ case BCMA_CHIP_ID_BCM4707: - case BCMA_CHIP_ID_BCM5357: - case BCMA_CHIP_ID_BCM53572: - chip->ngpio = 32; Added: trunk/target/linux/generic/patches-3.18/028-bcma-from-4.2.patch =================================================================== --- trunk/target/linux/generic/patches-3.18/028-bcma-from-4.2.patch (rev 0) +++ trunk/target/linux/generic/patches-3.18/028-bcma-from-4.2.patch 2015-05-09 17:38:48 UTC (rev 45652) @@ -0,0 +1,37 @@ +--- a/drivers/bcma/driver_gpio.c ++++ b/drivers/bcma/driver_gpio.c +@@ -226,6 +226,7 @@ int bcma_gpio_init(struct bcma_drv_cc *c + chip->of_node = cc->core->dev.of_node; + #endif + switch (bus->chipinfo.id) { ++ case BCMA_CHIP_ID_BCM4707: + case BCMA_CHIP_ID_BCM5357: + case BCMA_CHIP_ID_BCM53572: + chip->ngpio = 32; +@@ -235,16 +236,17 @@ int bcma_gpio_init(struct bcma_drv_cc *c + } + + /* +- * On MIPS we register GPIO devices (LEDs, buttons) using absolute GPIO +- * pin numbers. We don't have Device Tree there and we can't really use +- * relative (per chip) numbers. +- * So let's use predictable base for BCM47XX and "random" for all other. ++ * Register SoC GPIO devices with absolute GPIO pin base. ++ * On MIPS, we don't have Device Tree and we can't use relative (per chip) ++ * GPIO numbers. ++ * On some ARM devices, user space may want to access some system GPIO ++ * pins directly, which is easier to do with a predictable GPIO base. + */ +-#if IS_BUILTIN(CONFIG_BCM47XX) +- chip->base = bus->num * BCMA_GPIO_MAX_PINS; +-#else +- chip->base = -1; +-#endif ++ if (IS_BUILTIN(CONFIG_BCM47XX) || ++ cc->core->bus->hosttype == BCMA_HOSTTYPE_SOC) ++ chip->base = bus->num * BCMA_GPIO_MAX_PINS; ++ else ++ chip->base = -1; + + err = bcma_gpio_irq_domain_init(cc); + if (err) Added: trunk/target/linux/generic/patches-4.0/022-bcma-from-4.2.patch =================================================================== --- trunk/target/linux/generic/patches-4.0/022-bcma-from-4.2.patch (rev 0) +++ trunk/target/linux/generic/patches-4.0/022-bcma-from-4.2.patch 2015-05-09 17:38:48 UTC (rev 45652) @@ -0,0 +1,37 @@ +--- a/drivers/bcma/driver_gpio.c ++++ b/drivers/bcma/driver_gpio.c +@@ -226,6 +226,7 @@ int bcma_gpio_init(struct bcma_drv_cc *c + chip->of_node = cc->core->dev.of_node; + #endif + switch (bus->chipinfo.id) { ++ case BCMA_CHIP_ID_BCM4707: + case BCMA_CHIP_ID_BCM5357: + case BCMA_CHIP_ID_BCM53572: + chip->ngpio = 32; +@@ -235,16 +236,17 @@ int bcma_gpio_init(struct bcma_drv_cc *c + } + + /* +- * On MIPS we register GPIO devices (LEDs, buttons) using absolute GPIO +- * pin numbers. We don't have Device Tree there and we can't really use +- * relative (per chip) numbers. +- * So let's use predictable base for BCM47XX and "random" for all other. ++ * Register SoC GPIO devices with absolute GPIO pin base. ++ * On MIPS, we don't have Device Tree and we can't use relative (per chip) ++ * GPIO numbers. ++ * On some ARM devices, user space may want to access some system GPIO ++ * pins directly, which is easier to do with a predictable GPIO base. + */ +-#if IS_BUILTIN(CONFIG_BCM47XX) +- chip->base = bus->num * BCMA_GPIO_MAX_PINS; +-#else +- chip->base = -1; +-#endif ++ if (IS_BUILTIN(CONFIG_BCM47XX) || ++ cc->core->bus->hosttype == BCMA_HOSTTYPE_SOC) ++ chip->base = bus->num * BCMA_GPIO_MAX_PINS; ++ else ++ chip->base = -1; + + err = bcma_gpio_irq_domain_init(cc); + if (err) _______________________________________________ openwrt-commits mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-commits
