PCI: Add support for Apple M1
Subsystems (9)
Marc Zyngier
maintainerv5 cover PCI: Add support for Apple M1
This is v5 of the series adding PCIe support for the M1 SoC. Not a lot has changed this time around, and most of what I was saying in [1] is still valid.
Very little has changed code wise (a couple of bug fixes). The series however now carries a bunch of DT updates so that people can actually make use of PCIe on an M1 box (OK, not quite, you will still need [2], or whatever version replaces it). The corresponding bindings are either already merged, or queued for 5.16 (this is the case for the PCI binding).
It all should be in a state that makes it mergeable (yeah, I said that last time... I mean it this time! ;-).
As always, comments welcome.
M.
[1] https://lore.kernel.org/r/[email protected]
[2] https://lore.kernel.org/r/[email protected]
Alyssa Rosenzweig (2):
PCI: apple: Add initial hardware bring-up
PCI: apple: Set up reference clocks when probing
Marc Zyngier (10):
irqdomain: Make of_phandle_args_to_fwspec generally available of/irq: Allow matching of an interrupt-map local to an interrupt
controller
PCI: of: Allow matching of an interrupt-map local to a PCI device
PCI: apple: Add INTx and per-port interrupt support
PCI: apple: Implement MSI support
iommu/dart: Exclude MSI doorbell from PCIe device IOVA range
PCI: apple: Configure RID to SID mapper on device addition
arm64: dts: apple: t8103: Add PCIe DARTs
arm64: dts: apple: t8103: Add root port interrupt routing
arm64: dts: apple: j274: Expose PCI node for the Ethernet MAC address
Mark Kettenis (2):
arm64: apple: Add pinctrl nodes
arm64: apple: Add PCIe node
MAINTAINERS | 7 + arch/arm64/boot/dts/apple/t8103-j274.dts | 23 + arch/arm64/boot/dts/apple/t8103.dtsi | 203 ++++++ drivers/iommu/apple-dart.c | 27 + drivers/of/irq.c | 17 +- drivers/pci/controller/Kconfig | 17 + drivers/pci/controller/Makefile | 1 + drivers/pci/controller/pcie-apple.c | 822 +++++++++++++++++++++++ drivers/pci/of.c | 10 +- include/linux/irqdomain.h | 4 + kernel/irq/irqdomain.c | 6 +- 11 files changed, 1127 insertions(+), 10 deletions(-) create mode 100644 drivers/pci/controller/pcie-apple.c
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 1/14 irqdomain: Make of_phandle_args_to_fwspec generally available
of_phandle_args_to_fwspec() can be generally useful to code extracting a DT of_phandle and using an irq_fwspec to use the hierarchical irqdomain API.
Make it visible the the rest of the kernel, including modules.
--- include/linux/irqdomain.h | 4 ++++ kernel/irq/irqdomain.c | 6 +++--- 2 files changed, 7 insertions(+), 3 deletions(-)
include/linux/irqdomain.h +4 -0
@@ -64,6 +64,10 @@ struct irq_fwspec {u32 param[IRQ_DOMAIN_IRQ_SPEC_PARAMS ]; }; +/* Conversion function from of_phandle_args fields to fwspec */ +void of_phandle_args_to_fwspec (struct device_node *np,const u32 *args, +unsigned int count,struct irq_fwspec *fwspec); +/* * Should several domains have the same device node, but serve * different purposes (for example one domain is for PCI/MSI, and the
kernel/irq/irqdomain.c +3 -3
@@ -744,9 +744,8 @@ static int irq_domain_translate(struct irq_domain *d,return 0 ; } -static void of_phandle_args_to_fwspec (struct device_node *np,const u32 *args, -unsigned int count, -struct irq_fwspec *fwspec) +void of_phandle_args_to_fwspec (struct device_node *np,const u32 *args, +unsigned int count,struct irq_fwspec *fwspec) {int i;
@@ -756,6 +755,7 @@ static void of_phandle_args_to_fwspec(struct device_node *np, const u32 *args,for (i =0 ; i < count; i++) fwspec->param[i] = args[i]; } +EXPORT_SYMBOL_GPL (of_phandle_args_to_fwspec);unsigned int irq_create_fwspec_mapping (struct irq_fwspec *fwspec) {
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 2/14 of/irq: Allow matching of an interrupt-map local to an interrupt controller
In reply to Marc Zyngierof_irq_parse_raw() has a baked assumption that if a node has an interrupt-controller property, it cannot possibly also have an interrupt-map property (the latter being ignored).
This seems to be an odd behaviour, and there is no reason why we should avoid supporting this use case. This is specially useful when a PCI root port acts as an interrupt controller for PCI endpoints, such as this:
pcie0: pcie@690000000 {
[...]
port00: pci@0,0 {
device_type = "pci";
[...]
#address-cells = <3>;
interrupt-controller;
#interrupt-cells = <1>;
interrupt-map-mask = <0 0 0 7>;
interrupt-map = <0 0 0 1 &port00 0 0 0 0>,
<0 0 0 2 &port00 0 0 0 1>,
<0 0 0 3 &port00 0 0 0 2>,
<0 0 0 4 &port00 0 0 0 3>;
};
};Handle it by detecting that we have an interrupt-map early in the parsing, and special case the situation where the phandle in the interrupt map refers to the current node (which is the interesting case here).
--- drivers/of/irq.c | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-)
drivers/of/irq.c +12 -5
@@ -156,10 +156,14 @@ int of_irq_parse_raw(const __be32 *addr, struct of_phandle_args *out_irq)/* Now start the actual "proper" walk of the interrupt tree */ while (ipar !=NULL ) { -/* Now check if cursor is an interrupt-controller and if it is -* then we are done +/* +* Now check if cursor is an interrupt-controller and +* if it is then we are done, unless there is an +* interrupt-map which takes precedence. */ -if (of_property_read_bool (ipar,"interrupt-controller" )) { + imap =of_get_property (ipar,"interrupt-map" , &imaplen); +if (imap ==NULL && +of_property_read_bool (ipar,"interrupt-controller" )) {pr_debug (" -> got it !\n" );return 0 ; }
@@ -173,8 +177,6 @@ int of_irq_parse_raw(const __be32 *addr, struct of_phandle_args *out_irq) goto fail; } -/* Now look for an interrupt-map */ - imap =of_get_property (ipar,"interrupt-map" , &imaplen);/* No interrupt map, check for an interrupt parent */ if (imap ==NULL ) {pr_debug (" -> no map, getting parent\n" );
@@ -255,6 +257,11 @@ int of_irq_parse_raw(const __be32 *addr, struct of_phandle_args *out_irq) out_irq->args_count = intsize = newintsize; addrsize = newaddrsize; +if (ipar == newpar) { +pr_debug ("%pOF interrupt-map entry to self\n" , ipar); +return 0 ; + } + skiplevel:/* Iterate again with new parent */ out_irq->np = newpar;
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 3/14 PCI: of: Allow matching of an interrupt-map local to a PCI device
In reply to Marc ZyngierJust as we now allow an interrupt map to be parsed when part of an interrupt controller, there is no reason to ignore an interrupt map that would be part of a pci device node such as a root port since we already allow interrupt specifiers.
Allow the matching of such property when local to the node of a PCI device, which allows the device itself to use the interrupt map for for its own purpose.
--- drivers/pci/of.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
drivers/pci/of.c +8 -2
@@ -423,7 +423,7 @@ static int devm_of_pci_get_host_bridge_resources(struct device *dev,*/ static int of_irq_parse_pci (const struct pci_dev *pdev,struct of_phandle_args *out_irq) { -struct device_node *dn, *ppnode; +struct device_node *dn, *ppnode =NULL ;struct pci_dev *ppdev;__be32 laddr[3 ];u8 pin;
@@ -452,8 +452,14 @@ static int of_irq_parse_pci(const struct pci_dev *pdev, struct of_phandle_args *if (pin ==0 )return -ENODEV ; +/* Local interrupt-map in the device node? Use it! */ +if (of_get_property (dn,"interrupt-map" ,NULL )) { + pin =pci_swizzle_interrupt_pin (pdev, pin); + ppnode = dn; + } +/* Now we walk up the PCI tree */ -for (;;) { +while (!ppnode) {/* Get the pci_dev of our parent */ ppdev = pdev->bus->self;
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 4/14 PCI: apple: Add initial hardware bring-up
In reply to Marc ZyngierFrom: Alyssa Rosenzweig <[email protected]>
Add a minimal driver to bring up the PCIe bus on Apple system-on-chips, particularly the Apple M1. This driver exposes the internal bus used for the USB type-A ports, Ethernet, Wi-Fi, and Bluetooth. Bringing up the radios requires additional drivers beyond what's necessary for PCIe itself.
At this stage, nothing is functionnal.
--- MAINTAINERS | 7 + drivers/pci/controller/Kconfig | 12 ++ drivers/pci/controller/Makefile | 1 + drivers/pci/controller/pcie-apple.c | 237 ++++++++++++++++++++++++++++ 4 files changed, 257 insertions(+) create mode 100644 drivers/pci/controller/pcie-apple.c
MAINTAINERS +7 -0
@@ -1280,6 +1280,13 @@ S: Maintained F: Documentation/devicetree/bindings/iommu/apple,dart.yaml F: drivers/iommu/apple-dart.c +APPLE PCIE CONTROLLER DRIVER +M: Alyssa Rosenzweig <[email protected]> +M: Marc Zyngier <[email protected]> +L: [email protected] +S: Maintained +F: drivers/pci/controller/pcie-apple.c + APPLE SMC DRIVER M: Henrik Rydberg <[email protected]> L: [email protected]
drivers/pci/controller/Kconfig +12 -0
@@ -312,6 +312,18 @@ config PCIE_HISI_ERR Say Y here if you want error handling support for the PCIe controller's errors on HiSilicon HIP SoCs +config PCIE_APPLE + tristate "Apple PCIe controller" + depends on ARCH_APPLE || COMPILE_TEST + depends on OF + depends on PCI_MSI_IRQ_DOMAIN + help + Say Y here if you want to enable PCIe controller support on Apple + system-on-chips, like the Apple M1. This is required for the USB + type-A ports, Ethernet, Wi-Fi, and Bluetooth. + + If unsure, say Y if you have an Apple Silicon system. + source "drivers/pci/controller/dwc/Kconfig" source "drivers/pci/controller/mobiveil/Kconfig" source "drivers/pci/controller/cadence/Kconfig"
drivers/pci/controller/Makefile +1 -0
@@ -37,6 +37,7 @@ obj-$(CONFIG_VMD) += vmd.o obj-$(CONFIG_PCIE_BRCMSTB) += pcie-brcmstb.o obj-$(CONFIG_PCI_LOONGSON) += pci-loongson.o obj-$(CONFIG_PCIE_HISI_ERR) += pcie-hisi-error.o +obj-$(CONFIG_PCIE_APPLE) += pcie-apple.o # pcie-hisi.o quirks are needed even without CONFIG_PCIE_DW obj-y += dwc/ obj-y += mobiveil/
drivers/pci/controller/pcie-apple.c new file +237 -0
237 lines not on this page · raw message
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 5/14 PCI: apple: Set up reference clocks when probing
In reply to Marc ZyngierFrom: Alyssa Rosenzweig <[email protected]>
Apple's PCIe controller requires clocks to be configured in order to bring up the hardware. Add the register pokes required to do so.
Adapted from Corellium's driver via Mark Kettenis's U-Boot patches.
--- drivers/pci/controller/pcie-apple.c | 46 +++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+)
drivers/pci/controller/pcie-apple.c +46 -0
@@ -132,6 +132,48 @@ static void rmw_set(u32 set, void __iomem *addr)writel_relaxed (readl_relaxed (addr) | set, addr); } +static void rmw_clear (u32 clr,void __iomem *addr) +{ +writel_relaxed (readl_relaxed (addr) & ~clr, addr); +} + +static int apple_pcie_setup_refclk (struct apple_pcie *pcie, +struct apple_pcie_port *port) +{ +u32 stat; +int res; + + res =readl_relaxed_poll_timeout (pcie->base +CORE_RC_PHYIF_STAT , stat, + stat &CORE_RC_PHYIF_STAT_REFCLK , +100 ,50000 ); +if (res <0 ) +return res; + +rmw_set (CORE_LANE_CTL_CFGACC , pcie->base +CORE_LANE_CTL (port->idx)); +rmw_set (CORE_LANE_CFG_REFCLK0REQ , pcie->base +CORE_LANE_CFG (port->idx)); + + res =readl_relaxed_poll_timeout (pcie->base +CORE_LANE_CFG (port->idx), + stat, stat &CORE_LANE_CFG_REFCLK0ACK , +100 ,50000 ); +if (res <0 ) +return res; + +rmw_set (CORE_LANE_CFG_REFCLK1 , pcie->base +CORE_LANE_CFG (port->idx)); + res =readl_relaxed_poll_timeout (pcie->base +CORE_LANE_CFG (port->idx), + stat, stat &CORE_LANE_CFG_REFCLK1 , +100 ,50000 ); + +if (res <0 ) +return res; + +rmw_clear (CORE_LANE_CTL_CFGACC , pcie->base +CORE_LANE_CTL (port->idx)); + +rmw_set (CORE_LANE_CFG_REFCLKEN , pcie->base +CORE_LANE_CFG (port->idx)); +rmw_set (PORT_REFCLK_EN , port->base +PORT_REFCLK ); + +return 0 ; +} +static int apple_pcie_setup_port (struct apple_pcie *pcie,struct device_node *np) {
@@ -165,6 +207,10 @@ static int apple_pcie_setup_port(struct apple_pcie *pcie,rmw_set (PORT_APPCLK_EN , port->base +PORT_APPCLK ); + ret =apple_pcie_setup_refclk (pcie, port); +if (ret <0 ) +return ret; +rmw_set (PORT_PERST_OFF , port->base +PORT_PERST );gpiod_set_value (reset,1 );
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 6/14 PCI: apple: Add INTx and per-port interrupt support
In reply to Marc ZyngierAdd support for the per-port interrupt controller that deals with both INTx signalling and management interrupts.
This allows the Link-up/Link-down interrupts to be wired, allowing the bring-up to be synchronised (and provide debug information). The framework can further be used to handle the rest of the per port events if and when necessary.
Likewise, INTx signalling is implemented so that end-points can actually be used.
--- drivers/pci/controller/pcie-apple.c | 209 ++++++++++++++++++++++++++++ 1 file changed, 209 insertions(+)
drivers/pci/controller/pcie-apple.c +209 -0
@@ -21,6 +21,7 @@#include <linux/gpio/consumer.h> #include <linux/kernel.h> #include <linux/iopoll.h> +#include <linux/irqchip/chained_irq.h> #include <linux/irqdomain.h> #include <linux/module.h> #include <linux/msi.h>
@@ -118,12 +119,14 @@struct apple_pcie {struct device *dev;void __iomem *base; +struct completion event; };struct apple_pcie_port {struct apple_pcie *pcie;struct device_node *np;void __iomem *base; +struct irq_domain *domain;int idx; };
@@ -137,6 +140,200 @@ static void rmw_clear(u32 clr, void __iomem *addr)writel_relaxed (readl_relaxed (addr) & ~clr, addr); } +static void apple_port_irq_mask (struct irq_data *data) +{ +struct apple_pcie_port *port =irq_data_get_irq_chip_data (data); + +writel_relaxed (BIT (data->hwirq), port->base +PORT_INTMSKSET ); +} + +static void apple_port_irq_unmask (struct irq_data *data) +{ +struct apple_pcie_port *port =irq_data_get_irq_chip_data (data); + +writel_relaxed (BIT (data->hwirq), port->base +PORT_INTMSKCLR ); +} + +static bool hwirq_is_intx (unsigned int hwirq) +{ +return BIT (hwirq) & PORT_INT_INTx_MASK; +} + +static void apple_port_irq_ack (struct irq_data *data) +{ +struct apple_pcie_port *port =irq_data_get_irq_chip_data (data); + +if (!hwirq_is_intx (data->hwirq)) +writel_relaxed (BIT (data->hwirq), port->base +PORT_INTSTAT ); +} + +static int apple_port_irq_set_type (struct irq_data *data,unsigned int type) +{ +/* +* It doesn't seem that there is any way to configure the +* trigger, so assume INTx have to be level (as per the spec), +* and the rest is edge (which looks likely). +*/ +if (hwirq_is_intx (data->hwirq) ^ !!(type &IRQ_TYPE_LEVEL_MASK )) +return -EINVAL ; + +irqd_set_trigger_type (data, type); +return 0 ; +} + +static struct irq_chip apple_port_irqchip = { + .name ="PCIe" , + .irq_ack = apple_port_irq_ack, + .irq_mask = apple_port_irq_mask, + .irq_unmask = apple_port_irq_unmask, + .irq_set_type = apple_port_irq_set_type, +}; + +static int apple_port_irq_domain_alloc (struct irq_domain *domain, +unsigned int virq,unsigned int nr_irqs, +void *args) +{ +struct apple_pcie_port *port = domain->host_data; +struct irq_fwspec *fwspec = args; +int i; + +for (i =0 ; i < nr_irqs; i++) { +irq_flow_handler_t flow = handle_edge_irq; +unsigned int type =IRQ_TYPE_EDGE_RISING ; + +if (hwirq_is_intx (fwspec->param[0 ] + i)) { + flow = handle_level_irq; + type =IRQ_TYPE_LEVEL_HIGH ; + } + +irq_domain_set_info (domain, virq + i, fwspec->param[0 ] + i, + &apple_port_irqchip, port, flow, +NULL ,NULL ); + +irq_set_irq_type (virq + i, type); + } + +return 0 ; +} + +static void apple_port_irq_domain_free (struct irq_domain *domain, +unsigned int virq,unsigned int nr_irqs) +{ +int i; + +for (i =0 ; i < nr_irqs; i++) { +struct irq_data *d =irq_domain_get_irq_data (domain, virq + i); +irq_set_handler (virq + i,NULL ); +irq_domain_reset_irq_data (d); + } +} + +static const struct irq_domain_ops apple_port_irq_domain_ops = { + .translate = irq_domain_translate_onecell, + .alloc = apple_port_irq_domain_alloc, + .free = apple_port_irq_domain_free, +}; + +static void apple_port_irq_handler (struct irq_desc *desc) +{ +struct apple_pcie_port *port =irq_desc_get_handler_data (desc); +struct irq_chip *chip =irq_desc_get_chip (desc); +unsigned long stat; +int i; + +chained_irq_enter (chip, desc); + + stat =readl_relaxed (port->base +PORT_INTSTAT ); + +for_each_set_bit (i, &stat,32 ) +generic_handle_domain_irq (port->domain, i); + +chained_irq_exit (chip, desc); +} + +static int apple_pcie_port_setup_irq (struct apple_pcie_port *port) +{ +struct fwnode_handle *fwnode = &port->np->fwnode; +unsigned int irq; + +/* FIXME: consider moving each interrupt under each port */ + irq =irq_of_parse_and_map (to_of_node (dev_fwnode (port->pcie->dev)), + port->idx); +if (!irq) +return -ENXIO ; + + port->domain =irq_domain_create_linear (fwnode,32 , + &apple_port_irq_domain_ops, + port); +if (!port->domain) +return -ENOMEM ; + +/* Disable all interrupts */ +writel_relaxed (~0 , port->base +PORT_INTMSKSET ); +writel_relaxed (~0 , port->base +PORT_INTSTAT ); + +irq_set_chained_handler_and_data (irq, apple_port_irq_handler, port); + +return 0 ; +} + +static irqreturn_t apple_pcie_port_irq (int irq,void *data) +{ +struct apple_pcie_port *port = data; +unsigned int hwirq =irq_domain_get_irq_data (port->domain, irq)->hwirq; + +switch (hwirq) { +case PORT_INT_LINK_UP : +dev_info_ratelimited (port->pcie->dev,"Link up on %pOF\n" , + port->np); +complete_all (&port->pcie->event); +break ; +case PORT_INT_LINK_DOWN : +dev_info_ratelimited (port->pcie->dev,"Link down on %pOF\n" , + port->np); +break ; +default : +return IRQ_NONE ; + } + +return IRQ_HANDLED ; +} + +static int apple_pcie_port_register_irqs (struct apple_pcie_port *port) +{ +static struct { +unsigned int hwirq; +const char *name; + } port_irqs[] = { + {PORT_INT_LINK_UP ,"Link up" , }, + {PORT_INT_LINK_DOWN ,"Link down" , }, + }; +int i; + +for (i =0 ; i <ARRAY_SIZE (port_irqs); i++) { +struct irq_fwspec fwspec = { + .fwnode = &port->np->fwnode, + .param_count =1 , + .param = { + [0 ] = port_irqs[i].hwirq, + }, + }; +unsigned int irq; +int ret; + + irq =irq_domain_alloc_irqs (port->domain,1 ,NUMA_NO_NODE , + &fwspec); +if (WARN_ON (!irq)) +continue ; + + ret =request_irq (irq, apple_pcie_port_irq,0 , + port_irqs[i].name, port); +WARN_ON (ret); + } + +return 0 ; +} +static int apple_pcie_setup_refclk (struct apple_pcie *pcie,struct apple_pcie_port *port) {
@@ -221,8 +418,20 @@ static int apple_pcie_setup_port(struct apple_pcie *pcie,return ret; } + ret =apple_pcie_port_setup_irq (port); +if (ret) +return ret; + +init_completion (&pcie->event); + + ret =apple_pcie_port_register_irqs (port); +WARN_ON (ret); +writel_relaxed (PORT_LTSSMCTL_START , port->base +PORT_LTSSMCTL ); +if (!wait_for_completion_timeout (&pcie->event,HZ /10 )) +dev_warn (pcie->dev,"%pOF link didn't come up\n" , np); +return 0 ; }
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 7/14 PCI: apple: Implement MSI support
In reply to Marc ZyngierProbe for the 'msi-ranges' property, and implement the MSI support in the form of the usual two-level hierarchy.
Note that contrary to the wired interrupts, MSIs are shared among all the ports.
--- drivers/pci/controller/pcie-apple.c | 169 +++++++++++++++++++++++++++- 1 file changed, 168 insertions(+), 1 deletion(-)
drivers/pci/controller/pcie-apple.c +168 -1
@@ -116,10 +116,22 @@#define PORT_TUNSTAT_PERST_ACK_PEND BIT(1)#define PORT_PREFMEM_ENABLE 0x00994 +/* +* The doorbell address is set to 0xfffff000, which by convention +* matches what MacOS does, and it is possible to use any other +* address (in the bottom 4GB, as the base register is only 32bit). +*/ +#define DOORBELL_ADDR 0xfffff000 +struct apple_pcie { +struct mutex lock;struct device *dev;void __iomem *base; +struct irq_domain *domain; +unsigned long *bitmap;struct completion event; +struct irq_fwspec fwspec; +u32 nvecs; };struct apple_pcie_port {
@@ -140,6 +152,101 @@ static void rmw_clear(u32 clr, void __iomem *addr)writel_relaxed (readl_relaxed (addr) & ~clr, addr); } +static void apple_msi_top_irq_mask (struct irq_data *d) +{ +pci_msi_mask_irq (d); +irq_chip_mask_parent (d); +} + +static void apple_msi_top_irq_unmask (struct irq_data *d) +{ +pci_msi_unmask_irq (d); +irq_chip_unmask_parent (d); +} + +static struct irq_chip apple_msi_top_chip = { + .name ="PCIe MSI" , + .irq_mask = apple_msi_top_irq_mask, + .irq_unmask = apple_msi_top_irq_unmask, + .irq_eoi = irq_chip_eoi_parent, + .irq_set_affinity = irq_chip_set_affinity_parent, + .irq_set_type = irq_chip_set_type_parent, +}; + +static void apple_msi_compose_msg (struct irq_data *data,struct msi_msg *msg) +{ + msg->address_hi =upper_32_bits (DOORBELL_ADDR ); + msg->address_lo =lower_32_bits (DOORBELL_ADDR ); + msg->data = data->hwirq; +} + +static struct irq_chip apple_msi_bottom_chip = { + .name ="MSI" , + .irq_mask = irq_chip_mask_parent, + .irq_unmask = irq_chip_unmask_parent, + .irq_eoi = irq_chip_eoi_parent, + .irq_set_affinity = irq_chip_set_affinity_parent, + .irq_set_type = irq_chip_set_type_parent, + .irq_compose_msi_msg = apple_msi_compose_msg, +}; + +static int apple_msi_domain_alloc (struct irq_domain *domain,unsigned int virq, +unsigned int nr_irqs,void *args) +{ +struct apple_pcie *pcie = domain->host_data; +struct irq_fwspec fwspec = pcie->fwspec; +unsigned int i; +int ret, hwirq; + +mutex_lock (&pcie->lock); + + hwirq =bitmap_find_free_region (pcie->bitmap, pcie->nvecs, +order_base_2 (nr_irqs)); + +mutex_unlock (&pcie->lock); + +if (hwirq <0 ) +return -ENOSPC ; + + fwspec.param[1 ] += hwirq; + + ret =irq_domain_alloc_irqs_parent (domain, virq, nr_irqs, &fwspec); +if (ret) +return ret; + +for (i =0 ; i < nr_irqs; i++) { +irq_domain_set_hwirq_and_chip (domain, virq + i, hwirq + i, + &apple_msi_bottom_chip, + domain->host_data); + } + +return 0 ; +} + +static void apple_msi_domain_free (struct irq_domain *domain,unsigned int virq, +unsigned int nr_irqs) +{ +struct irq_data *d =irq_domain_get_irq_data (domain, virq); +struct apple_pcie *pcie = domain->host_data; + +mutex_lock (&pcie->lock); + +bitmap_release_region (pcie->bitmap, d->hwirq,order_base_2 (nr_irqs)); + +mutex_unlock (&pcie->lock); +} + +static const struct irq_domain_ops apple_msi_domain_ops = { + .alloc = apple_msi_domain_alloc, + .free = apple_msi_domain_free, +}; + +static struct msi_domain_info apple_msi_info = { + .flags = (MSI_FLAG_USE_DEF_DOM_OPS |MSI_FLAG_USE_DEF_CHIP_OPS | +MSI_FLAG_MULTI_PCI_MSI |MSI_FLAG_PCI_MSIX ), + .chip = &apple_msi_top_chip, +}; +static void apple_port_irq_mask (struct irq_data *data) {struct apple_pcie_port *port =irq_data_get_irq_chip_data (data);
@@ -274,6 +381,15 @@ static int apple_pcie_port_setup_irq(struct apple_pcie_port *port)irq_set_chained_handler_and_data (irq, apple_port_irq_handler, port); +/* Configure MSI base address */ +BUILD_BUG_ON (upper_32_bits (DOORBELL_ADDR )); +writel_relaxed (lower_32_bits (DOORBELL_ADDR ), port->base +PORT_MSIADDR ); + +/* Enable MSIs, shared between all ports */ +writel_relaxed (0 , port->base +PORT_MSIBASE ); +writel_relaxed ((ilog2 (port->pcie->nvecs) <<PORT_MSICFG_L2MSINUM_SHIFT ) | +PORT_MSICFG_EN , port->base +PORT_MSICFG ); +return 0 ; }
@@ -435,6 +551,55 @@ static int apple_pcie_setup_port(struct apple_pcie *pcie,return 0 ; } +static int apple_msi_init (struct apple_pcie *pcie) +{ +struct fwnode_handle *fwnode =dev_fwnode (pcie->dev); +struct of_phandle_args args = {}; +struct irq_domain *parent; +int ret; + + ret =of_parse_phandle_with_args (to_of_node (fwnode),"msi-ranges" , +"#interrupt-cells" ,0 , &args); +if (ret) +return ret; + + ret =of_property_read_u32_index (to_of_node (fwnode),"msi-ranges" , + args.args_count +1 , &pcie->nvecs); +if (ret) +return ret; + +of_phandle_args_to_fwspec (args.np, args.args, args.args_count, + &pcie->fwspec); + + pcie->bitmap =devm_bitmap_zalloc (pcie->dev, pcie->nvecs,GFP_KERNEL ); +if (!pcie->bitmap) +return -ENOMEM ; + + parent =irq_find_matching_fwspec (&pcie->fwspec,DOMAIN_BUS_WIRED ); +if (!parent) { +dev_err (pcie->dev,"failed to find parent domain\n" ); +return -ENXIO ; + } + + parent =irq_domain_create_hierarchy (parent,0 , pcie->nvecs, fwnode, + &apple_msi_domain_ops, pcie); +if (!parent) { +dev_err (pcie->dev,"failed to create IRQ domain\n" ); +return -ENOMEM ; + } +irq_domain_update_bus_token (parent,DOMAIN_BUS_NEXUS ); + + pcie->domain =pci_msi_create_irq_domain (fwnode, &apple_msi_info, + parent); +if (!pcie->domain) { +dev_err (pcie->dev,"failed to create MSI domain\n" ); +irq_domain_remove (parent); +return -ENOMEM ; + } + +return 0 ; +} +static int apple_pcie_init (struct pci_config_window *cfg) {struct device *dev = cfg->parent;
@@ -449,6 +614,8 @@ static int apple_pcie_init(struct pci_config_window *cfg) pcie->dev = dev; +mutex_init (&pcie->lock); + pcie->base =devm_platform_ioremap_resource (platform,1 );if (IS_ERR (pcie->base))return PTR_ERR (pcie->base);
@@ -461,7 +628,7 @@ static int apple_pcie_init(struct pci_config_window *cfg) } } -return 0 ; +return apple_msi_init (pcie); }static const struct pci_ecam_ops apple_pcie_cfg_ecam_ops = {
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 8/14 iommu/dart: Exclude MSI doorbell from PCIe device IOVA range
In reply to Marc ZyngierThe MSI doorbell on Apple HW can be any address in the low 4GB range. However, the MSI write is matched by the PCIe block before hitting the iommu. It must thus be excluded from the IOVA range that is assigned to any PCIe device.
--- drivers/iommu/apple-dart.c | 27 +++++++++++++++++++++++++++ drivers/pci/controller/Kconfig | 5 +++++ drivers/pci/controller/pcie-apple.c | 4 +++- 3 files changed, 35 insertions(+), 1 deletion(-)
drivers/iommu/apple-dart.c +27 -0
@@ -721,6 +721,31 @@ static int apple_dart_def_domain_type(struct device *dev)return 0 ; } +#ifndef CONFIG_PCIE_APPLE_MSI_DOORBELL_ADDR +/* Keep things compiling when CONFIG_PCI_APPLE isn't selected */ +#define CONFIG_PCIE_APPLE_MSI_DOORBELL_ADDR 0 +#endif +#define DOORBELL_ADDR (CONFIG_PCIE_APPLE_MSI_DOORBELL_ADDR & PAGE_MASK) + +static void apple_dart_get_resv_regions (struct device *dev, +struct list_head *head) +{ +if (IS_ENABLED (CONFIG_PCIE_APPLE ) &&dev_is_pci (dev)) { +struct iommu_resv_region *region; +int prot =IOMMU_WRITE |IOMMU_NOEXEC |IOMMU_MMIO ; + + region =iommu_alloc_resv_region (DOORBELL_ADDR , +PAGE_SIZE , prot, +IOMMU_RESV_MSI ); +if (!region) +return ; + +list_add_tail (®ion->list, head); + } + +iommu_dma_get_resv_regions (dev, head); +} +static const struct iommu_ops apple_dart_iommu_ops = { .domain_alloc = apple_dart_domain_alloc, .domain_free = apple_dart_domain_free,
@@ -737,6 +762,8 @@ static const struct iommu_ops apple_dart_iommu_ops = { .device_group = apple_dart_device_group, .of_xlate = apple_dart_of_xlate, .def_domain_type = apple_dart_def_domain_type, + .get_resv_regions = apple_dart_get_resv_regions, + .put_resv_regions = generic_iommu_put_resv_regions, .pgsize_bitmap = -1UL, /* Restricted during dart probe */ };
drivers/pci/controller/Kconfig +5 -0
@@ -312,6 +312,11 @@ config PCIE_HISI_ERR Say Y here if you want error handling support for the PCIe controller's errors on HiSilicon HIP SoCs +config PCIE_APPLE_MSI_DOORBELL_ADDR + hex + default 0xfffff000 + depends on PCIE_APPLE + config PCIE_APPLE tristate "Apple PCIe controller" depends on ARCH_APPLE || COMPILE_TEST
drivers/pci/controller/pcie-apple.c +3 -1
@@ -120,8 +120,10 @@* The doorbell address is set to 0xfffff000, which by convention * matches what MacOS does, and it is possible to use any other * address (in the bottom 4GB, as the base register is only 32bit). +* However, it has to be excluded from the the IOVA range, and the +* DART driver has to know about it. */ -#define DOORBELL_ADDR 0xfffff000 +#define DOORBELL_ADDR CONFIG_PCIE_APPLE_MSI_DOORBELL_ADDRstruct apple_pcie {struct mutex lock;
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 9/14 PCI: apple: Configure RID to SID mapper on device addition
In reply to Marc ZyngierThe Apple PCIe controller doesn't directly feed the endpoint's Requester ID to the IOMMU (DART), but instead maps RIDs onto Stream IDs (SIDs). The DART and the PCIe controller must thus agree on the SIDs that are used for translation (by using the 'iommu-map' property).
For this purpose, parse the 'iommu-map' property each time a device gets added, and use the resulting translation to configure the PCIe RID-to-SID mapper. Similarily, remove the translation if/when the device gets removed.
This is all driven from a bus notifier which gets registered at probe time. Hopefully this is the only PCI controller driver in the whole system.
--- drivers/pci/controller/pcie-apple.c | 165 +++++++++++++++++++++++++++- 1 file changed, 163 insertions(+), 2 deletions(-)
drivers/pci/controller/pcie-apple.c +163 -2
@@ -23,8 +23,10 @@#include <linux/iopoll.h> #include <linux/irqchip/chained_irq.h> #include <linux/irqdomain.h> +#include <linux/list.h> #include <linux/module.h> #include <linux/msi.h> +#include <linux/notifier.h> #include <linux/of_irq.h> #include <linux/pci-ecam.h>
@@ -116,6 +118,8 @@#define PORT_TUNSTAT_PERST_ACK_PEND BIT(1)#define PORT_PREFMEM_ENABLE 0x00994 +#define MAX_RID2SID 64 +/* * The doorbell address is set to 0xfffff000, which by convention * matches what MacOS does, and it is possible to use any other
@@ -131,6 +135,7 @@ struct apple_pcie {void __iomem *base;struct irq_domain *domain;unsigned long *bitmap; +struct list_head ports;struct completion event;struct irq_fwspec fwspec;u32 nvecs;
@@ -141,6 +146,9 @@ struct apple_pcie_port {struct device_node *np;void __iomem *base;struct irq_domain *domain; +struct list_head entry; +DECLARE_BITMAP ( sid_map,MAX_RID2SID ); +int sid_map_sz;int idx; };
@@ -489,6 +497,14 @@ static int apple_pcie_setup_refclk(struct apple_pcie *pcie,return 0 ; } +static u32 apple_pcie_rid2sid_write (struct apple_pcie_port *port, +int idx,u32 val) +{ +writel_relaxed (val, port->base +PORT_RID2SID (idx)); +/* Read back to ensure completion of the write */ +return readl_relaxed (port->base +PORT_RID2SID (idx)); +} +static int apple_pcie_setup_port (struct apple_pcie *pcie,struct device_node *np) {
@@ -496,7 +512,7 @@ static int apple_pcie_setup_port(struct apple_pcie *pcie,struct apple_pcie_port *port;struct gpio_desc *reset;u32 stat, idx; -int ret; +int ret, i; reset =gpiod_get_from_of_node (np,"reset-gpios" ,0 ,GPIOD_OUT_LOW ,"#PERST" );
@@ -540,6 +556,18 @@ static int apple_pcie_setup_port(struct apple_pcie *pcie,if (ret)return ret; +/* Reset all RID/SID mappings, and check for RAZ/WI registers */ +for (i =0 ; i <MAX_RID2SID ; i++) { +if (apple_pcie_rid2sid_write (port, i,0xbad1d ) !=0xbad1d ) +break ; +apple_pcie_rid2sid_write (port, i,0 ); + } + +dev_dbg (pcie->dev,"%pOF: %d RID/SID mapping entries\n" , np, i); + + port->sid_map_sz = i; + +list_add_tail (&port->entry, &pcie->ports);init_completion (&pcie->event); ret =apple_pcie_port_register_irqs (port);
@@ -602,6 +630,121 @@ static int apple_msi_init(struct apple_pcie *pcie)return 0 ; } +static struct apple_pcie_port *apple_pcie_get_port (struct pci_dev *pdev) +{ +struct pci_config_window *cfg = pdev->sysdata; +struct apple_pcie *pcie = cfg->priv; +struct pci_dev *port_pdev = pdev; +struct apple_pcie_port *port; + +/* Find the root port this device is on */ + port_pdev =pcie_find_root_port (pdev); + +/* If finding the port itself, nothing to do */ +if (WARN_ON (!port_pdev) || pdev == port_pdev) +return NULL ; + +list_for_each_entry (port, &pcie->ports, entry) { +if (port->idx ==PCI_SLOT (port_pdev->devfn)) +return port; + } + +return NULL ; +} + +static int apple_pcie_add_device (struct apple_pcie_port *port, +struct pci_dev *pdev) +{ +u32 sid, rid =PCI_DEVID (pdev->bus->number, pdev->devfn); +int idx, err; + +dev_dbg (&pdev->dev,"added to bus %s, index %d\n" , +pci_name (pdev->bus->self), port->idx); + + err =of_map_id (port->pcie->dev->of_node, rid,"iommu-map" , +"iommu-map-mask" ,NULL , &sid); +if (err) +return err; + +mutex_lock (&port->pcie->lock); + + idx =bitmap_find_free_region (port->sid_map, port->sid_map_sz,0 ); +if (idx >=0 ) { +apple_pcie_rid2sid_write (port, idx, +PORT_RID2SID_VALID | + (sid <<PORT_RID2SID_SID_SHIFT ) | rid); + +dev_dbg (&pdev->dev,"mapping RID%x to SID%x (index %d)\n" , + rid, sid, idx); + } + +mutex_unlock (&port->pcie->lock); + +return idx >=0 ?0 : -ENOSPC ; +} + +static void apple_pcie_release_device (struct apple_pcie_port *port, +struct pci_dev *pdev) +{ +u32 rid =PCI_DEVID (pdev->bus->number, pdev->devfn); +int idx; + +mutex_lock (&port->pcie->lock); + +for_each_set_bit (idx, port->sid_map, port->sid_map_sz) { +u32 val; + + val =readl_relaxed (port->base +PORT_RID2SID (idx)); +if ((val &0xffff ) == rid) { +apple_pcie_rid2sid_write (port, idx,0 ); +bitmap_release_region (port->sid_map, idx,0 ); +dev_dbg (&pdev->dev,"Released %x (%d)\n" , val, idx); +break ; + } + } + +mutex_unlock (&port->pcie->lock); +} + +static int apple_pcie_bus_notifier (struct notifier_block *nb, +unsigned long action, +void *data) +{ +struct device *dev = data; +struct pci_dev *pdev =to_pci_dev (dev); +struct apple_pcie_port *port; +int err; + +/* +* This is a bit ugly. We assume that if we get notified for +* any PCI device, we must be in charge of it, and that there +* is no other PCI controller in the whole system. It probably +* holds for now, but who knows for how long? +*/ + port =apple_pcie_get_port (pdev); +if (!port) +return NOTIFY_DONE ; + +switch (action) { +case BUS_NOTIFY_ADD_DEVICE : + err =apple_pcie_add_device (port, pdev); +if (err) +return notifier_from_errno (err); +break ; +case BUS_NOTIFY_DEL_DEVICE : +apple_pcie_release_device (port, pdev); +break ; +default : +return NOTIFY_DONE ; + } + +return NOTIFY_OK ; +} + +static struct notifier_block apple_pcie_nb = { + .notifier_call = apple_pcie_bus_notifier, +}; +static int apple_pcie_init (struct pci_config_window *cfg) {struct device *dev = cfg->parent;
@@ -622,6 +765,9 @@ static int apple_pcie_init(struct pci_config_window *cfg)if (IS_ERR (pcie->base))return PTR_ERR (pcie->base); + cfg->priv = pcie; +INIT_LIST_HEAD (&pcie->ports); +for_each_child_of_node (dev->of_node, of_port) { ret =apple_pcie_setup_port (pcie, of_port);if (ret) {
@@ -633,6 +779,21 @@ static int apple_pcie_init(struct pci_config_window *cfg)return apple_msi_init (pcie); } +static int apple_pcie_probe (struct platform_device *pdev) +{ +int ret; + + ret =bus_register_notifier (&pci_bus_type, &apple_pcie_nb); +if (ret) +return ret; + + ret =pci_host_common_probe (pdev); +if (ret) +bus_unregister_notifier (&pci_bus_type, &apple_pcie_nb); + +return ret; +} +static const struct pci_ecam_ops apple_pcie_cfg_ecam_ops = { .init = apple_pcie_init, .pci_ops = {
@@ -649,7 +810,7 @@ static const struct of_device_id apple_pcie_of_match[] = {MODULE_DEVICE_TABLE (of, apple_pcie_of_match);static struct platform_driver apple_pcie_driver = { - .probe = pci_host_common_probe, + .probe = apple_pcie_probe, .driver = { .name ="pcie-apple" , .of_match_table = apple_pcie_of_match,
Signature · 1 line
2.30.2
Marc Zyngier
maintainerPATCH v5 10/14 arm64: apple: Add pinctrl nodes
In reply to Marc ZyngierFrom: Mark Kettenis <[email protected]>
Add pinctrl nodes corresponding to the gpio,t8101 nodes in the Apple device tree for the Mac mini (M1, 2020).
Clock references are left out at the moment and will be added once the appropriate bindings have been settled upon.
--- arch/arm64/boot/dts/apple/t8103.dtsi | 83 ++++++++++++++++++++++++++++ 1 file changed, 83 insertions(+)
arch/arm64/boot/dts/apple/t8103.dtsi +83 -0
@@ -9,6 +9,7 @@ #include <dt-bindings/interrupt-controller/apple-aic.h> #include <dt-bindings/interrupt-controller/irq.h> +#include <dt-bindings/pinctrl/apple.h> / { compatible = "apple,t8103", "apple,arm-platform";
@@ -131,5 +132,87 @@ aic: interrupt-controller@23b100000 { interrupt-controller; reg = <0x2 0x3b100000 0x0 0x8000>; }; + + pinctrl_ap: pinctrl@23c100000 { + compatible = "apple,t8103-pinctrl", "apple,pinctrl"; + reg = <0x2 0x3c100000 0x0 0x100000>; + + gpio-controller; + #gpio-cells = <2>; + gpio-ranges = <&pinctrl_ap 0 0 212>; + + interrupt-controller; + interrupt-parent = <&aic>; + interrupts = <AIC_IRQ 190 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 191 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 192 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 193 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 194 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 195 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 196 IRQ_TYPE_LEVEL_HIGH>; + + pcie_pins: pcie-pins { + pinmux = <APPLE_PINMUX(150, 1)>, + <APPLE_PINMUX(151, 1)>, + <APPLE_PINMUX(32, 1)>; + }; + }; + + pinctrl_aop: pinctrl@24a820000 { + compatible = "apple,t8103-pinctrl", "apple,pinctrl"; + reg = <0x2 0x4a820000 0x0 0x4000>; + + gpio-controller; + #gpio-cells = <2>; + gpio-ranges = <&pinctrl_aop 0 0 42>; + + interrupt-controller; + interrupt-parent = <&aic>; + interrupts = <AIC_IRQ 268 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 269 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 270 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 271 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 272 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 273 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 274 IRQ_TYPE_LEVEL_HIGH>; + }; + + pinctrl_nub: pinctrl@23d1f0000 { + compatible = "apple,t8103-pinctrl", "apple,pinctrl"; + reg = <0x2 0x3d1f0000 0x0 0x4000>; + + gpio-controller; + #gpio-cells = <2>; + gpio-ranges = <&pinctrl_nub 0 0 23>; + + interrupt-controller; + interrupt-parent = <&aic>; + interrupts = <AIC_IRQ 330 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 331 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 332 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 333 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 334 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 335 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 336 IRQ_TYPE_LEVEL_HIGH>; + }; + + pinctrl_smc: pinctrl@23e820000 { + compatible = "apple,t8103-pinctrl", "apple,pinctrl"; + reg = <0x2 0x3e820000 0x0 0x4000>; + + gpio-controller; + #gpio-cells = <2>; + gpio-ranges = <&pinctrl_smc 0 0 16>; + + interrupt-controller; + interrupt-parent = <&aic>; + interrupts = <AIC_IRQ 391 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 392 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 393 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 394 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 395 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 396 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 397 IRQ_TYPE_LEVEL_HIGH>; + }; }; };
Signature · 1 line
2.30.2
Re: [PATCH v5 10/14] arm64: apple: Add pinctrl nodes
Quoted 12 lines · Marc Zyngier
From: Mark Kettenis <[email protected]>
Add pinctrl nodes corresponding to the gpio,t8101 nodes in the Apple device tree for the Mac mini (M1, 2020).
Clock references are left out at the moment and will be added once the appropriate bindings have been settled upon.
Signed-off-by Mark Kettenis <[email protected]>Reviewed-by Linus Walleij <[email protected]>Signed-off-by Marc Zyngier <[email protected]>
(...)
arch/arm64/boot/dts/apple/t8103.dtsi aic: interrupt-controller@23b100000 { · line 142
Quoted 7 lines
arch/arm64/boot/dts/apple/t8103.dtsi +7
-0+ pinctrl_ap: pinctrl@23c100000 { + compatible = "apple,t8103-pinctrl", "apple,pinctrl"; + reg = <0x2 0x3c100000 0x0 0x100000>; + + gpio-controller; + #gpio-cells = <2>; + gpio-ranges = <&pinctrl_ap 0 0 212>;
In other discussions it turns out that the driver is abusing these gpio-ranges to find out how many pins are in each pinctrl instance. This is not the idea with gpio-ranges, these can be multiple and map different sets, so we need something like
apple,npins = <212>;
(+ bindings)
or so...
Yours,
Linus Walleij
Marc Zyngier
maintainerRe: [PATCH v5 10/14] arm64: apple: Add pinctrl nodes
Quoted 29 lines · Linus Walleij
Quoted 12 lines · Marc Zyngier
From: Mark Kettenis <[email protected]>
Add pinctrl nodes corresponding to the gpio,t8101 nodes in the Apple device tree for the Mac mini (M1, 2020).
Clock references are left out at the moment and will be added once the appropriate bindings have been settled upon.
Signed-off-by Mark Kettenis <[email protected]>Reviewed-by Linus Walleij <[email protected]>Signed-off-by Marc Zyngier <[email protected]>(...)
arch/arm64/boot/dts/apple/t8103.dtsi aic: interrupt-controller@23b100000 { · line 142
Quoted 7 lines
arch/arm64/boot/dts/apple/t8103.dtsi +7
-0+ pinctrl_ap: pinctrl@23c100000 { + compatible = "apple,t8103-pinctrl", "apple,pinctrl"; + reg = <0x2 0x3c100000 0x0 0x100000>; + + gpio-controller; + #gpio-cells = <2>; + gpio-ranges = <&pinctrl_ap 0 0 212>;In other discussions it turns out that the driver is abusing these gpio-ranges to find out how many pins are in each pinctrl instance. This is not the idea with gpio-ranges, these can be multiple and map different sets, so we need something like
Quoted 4 lines
apple,npins = <212>;
(+ bindings)or so...
Is it the driver that needs updating? Or the binding? I don't really care about the former, but the latter is more disruptive as it has impacts over both u-boot and at least OpenBSD.
How is that solved on other pinctrl blocks? I can't see anyone having a similar a similar property.
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Re: [PATCH v5 10/14] arm64: apple: Add pinctrl nodes
Quoted 2 lines
Date: Thu, 30 Sep 2021 09:00:49 +0100
From: Marc Zyngier <[email protected]>
Hi Linus and Marc,
Quoted 31 lines
Quoted 29 lines · Linus Walleij
Quoted 12 lines · Marc Zyngier
From: Mark Kettenis <[email protected]>
Add pinctrl nodes corresponding to the gpio,t8101 nodes in the Apple device tree for the Mac mini (M1, 2020).
Clock references are left out at the moment and will be added once the appropriate bindings have been settled upon.
Signed-off-by Mark Kettenis <[email protected]>Reviewed-by Linus Walleij <[email protected]>Signed-off-by Marc Zyngier <[email protected]>(...)
arch/arm64/boot/dts/apple/t8103.dtsi aic: interrupt-controller@23b100000 { · line 142
Quoted 7 lines
arch/arm64/boot/dts/apple/t8103.dtsi +7
-0+ pinctrl_ap: pinctrl@23c100000 { + compatible = "apple,t8103-pinctrl", "apple,pinctrl"; + reg = <0x2 0x3c100000 0x0 0x100000>; + + gpio-controller; + #gpio-cells = <2>; + gpio-ranges = <&pinctrl_ap 0 0 212>;In other discussions it turns out that the driver is abusing these gpio-ranges to find out how many pins are in each pinctrl instance. This is not the idea with gpio-ranges, these can be multiple and map different sets, so we need something like
Quoted 8 lines
Quoted 4 lines
apple,npins = <212>;
(+ bindings)or so...
Is it the driver that needs updating? Or the binding? I don't really care about the former, but the latter is more disruptive as it has impacts over both u-boot and at least OpenBSD.
I don't have a finished OpenBSD driver yet, and U-Boot support is still in the process of being upstreamed, so tweaking the binding a bit is not out of the question at this point. And as long as the gpio-ranges property continues to be there, things won't break anyway.
Quoted 2 lines
How is that solved on other pinctrl blocks? I can't see anyone having a similar a similar property.
I suspect most pinctrl blocks have a well-defined number of pins that is simply a #define in the driver. Here we don't really know what the hardware provides but the "Apple device tree" has a property that describes the number of pins, which varies between the different blocks.
Since there is a simple 1:1 mapping between pins and gpios it seemed natural to me to simply use the value from gpio-ranges. My thinking was that having a separate property to encode the number of pins just increases the chances of the two getting out of sync. But maybe that is the whole point Linus is trying to make; not all pins may actually provide GPIO functionality and gpio-ranges can be used to map only those pins that actually do. In this particular case I don't think it makes sense to map multiple ranges though as we will probably never know full details for all the pins.
FWIW, there are other U-Boot drivers that use gpio-ranges to get the pin count. But I suppose U-Boot has somewhat different standards than the Linux kernel, prioritising code size and such.
Re: [PATCH v5 10/14] arm64: apple: Add pinctrl nodes
In reply to Marc ZyngierQuoted 11 lines · Marc Zyngier
Quoted 9 lines
In other discussions it turns out that the driver is abusing these gpio-ranges to find out how many pins are in each pinctrl instance. This is not the idea with gpio-ranges, these can be multiple and map different sets, so we need something like
apple,npins = <212>;
(+ bindings)or so...
Is it the driver that needs updating? Or the binding?
Both, I guess.
Quoted 6 lines
I don't really
care about the former, but the latter is more disruptive as it has impacts over both u-boot and at least OpenBSD.How is that solved on other pinctrl blocks? I can't see anyone having a similar a similar property.
The Apple pincontroller is unique in having four instances using the same compatible string (I raised this as an issue too).
Most SoCs has one instance of a pin controller, with one compatible string and then we also know how many pins it has.
The maintainer seeme unhappy about my suggestion to name the four pin controllers after function and insist to use the same compatible for all four, which means they instead need to be parametrized, which means this parameter has to be added because ranges should not be used in this way.
I guess the code can survive using the ranges as a fallback at the cost of some more complex code.
Yours,
Linus Walleij
Re: [PATCH v5 10/14] arm64: apple: Add pinctrl nodes
In reply to Marc Zyngierarch/arm64/boot/dts/apple/t8103.dtsi
Quoted 18 lines · Marc Zyngier
From: Mark Kettenis <[email protected]>
Add pinctrl nodes corresponding to the gpio,t8101 nodes in the Apple device tree for the Mac mini (M1, 2020).
Clock references are left out at the moment and will be added once the appropriate bindings have been settled upon.
Signed-off-by Mark Kettenis <[email protected]>Reviewed-by Linus Walleij <[email protected]>Signed-off-by Marc Zyngier <[email protected]>--- arch/arm64/boot/dts/apple/t8103.dtsi | 83 ++++++++++++++++++++++++++++ 1 file changed, 83 insertions(+)arch/arm64/boot/dts/apple/t8103.dtsi +0
-0
[snip]
Looks good. Can you resend just this patch with the apple,npins properties added? Once that's settled in the binding (which seems to just be waiting on some linter issues) I can merge this and the rest of the DT changes through my tree.
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
Marc Zyngier
maintainerPATCH v5 11/14 arm64: apple: Add PCIe node
In reply to Marc ZyngierFrom: Mark Kettenis <[email protected]>
Add node corresponding to the apcie,t8103 node in the Apple device tree for the Mac mini (M1, 2020).
Power domain references and DART (IOMMU) references are left out at the moment and will be added once the appropriate bindings have been settled upon.
--- arch/arm64/boot/dts/apple/t8103.dtsi | 63 ++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+)
arch/arm64/boot/dts/apple/t8103.dtsi +63 -0
@@ -214,5 +214,68 @@ pinctrl_smc: pinctrl@23e820000 { <AIC_IRQ 396 IRQ_TYPE_LEVEL_HIGH>, <AIC_IRQ 397 IRQ_TYPE_LEVEL_HIGH>; }; + + pcie0: pcie@690000000 { + compatible = "apple,t8103-pcie", "apple,pcie"; + device_type = "pci"; + + reg = <0x6 0x90000000 0x0 0x1000000>, + <0x6 0x80000000 0x0 0x100000>, + <0x6 0x81000000 0x0 0x4000>, + <0x6 0x82000000 0x0 0x4000>, + <0x6 0x83000000 0x0 0x4000>; + reg-names = "config", "rc", "port0", "port1", "port2"; + + interrupt-parent = <&aic>; + interrupts = <AIC_IRQ 695 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 698 IRQ_TYPE_LEVEL_HIGH>, + <AIC_IRQ 701 IRQ_TYPE_LEVEL_HIGH>; + + msi-controller; + msi-parent = <&pcie0>; + msi-ranges = <&aic AIC_IRQ 704 IRQ_TYPE_EDGE_RISING 32>; + + bus-range = <0 3>; + #address-cells = <3>; + #size-cells = <2>; + ranges = <0x43000000 0x6 0xa0000000 0x6 0xa0000000 0x0 0x20000000>, + <0x02000000 0x0 0xc0000000 0x6 0xc0000000 0x0 0x40000000>; + + pinctrl-0 = <&pcie_pins>; + pinctrl-names = "default"; + + pci@0,0 { + device_type = "pci"; + reg = <0x0 0x0 0x0 0x0 0x0>; + reset-gpios = <&pinctrl_ap 152 0>; + max-link-speed = <2>; + + #address-cells = <3>; + #size-cells = <2>; + ranges; + }; + + pci@1,0 { + device_type = "pci"; + reg = <0x800 0x0 0x0 0x0 0x0>; + reset-gpios = <&pinctrl_ap 153 0>; + max-link-speed = <2>; + + #address-cells = <3>; + #size-cells = <2>; + ranges; + }; + + pci@2,0 { + device_type = "pci"; + reg = <0x1000 0x0 0x0 0x0 0x0>; + reset-gpios = <&pinctrl_ap 33 0>; + max-link-speed = <1>; + + #address-cells = <3>; + #size-cells = <2>; + ranges; + }; + }; }; };
Signature · 1 line
2.30.2
Re: [PATCH v5 11/14] arm64: apple: Add PCIe node
Quoted 9 lines · Marc Zyngier
From: Mark Kettenis <[email protected]>
Add node corresponding to the apcie,t8103 node in the Apple device tree for the Mac mini (M1, 2020).
Power domain references and DART (IOMMU) references are left out at the moment and will be added once the appropriate bindings have been settled upon.
Quoted 8 lines
Acked-by Marc Zyngier <[email protected]>Signed-off-by Mark Kettenis <[email protected]>Signed-off-by Marc Zyngier <[email protected]>--- arch/arm64/boot/dts/apple/t8103.dtsi | 63 ++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+)
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
Marc Zyngier
maintainerPATCH v5 12/14 arm64: dts: apple: t8103: Add PCIe DARTs
In reply to Marc ZyngierPCIe on the Apple M1 (aka t8103) requires the use of IOMMUs (aka DARTs). Add the three instances that deal with the internal PCIe ports and route each port's traffic through its DART.
--- arch/arm64/boot/dts/apple/t8103.dtsi | 30 ++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+)
arch/arm64/boot/dts/apple/t8103.dtsi +30 -0
@@ -215,6 +215,30 @@ pinctrl_smc: pinctrl@23e820000 { <AIC_IRQ 397 IRQ_TYPE_LEVEL_HIGH>; }; + pcie0_dart_0: dart@681008000 { + compatible = "apple,t8103-dart"; + reg = <0x6 0x81008000 0x0 0x4000>; + #iommu-cells = <1>; + interrupt-parent = <&aic>; + interrupts = <AIC_IRQ 696 IRQ_TYPE_LEVEL_HIGH>; + }; + + pcie0_dart_1: dart@682008000 { + compatible = "apple,t8103-dart"; + reg = <0x6 0x82008000 0x0 0x4000>; + #iommu-cells = <1>; + interrupt-parent = <&aic>; + interrupts = <AIC_IRQ 699 IRQ_TYPE_LEVEL_HIGH>; + }; + + pcie0_dart_2: dart@683008000 { + compatible = "apple,t8103-dart"; + reg = <0x6 0x83008000 0x0 0x4000>; + #iommu-cells = <1>; + interrupt-parent = <&aic>; + interrupts = <AIC_IRQ 702 IRQ_TYPE_LEVEL_HIGH>; + }; + pcie0: pcie@690000000 { compatible = "apple,t8103-pcie", "apple,pcie"; device_type = "pci";
@@ -235,6 +259,12 @@ pcie0: pcie@690000000 { msi-parent = <&pcie0>; msi-ranges = <&aic AIC_IRQ 704 IRQ_TYPE_EDGE_RISING 32>; + + iommu-map = <0x100 &pcie0_dart_0 1 1>, + <0x200 &pcie0_dart_1 1 1>, + <0x300 &pcie0_dart_2 1 1>; + iommu-map-mask = <0xff00>; + bus-range = <0 3>; #address-cells = <3>; #size-cells = <2>;
Signature · 1 line
2.30.2
Re: [PATCH v5 12/14] arm64: dts: apple: t8103: Add PCIe DARTs
Quoted 9 lines · Marc Zyngier
PCIe on the Apple M1 (aka t8103) requires the use of IOMMUs (aka DARTs). Add the three instances that deal with the internal PCIe ports and route each port's traffic through its DART.
Signed-off-by Marc Zyngier <[email protected]>--- arch/arm64/boot/dts/apple/t8103.dtsi | 30 ++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+)
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
Marc Zyngier
maintainerPATCH v5 13/14 arm64: dts: apple: t8103: Add root port interrupt routing
In reply to Marc ZyngierAdd the interrupt-map properties that are required for INTx signalling.
--- arch/arm64/boot/dts/apple/t8103.dtsi | 33 +++++++++++++++++++++++++--- 1 file changed, 30 insertions(+), 3 deletions(-)
arch/arm64/boot/dts/apple/t8103.dtsi +30 -3
@@ -274,7 +274,7 @@ pcie0: pcie@690000000 { pinctrl-0 = <&pcie_pins>; pinctrl-names = "default"; - pci@0,0 { + port00: pci@0,0 { device_type = "pci"; reg = <0x0 0x0 0x0 0x0 0x0>; reset-gpios = <&pinctrl_ap 152 0>;
@@ -283,9 +283,18 @@ pci@0,0 { #address-cells = <3>; #size-cells = <2>; ranges; + + interrupt-controller; + #interrupt-cells = <1>; + + interrupt-map-mask = <0 0 0 7>; + interrupt-map = <0 0 0 1 &port00 0 0 0 0>, + <0 0 0 2 &port00 0 0 0 1>, + <0 0 0 3 &port00 0 0 0 2>, + <0 0 0 4 &port00 0 0 0 3>; }; - pci@1,0 { + port01: pci@1,0 { device_type = "pci"; reg = <0x800 0x0 0x0 0x0 0x0>; reset-gpios = <&pinctrl_ap 153 0>;
@@ -294,9 +303,18 @@ pci@1,0 { #address-cells = <3>; #size-cells = <2>; ranges; + + interrupt-controller; + #interrupt-cells = <1>; + + interrupt-map-mask = <0 0 0 7>; + interrupt-map = <0 0 0 1 &port01 0 0 0 0>, + <0 0 0 2 &port01 0 0 0 1>, + <0 0 0 3 &port01 0 0 0 2>, + <0 0 0 4 &port01 0 0 0 3>; }; - pci@2,0 { + port02: pci@2,0 { device_type = "pci"; reg = <0x1000 0x0 0x0 0x0 0x0>; reset-gpios = <&pinctrl_ap 33 0>;
@@ -305,6 +323,15 @@ pci@2,0 { #address-cells = <3>; #size-cells = <2>; ranges; + + interrupt-controller; + #interrupt-cells = <1>; + + interrupt-map-mask = <0 0 0 7>; + interrupt-map = <0 0 0 1 &port02 0 0 0 0>, + <0 0 0 2 &port02 0 0 0 1>, + <0 0 0 3 &port02 0 0 0 2>, + <0 0 0 4 &port02 0 0 0 3>; }; }; };
Signature · 1 line
2.30.2
Re: [PATCH v5 13/14] arm64: dts: apple: t8103: Add root port interrupt routing
Quoted 9 lines · Marc Zyngier
Add the interrupt-map properties that are required for INTx signalling.
Tested-by Alyssa Rosenzweig <[email protected]>Signed-off-by Marc Zyngier <[email protected]>--- arch/arm64/boot/dts/apple/t8103.dtsi | 33 +++++++++++++++++++++++++--- 1 file changed, 30 insertions(+), 3 deletions(-)
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
Marc Zyngier
maintainerPATCH v5 14/14 arm64: dts: apple: j274: Expose PCI node for the Ethernet MAC address
In reply to Marc ZyngierAt the moment, all the Minis running Linux have the same MAC address (00:10:18:00:00:00), which is a bit annoying.
Expose the PCI node corresponding to the Ethernet device, and declare a 'local-mac-address' property. The bootloader will update it (m1n1 already has the required feature). And if it doesn't, then the default value is already present in the DT.
This relies on forcing the bus number for each port so that the endpoints connected to them are correctly numbered (and keeps dtc quiet).
--- arch/arm64/boot/dts/apple/t8103-j274.dts | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+)
arch/arm64/boot/dts/apple/t8103-j274.dts +23 -0
@@ -17,6 +17,7 @@ / { aliases { serial0 = &serial0; + ethernet0 = ðernet0; }; chosen {
@@ -43,3 +44,25 @@ memory@800000000 { &serial0 { status = "okay"; }; + +/* + * Force the bus number assignments so that we can declare some of the + * on-board devices and properties that are populated by the bootloader + * (such as MAC addresses). + */ +&port00 { + bus-range = <1 1>; +}; + +&port01 { + bus-range = <2 2>; +}; + +&port02 { + bus-range = <3 3>; + ethernet0: pci@0,0 { + reg = <0x30000 0x0 0x0 0x0 0x0>; + /* To be filled by the loader */ + local-mac-address = [00 10 18 00 00 00]; + }; +};
Signature · 1 line
2.30.2
Re: [PATCH v5 14/14] arm64: dts: apple: j274: Expose PCI node for the Ethernet MAC address
Quoted 8 lines · Marc Zyngier
At the moment, all the Minis running Linux have the same MAC address (00:10:18:00:00:00), which is a bit annoying.
Expose the PCI node corresponding to the Ethernet device, and declare a 'local-mac-address' property. The bootloader will update it (m1n1 already has the required feature). And if it doesn't, then the default value is already present in the DT.
Quoted 9 lines
This relies on forcing the bus number for each port so that the endpoints connected to them are correctly numbered (and keeps dtc quiet).
Signed-off-by Marc Zyngier <[email protected]>--- arch/arm64/boot/dts/apple/t8103-j274.dts | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+)
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
Quoted 42 lines · Marc Zyngier
This is v5 of the series adding PCIe support for the M1 SoC. Not a lot has changed this time around, and most of what I was saying in [1] is still valid.
Very little has changed code wise (a couple of bug fixes). The series however now carries a bunch of DT updates so that people can actually make use of PCIe on an M1 box (OK, not quite, you will still need [2], or whatever version replaces it). The corresponding bindings are either already merged, or queued for 5.16 (this is the case for the PCI binding).
It all should be in a state that makes it mergeable (yeah, I said that last time... I mean it this time! ;-).
As always, comments welcome.
M.[1] https://lore.kernel.org/r/[email protected]
[2] https://lore.kernel.org/r/[email protected]Alyssa Rosenzweig (2):
PCI: apple: Add initial hardware bring-up
PCI: apple: Set up reference clocks when probingMarc Zyngier (10):
irqdomain: Makeof_phandle_args_to_fwspecgenerally available of/irq: Allow matching of an interrupt-map local to an interrupt
controller
PCI: of: Allow matching of an interrupt-map local to a PCI device
PCI: apple: Add INTx and per-port interrupt support
PCI: apple: Implement MSI support
iommu/dart: Exclude MSI doorbell from PCIe device IOVA range
PCI: apple: Configure RID to SID mapper on device addition
arm64: dts: apple: t8103: Add PCIe DARTs
arm64: dts: apple: t8103: Add root port interrupt routing
arm64: dts: apple: j274: Expose PCI node for the Ethernet MAC addressMark Kettenis (2):
arm64: apple: Add pinctrl nodes
arm64: apple: Add PCIe node
Quoted 13 lines
MAINTAINERS | 7 + arch/arm64/boot/dts/apple/t8103-j274.dts | 23 + arch/arm64/boot/dts/apple/t8103.dtsi | 203 ++++++ drivers/iommu/apple-dart.c | 27 + drivers/of/irq.c | 17 +- drivers/pci/controller/Kconfig | 17 + drivers/pci/controller/Makefile | 1 + drivers/pci/controller/pcie-apple.c | 822 +++++++++++++++++++++++ drivers/pci/of.c | 10 +- include/linux/irqdomain.h | 4 + kernel/irq/irqdomain.c | 6 +- 11 files changed, 1127 insertions(+), 10 deletions(-) create mode 100644 drivers/pci/controller/pcie-apple.c
I have applied (with very minor log changes) patches [1-9] to pci/apple for v5.16, I expect the dts changes to go via the arm-soc tree separately, please let me know if that works for you.
Thanks,
Lorenzo
Marc Zyngier
maintainerHi Lorenzo,
[+LinusW, Arnd]
Quoted 58 lines · Lorenzo Pieralisi
Quoted 42 lines · Marc Zyngier
This is v5 of the series adding PCIe support for the M1 SoC. Not a lot has changed this time around, and most of what I was saying in [1] is still valid.
Very little has changed code wise (a couple of bug fixes). The series however now carries a bunch of DT updates so that people can actually make use of PCIe on an M1 box (OK, not quite, you will still need [2], or whatever version replaces it). The corresponding bindings are either already merged, or queued for 5.16 (this is the case for the PCI binding).
It all should be in a state that makes it mergeable (yeah, I said that last time... I mean it this time! ;-).
As always, comments welcome.
M.[1] https://lore.kernel.org/r/[email protected]
[2] https://lore.kernel.org/r/[email protected]Alyssa Rosenzweig (2):
PCI: apple: Add initial hardware bring-up
PCI: apple: Set up reference clocks when probingMarc Zyngier (10):
irqdomain: Makeof_phandle_args_to_fwspecgenerally available of/irq: Allow matching of an interrupt-map local to an interrupt
controller
PCI: of: Allow matching of an interrupt-map local to a PCI device
PCI: apple: Add INTx and per-port interrupt support
PCI: apple: Implement MSI support
iommu/dart: Exclude MSI doorbell from PCIe device IOVA range
PCI: apple: Configure RID to SID mapper on device addition
arm64: dts: apple: t8103: Add PCIe DARTs
arm64: dts: apple: t8103: Add root port interrupt routing
arm64: dts: apple: j274: Expose PCI node for the Ethernet MAC addressMark Kettenis (2):
arm64: apple: Add pinctrl nodes
arm64: apple: Add PCIe nodeQuoted 13 lines
MAINTAINERS | 7 + arch/arm64/boot/dts/apple/t8103-j274.dts | 23 + arch/arm64/boot/dts/apple/t8103.dtsi | 203 ++++++ drivers/iommu/apple-dart.c | 27 + drivers/of/irq.c | 17 +- drivers/pci/controller/Kconfig | 17 + drivers/pci/controller/Makefile | 1 + drivers/pci/controller/pcie-apple.c | 822 +++++++++++++++++++++++ drivers/pci/of.c | 10 +- include/linux/irqdomain.h | 4 + kernel/irq/irqdomain.c | 6 +- 11 files changed, 1127 insertions(+), 10 deletions(-) create mode 100644 drivers/pci/controller/pcie-apple.c
Quoted 3 lines
I have applied (with very minor log changes) patches [1-9] to pci/apple for v5.16, I expect the dts changes to go via the arm-soc tree separately, please let me know if that works for you.
Yes, that's absolutely fine. I hope we can resolve the issue on the pinctrl binding pretty quickly, and get the arm-soc folks to pull the DT changes in for 5.16 too.
This would make the Mini a usable machine with a mainline kernel.
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Quoted 3 lines · Marc Zyngier
Yes, that's absolutely fine. I hope we can resolve the issue on the pinctrl binding pretty quickly, and get the arm-soc folks to pull the DT changes in for 5.16 too.
I think I ACKed a patch for apple,npins = <> yesterday.
Quoted 1 line
This would make the Mini a usable machine with a mainline kernel.
That seems useful.
Yours,
Linus Walleij
Quoted 7 lines · Linus Walleij
Quoted 3 lines · Marc Zyngier
Yes, that's absolutely fine. I hope we can resolve the issue on the pinctrl binding pretty quickly, and get the arm-soc folks to pull the DT changes in for 5.16 too.
I think I ACKed a patch for apple,npins = <> yesterday.
You reviewed it :)
It still needs some fixes to pass the schema linter though.
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
Quoted 58 lines · Lorenzo Pieralisi
Quoted 42 lines · Marc Zyngier
This is v5 of the series adding PCIe support for the M1 SoC. Not a lot has changed this time around, and most of what I was saying in [1] is still valid.
Very little has changed code wise (a couple of bug fixes). The series however now carries a bunch of DT updates so that people can actually make use of PCIe on an M1 box (OK, not quite, you will still need [2], or whatever version replaces it). The corresponding bindings are either already merged, or queued for 5.16 (this is the case for the PCI binding).
It all should be in a state that makes it mergeable (yeah, I said that last time... I mean it this time! ;-).
As always, comments welcome.
M.[1] https://lore.kernel.org/r/[email protected]
[2] https://lore.kernel.org/r/[email protected]Alyssa Rosenzweig (2):
PCI: apple: Add initial hardware bring-up
PCI: apple: Set up reference clocks when probingMarc Zyngier (10):
irqdomain: Makeof_phandle_args_to_fwspecgenerally available of/irq: Allow matching of an interrupt-map local to an interrupt
controller
PCI: of: Allow matching of an interrupt-map local to a PCI device
PCI: apple: Add INTx and per-port interrupt support
PCI: apple: Implement MSI support
iommu/dart: Exclude MSI doorbell from PCIe device IOVA range
PCI: apple: Configure RID to SID mapper on device addition
arm64: dts: apple: t8103: Add PCIe DARTs
arm64: dts: apple: t8103: Add root port interrupt routing
arm64: dts: apple: j274: Expose PCI node for the Ethernet MAC addressMark Kettenis (2):
arm64: apple: Add pinctrl nodes
arm64: apple: Add PCIe nodeQuoted 13 lines
MAINTAINERS | 7 + arch/arm64/boot/dts/apple/t8103-j274.dts | 23 + arch/arm64/boot/dts/apple/t8103.dtsi | 203 ++++++ drivers/iommu/apple-dart.c | 27 + drivers/of/irq.c | 17 +- drivers/pci/controller/Kconfig | 17 + drivers/pci/controller/Makefile | 1 + drivers/pci/controller/pcie-apple.c | 822 +++++++++++++++++++++++ drivers/pci/of.c | 10 +- include/linux/irqdomain.h | 4 + kernel/irq/irqdomain.c | 6 +- 11 files changed, 1127 insertions(+), 10 deletions(-) create mode 100644 drivers/pci/controller/pcie-apple.c
Quoted 3 lines
I have applied (with very minor log changes) patches [1-9] to pci/apple for v5.16, I expect the dts changes to go via the arm-soc tree separately, please let me know if that works for you.
FYI, I pushed patches 1-3 to kernelCI and didn't see any regressions. I am a bit worried about changes to the DT interrupt parsing and ancient platforms (such as PowerMacs). Most likely there wouldn't be any report until -rc1 or months later on those old systems.
Rob
Quoted 4 lines · Rob Herring
FYI, I pushed patches 1-3 to kernelCI and didn't see any regressions. I am a bit worried about changes to the DT interrupt parsing and ancient platforms (such as PowerMacs). Most likely there wouldn't be any report until -rc1 or months later on those old systems.
Lets page the PPC lists to see if someone can test on some powermac.
Linus Walleij
Marc Zyngier
maintainerQuoted 9 lines · Linus Walleij
Quoted 4 lines · Rob Herring
FYI, I pushed patches 1-3 to kernelCI and didn't see any regressions. I am a bit worried about changes to the DT interrupt parsing and ancient platforms (such as PowerMacs). Most likely there wouldn't be any report until -rc1 or months later on those old systems.
Lets page the PPC lists to see if someone can test on some powermac.
/me eyes the XServe-G5 that hasn't been powered on in 10 years. What could possibly go wrong?
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Quoted 8 lines · Linus Walleij
Quoted 4 lines · Rob Herring
FYI, I pushed patches 1-3 to kernelCI and didn't see any regressions. I am a bit worried about changes to the DT interrupt parsing and ancient platforms (such as PowerMacs). Most likely there wouldn't be any report until -rc1 or months later on those old systems.
Lets page the PPC lists to see if someone can test on some powermac.
It boots and everything seems fine on an iMac-G5 of mine.
I don't have access to any other powermac hardware at the moment due to the lockdown here.
cheers