Skip to contentSkip to conversation

bcma: register bcma as device tree driver

PATCH Superseded Hauke Mehrtens 3 participants 7 messages Sep 16, 2014 – Sep 18, 2014

Subsystems (2)

v2 of 6 Superseded Latest is v6 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/2 bcma: register bcma as device tree driver

This driver is used by the bcm53xx ARM SoC code. Now it is possible to give the address of the chipcommon core in device tree and bcma will search for all the other cores.

---
 Documentation/devicetree/bindings/bus/bcma.txt | 40 +++++++++++++
 drivers/bcma/bcma_private.h                    | 16 +++++
 drivers/bcma/host_soc.c                        | 82 ++++++++++++++++++++++++++
 drivers/bcma/main.c                            | 10 ++++
 include/linux/bcma/bcma.h                      |  2 +
 5 files changed, 150 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/bus/bcma.txt

This is based on wireless-testing and should go into that tree.

changes since:
v1:
- renamed aix to axi
RFC:
- reworded the irq description
- improved the example
- hocked into bcma_modeinit() and bcma_modexit()

Documentation/devicetree/bindings/bus/bcma.txt new file +40 -0
new file mode 100644
index 0000000..f06f5c3
@@ -0,0 +1,40 @@
+Driver for ARM AXI Bus with Broadcom Plugins (bcma)
+
+Required properties:
+
+- compatible : brcm,bus-axi
+
+- reg : iomem address range of chipcommon core
+
+The cores on the AXI bus are auto detected by bcma. bcma automatically 
+detects the cores and the memory ranges they are using and they get 
+registered afterwards. Automatic detection of the IRQ number is not 
+possible on BCM47xx/BCM53xx ARM and MIPS SoCs. To assign IRQ number to 
+the cores, provide them manually through device tree. The IRQ number 
+and the device tree child entry will get assigned to the core with the 
+matching reg address.
+
+Example:
+
+	axi at 18000000 {
+		compatible = "brcm,bus-axi";
+		reg = <0x18000000 0x1000>;
+		ranges = <0x00000000 0x18000000 0x00100000>;
+		#address-cells = <1>;
+		#size-cells = <1>;
+
+		ethernet at 18024000 {
+			reg = <0x18024000 0x1000>;
+			interrupts = <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>;
+		};
+
+		ethernet at 18025000 {
+			reg = <0x18025000 0x1000>;
+			interrupts = <GIC_SPI 148 IRQ_TYPE_LEVEL_HIGH>;
+		};
+
+		pcie at 18012000 {
+			reg = <0x18012000 0x1000>;
+			interrupts = <GIC_SPI 131 IRQ_TYPE_LEVEL_HIGH>;
+		};
+	};
drivers/bcma/bcma_private.h +16 -0
index b40be43..b8728f0 100644
@@ -88,6 +88,22 @@ extern int __init bcma_host_pci_init(void);
 extern void __exit bcma_host_pci_exit(void);
 #endif /* CONFIG_BCMA_HOST_PCI */
 
+#ifdef CONFIG_BCMA_HOST_SOC
+/* host_pci.c */
+#ifdef CONFIG_OF
+extern int __init bcma_host_soc_register_driver(void);
+extern void __exit bcma_host_soc_unregister_driver(void);
+#else
+static inline int __init bcma_host_soc_register_driver(void)
+{
+	return 0;
+}
+static inline void __exit bcma_host_soc_unregister_driver(void)
+{
+}
+#endif /* CONFIG_OF */
+#endif /* CONFIG_BCMA_HOST_SOC */
+
 /* driver_pci.c */
 u32 bcma_pcie_read(struct bcma_drv_pci *pc, u32 address);
 
drivers/bcma/host_soc.c +82 -0

97 lines not on this page · raw message

drivers/bcma/main.c +10 -0
index c421403..e5d578c 100644
@@ -528,6 +528,13 @@ static int __init bcma_modinit(void)
 	if (err)
 		return err;
 
+#ifdef CONFIG_BCMA_HOST_SOC
+	err = bcma_host_soc_register_driver();
+	if (err) {
+		pr_err("SoC host initialization failed\n");
+		err = 0;
+	}
+#endif
 #ifdef CONFIG_BCMA_HOST_PCI
 	err = bcma_host_pci_init();
 	if (err) {
@@ -545,6 +552,9 @@ static void __exit bcma_modexit(void)
 #ifdef CONFIG_BCMA_HOST_PCI
 	bcma_host_pci_exit();
 #endif
+#ifdef CONFIG_BCMA_HOST_SOC
+	bcma_host_soc_unregister_driver();
+#endif
 	bus_unregister(&bcma_bus_type);
 }
 module_exit(bcma_modexit)
include/linux/bcma/bcma.h +2 -0
index 6345979..729f48e 100644
@@ -323,6 +323,8 @@ struct bcma_bus {
 		struct pci_dev *host_pci;
 		/* Pointer to the SDIO device (only for BCMA_HOSTTYPE_SDIO) */
 		struct sdio_func *host_sdio;
+		/* Pointer to platform device (only for BCMA_HOSTTYPE_SOC) */
+		struct platform_device *host_pdev;
 	};
 
 	struct bcma_chipinfo chipinfo;
Signature · 1 line
1.9.1
#1 lore raw

PATCH v2 2/2 bcma: get IRQ numbers from dt

It is not possible to auto detect the irq numbers used by the cores on an arm SoC. If bcma was registered with device tree it will search for some device tree nodes with the irq number and add it to the core configuration.

---
 drivers/bcma/main.c | 49 ++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 48 insertions(+), 1 deletion(-)

This is based on wireless-testing and should go into that tree.

changes since:
RFC:
- add #ifdef CONFIG_OF

drivers/bcma/main.c +48 -1
index e5d578c..b8731ee 100644
@@ -10,6 +10,8 @@
 #include <linux/platform_device.h>
 #include <linux/bcma/bcma.h>
 #include <linux/slab.h>
+#include <linux/of_irq.h>
+#include <linux/of_address.h>
 
 MODULE_DESCRIPTION("Broadcom's specific AMBA driver");
 MODULE_LICENSE("GPL");
@@ -131,6 +133,45 @@ static bool bcma_is_core_needed_early(u16 core_id)
 	return false;
 }
 
+#ifdef CONFIG_OF
+static struct device_node *bcma_of_find_child_device(struct platform_device *parent,
+						     struct bcma_device *core)
+{
+	struct device_node *node;
+	u64 size;
+	const __be32 *reg;
+
+	if (!parent || !parent->dev.of_node)
+		return NULL;
+
+	for_each_child_of_node(parent->dev.of_node, node) {
+		reg = of_get_address(node, 0, &size, NULL);
+		if (!reg)
+			continue;
+		if (be32_to_cpup(reg) == core->addr)
+			return node;
+	}
+	return NULL;
+}
+
+static void bcma_of_fill_device(struct platform_device *parent,
+				struct bcma_device *core)
+{
+	struct device_node *node;
+
+	node = bcma_of_find_child_device(parent, core);
+	if (!node)
+		return;
+	core->dev.of_node = node;
+	core->irq = irq_of_parse_and_map(node, 0);
+}
+#else
+static void bcma_of_fill_device(struct platform_device *parent,
+				struct bcma_device *core)
+{
+}
+#endif /* CONFIG_OF */
+
 static void bcma_register_core(struct bcma_bus *bus, struct bcma_device *core)
 {
 	int err;
@@ -147,7 +188,13 @@ static void bcma_register_core(struct bcma_bus *bus, struct bcma_device *core)
 		break;
 	case BCMA_HOSTTYPE_SOC:
 		core->dev.dma_mask = &core->dev.coherent_dma_mask;
-		core->dma_dev = &core->dev;
+		if (bus->host_pdev) {
+			core->dma_dev = &bus->host_pdev->dev;
+			core->dev.parent = &bus->host_pdev->dev;
+			bcma_of_fill_device(bus->host_pdev, core);
+		} else {
+			core->dma_dev = &core->dev;
+		}
 		break;
 	case BCMA_HOSTTYPE_SDIO:
 		break;
Signature · 1 line
1.9.1
maintainer
#2 lore raw

PATCH v2 1/2 bcma: register bcma as device tree driver

In reply to Hauke Mehrtens
Quoted 3 lines · Hauke Mehrtens

This driver is used by the bcm53xx ARM SoC code. Now it is possible to give the address of the chipcommon core in device tree and bcma will search for all the other cores.

Did you get any answer from Arend about detecting IRQs?

If not:
Arend: how much time it make take you to get an answer?

#3 lore raw

PATCH v2 1/2 bcma: register bcma as device tree driver

Quoted 9 lines · Rafa? Mi?ecki
Quoted 3 lines · Hauke Mehrtens

This driver is used by the bcm53xx ARM SoC code. Now it is possible to give the address of the chipcommon core in device tree and bcma will search for all the other cores.

Did you get any answer from Arend about detecting IRQs?

If not:
Arend: how much time it make take you to get an answer?

I already discussed this with our chip architect. There is a chip design rule that core index corresponds to the irq number. This at least is true for the bcm43xx devices, but unsure about others. So that option does not seem to fit. That leaves the OOB_ROUTER core I mentioned earlier, but it is a chip designers nightmare as they told me. Did not sound encouraging enough to start digging in there to obtain the information.

Regards,
Arend

#4 lore raw

PATCH v2 1/2 bcma: register bcma as device tree driver

Quoted 11 lines · Arend van Spriel
Quoted 9 lines · Rafa? Mi?ecki
Quoted 3 lines · Hauke Mehrtens

This driver is used by the bcm53xx ARM SoC code. Now it is possible to give the address of the chipcommon core in device tree and bcma will search for all the other cores.

Did you get any answer from Arend about detecting IRQs?

If not:
Arend: how much time it make take you to get an answer?

Quoted 7 lines

I already discussed this with our chip architect. There is a chip design rule that core index corresponds to the irq number. This at least is true for the bcm43xx devices, but unsure about others. So that option does not seem to fit. That leaves the OOB_ROUTER core I mentioned earlier, but it is a chip designers nightmare as they told me. Did not sound encouraging enough to start digging in there to obtain the information.

Thanks for asking around.

I will go with specifying the IRQs in device tree then.

Hauke

maintainer
#5 lore raw

PATCH v2 1/2 bcma: register bcma as device tree driver

In reply to Hauke Mehrtens

Review

Quoted 2 lines · Hauke Mehrtens
(quoted diff) +2 -0
+The cores on the AXI bus are auto detected by bcma. bcma automatically
+detects the cores

I'm far from being an English expert, but above is kind of pleonasm to me ;)

Review

Quoted 3 lines

and the memory ranges they are using and they get

(quoted diff) +2 -0
+registered afterwards. Automatic detection of the IRQ number is not
+possible on BCM47xx/BCM53xx ARM and MIPS SoCs.

Should we replace "not possible" with something like "not reliable"? After the last info we got from Arend.

drivers/bcma/bcma_private.h extern int __init bcma_host_pci_init(void); · line 92

Quoted 2 lines
drivers/bcma/bcma_private.h +2 -0
+#ifdef CONFIG_BCMA_HOST_SOC
+/* host_pci.c */

s/pci/soc/

drivers/bcma/bcma_private.h extern int __init bcma_host_pci_init(void); · line 105

Quoted 13 lines
drivers/bcma/bcma_private.h +13 -0
+#ifdef CONFIG_OF
+extern int __init bcma_host_soc_register_driver(void);
+extern void __exit bcma_host_soc_unregister_driver(void);
+#else
+static inline int __init bcma_host_soc_register_driver(void)
+{
+       return 0;
+}
+static inline void __exit bcma_host_soc_unregister_driver(void)
+{
+}
+#endif /* CONFIG_OF */
+#endif /* CONFIG_BCMA_HOST_SOC */

OK, so you just made bcma_host_soc_(un)register_driver calls safe above.

Quoted 5 lines
drivers/bcma/main.c +0 -0
index c421403..e5d578c 100644

drivers/bcma/main.c static int __init bcma_modinit(void) · line 537

Quoted 10 lines
drivers/bcma/main.c +7 -0
@@ -528,6 +528,13 @@ static int __init bcma_modinit(void)
        if (err)
                return err;
 
+#ifdef CONFIG_BCMA_HOST_SOC
+       err = bcma_host_soc_register_driver();
+       if (err) {
+               pr_err("SoC host initialization failed\n");
+               err = 0;
+       }
+#endif

And above you check for CONFIG_ anyway.

Signature · 1 line
Rafa?
#6 lore raw

PATCH v2 1/2 bcma: register bcma as device tree driver

Quoted 5 lines · Rafa? Mi?ecki

Review

Quoted 2 lines · Hauke Mehrtens
(quoted diff) +2 -0
+The cores on the AXI bus are auto detected by bcma. bcma automatically
+detects the cores

I'm far from being an English expert, but above is kind of pleonasm to me ;)

Yes to me too. ;-)

Quoted 6 lines

Review

Quoted 3 lines

and the memory ranges they are using and they get

(quoted diff) +2 -0
+registered afterwards. Automatic detection of the IRQ number is not
+possible on BCM47xx/BCM53xx ARM and MIPS SoCs.

Should we replace "not possible" with something like "not reliable"? After the last info we got from Arend.

Yes that sounds good.

Quoted 33 lines

drivers/bcma/bcma_private.h extern int __init bcma_host_pci_init(void); · line 92

Quoted 4 lines
drivers/bcma/bcma_private.h +2 -0
+#ifdef CONFIG_BCMA_HOST_SOC
+/* host_pci.c */

s/pci/soc/

drivers/bcma/bcma_private.h extern int __init bcma_host_pci_init(void); · line 105

Quoted 13 lines
drivers/bcma/bcma_private.h +13 -0
+#ifdef CONFIG_OF
+extern int __init bcma_host_soc_register_driver(void);
+extern void __exit bcma_host_soc_unregister_driver(void);
+#else
+static inline int __init bcma_host_soc_register_driver(void)
+{
+       return 0;
+}
+static inline void __exit bcma_host_soc_unregister_driver(void)
+{
+}
+#endif /* CONFIG_OF */
+#endif /* CONFIG_BCMA_HOST_SOC */

OK, so you just made bcma_host_soc_(un)register_driver calls safe above.

Quoted 8 lines
drivers/bcma/main.c +0 -0
index c421403..e5d578c 100644
@@ -528,6 +528,13 @@ static int __init bcma_modinit(void)
        if (err)
                return err;
 
Quoted 10 lines

drivers/bcma/main.c static int __init bcma_modinit(void) · line 537

Quoted 7 lines
drivers/bcma/main.c +7 -0
+#ifdef CONFIG_BCMA_HOST_SOC
+       err = bcma_host_soc_register_driver();
+       if (err) {
+               pr_err("SoC host initialization failed\n");
+               err = 0;
+       }
+#endif

And above you check for CONFIG_ anyway.

Yes that sounds good.