Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1397983imm; Fri, 27 Jul 2018 17:06:26 -0700 (PDT) X-Google-Smtp-Source: AAOMgpeX6q34u2OAooHA9VA4DwYhRv0mp0e+kb2PlAtwwHgNUvCA/S6lua4Q6mbsgauGnR21ggD8 X-Received: by 2002:a63:d309:: with SMTP id b9-v6mr7844509pgg.163.1532736386765; Fri, 27 Jul 2018 17:06:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532736386; cv=none; d=google.com; s=arc-20160816; b=GJG6JsnG659UyD6CF8HnB3QYq8/ItB9J60bF4inFaK50jqgXN3uo7y2P7Sje5p51K6 2Ql0k0l8BgTJmwjSzbUALwb485qdn3HqoZ8byxZHumeHnIqTh2yWdLaBY511JtOMXoPS 07IHTiIhpViqXhA3CFZdOt4G+F+du1bHpiN7J0m9vHtaTGcMGQzBPHISUsu1juTuOqHj VhY48Fi3qbiP+6IeI2XAlgoOq/WkMXAeD3QV/EC+0/bZxsoSt6fjXS4QwqF8b65BxdU1 ljq3mc1lk0TyuEEbgKwVDQv/Got4XmGlajvzqubMEiAY1C5O6A8kpOTseZG1uMh5gknH L8yg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=IC172BlHHoYPqNx83nrSQasv5/U8cKJ2RbFMr1cwNmU=; b=TLGa7rcr01WHomJB7hGV/7EjqWpnNDJjyuYdXniyrxJY3mDAjqyVoEd0CB93QO575g BnbjoFdl5eqIt5ibvqyKdLeO5zP85znZ9nocqYdrvrKLiRv+lFQgul35bf6zCQdzRVZM RQF1QOytBXO5UXue5CEznCe5j8s52j8wQ8yoi4dozLdKrJYYSfVrn+VKmhvguafFH4+Z 0CjfjGFQthqDwe77aBQLq6IUDKcJC37ufXmcfFVkv9DItx3IA1c/xrcEc0uc9cXZb/WL yAJVvFKQPL5h7PMXm05pw0Lyxs0Om9bjydSnitAwJtkkIi/2WirZVjVoeN4cj40dGiao grSg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@wdc.com header.s=dkim.wdc.com header.b="BeI0lxq/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u3-v6si4780300plb.2.2018.07.27.17.06.12; Fri, 27 Jul 2018 17:06:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@wdc.com header.s=dkim.wdc.com header.b="BeI0lxq/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389225AbeG1B3I (ORCPT + 99 others); Fri, 27 Jul 2018 21:29:08 -0400 Received: from esa5.hgst.iphmx.com ([216.71.153.144]:11251 "EHLO esa5.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388893AbeG1B3I (ORCPT ); Fri, 27 Jul 2018 21:29:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wdc.com; i=@wdc.com; q=dns/txt; s=dkim.wdc.com; t=1532736294; x=1564272294; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=G1J6hjMs2b/FDXS4BiWaNwhy1C9ncRjwQhEggzfuPsg=; b=BeI0lxq/vT58zWUy5xTL0Sd1nnSKAJsnyetkgYYtDtpKxPu7nv/Y5HqJ dzlyIn3hfVxoSOko/lpqwtjfb3UMoi18oUeRxZjjmgr/kzQqsHYsk96nY zPvZIyZGyLzvJYmqZNvsn2asDqZl1yBthEV+0c6hz/BgoOccDek2cOA6b bf9xTCIo8J7r9SdA0chOFOar8QRRGktgZS9X75woqTaOFWa5KxG0U3qqs fEsWpxlWJIdcfBr+esfyX/BdFDtfjoO6WwgeASxYGagSe5hUJuNnstKnY Td/teXOLsIq/CnqwMgbK4TZokYrNtvnSLBIWO0L7ECFcTQVufziyIQSh9 A==; X-IronPort-AV: E=Sophos;i="5.51,411,1526313600"; d="scan'208";a="86033634" Received: from uls-op-cesaip01.wdc.com (HELO uls-op-cesaep01.wdc.com) ([199.255.45.14]) by ob1.hgst.iphmx.com with ESMTP; 28 Jul 2018 08:04:53 +0800 Received: from uls-op-cesaip01.wdc.com ([10.248.3.36]) by uls-op-cesaep01.wdc.com with ESMTP; 27 Jul 2018 16:53:25 -0700 Received: from c02v91rdhtd5.sdcorp.global.sandisk.com (HELO [10.196.159.148]) ([10.196.159.148]) by uls-op-cesaip01.wdc.com with ESMTP; 27 Jul 2018 17:04:52 -0700 Subject: Re: [PATCH 7/9] irqchip: add a RISC-V PLIC driver To: Christoph Hellwig , "tglx@linutronix.de" , "palmer@sifive.com" , "jason@lakedaemon.net" , "marc.zyngier@arm.com" , "robh+dt@kernel.org" , "mark.rutland@arm.com" Cc: "anup@brainfault.org" , "devicetree@vger.kernel.org" , "aou@eecs.berkeley.edu" , "linux-kernel@vger.kernel.org" , "linux-riscv@lists.infradead.org" , "shorne@gmail.com" References: <20180726143723.16585-1-hch@lst.de> <20180726143723.16585-8-hch@lst.de> From: Atish Patra Message-ID: <1b3f6066-0c7c-a5f5-75ad-559fe81091ee@wdc.com> Date: Fri, 27 Jul 2018 17:04:52 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180726143723.16585-8-hch@lst.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/26/18 7:38 AM, Christoph Hellwig wrote: > This patch adds a driver for the Platform Level Interrupt Controller (PLIC) > specified as part of the RISC-V supervisor level ISA manual, in the memory > layout implemented by SiFive and qemu. > > The PLIC connects global interrupt sources to the local interrupt controller > on each hart. > > This driver is based on the driver in the RISC-V tree from Palmer Dabbelt, > but has been almost entirely rewritten since. > > Signed-off-by: Christoph Hellwig I tried to boot HighFive Unleashed with the patch series after applying all the patches from riscv-all branch except timer & irq patches. It gets stuck pretty early. Here is my github repo with all the changes: https://github.com/atishp04/riscv-linux/commits/master_chris_cleanup_hifive I am still looking into it. Palmer: Did I miss something? FWIW, here is the boot log. --------- Boot log ------------------------------------------- [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=5 [ 0.000000] NR_IRQS: 0, nr_irqs: 0, preallocated irqs: 0 [ 0.000000] plic: mapped 53 interrupts to 4 (out of 9) handlers. [ 0.000000] clocksource: riscv_clocksource: mask: 0xffffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns [ 0.000000] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=10000) [ 0.010000] pid_max: default: 32768 minimum: 301 [ 0.010000] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes) [ 0.020000] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes) [ 0.020000] Hierarchical SRCU implementation. [ 0.030000] smp: Bringing up secondary CPUs ... > --- > drivers/irqchip/Kconfig | 13 ++ > drivers/irqchip/Makefile | 1 + > drivers/irqchip/irq-riscv-plic.c | 219 +++++++++++++++++++++++++++++++ > 3 files changed, 233 insertions(+) > create mode 100644 drivers/irqchip/irq-riscv-plic.c > > diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig > index e9233db16e03..5ac6dd922a0d 100644 > --- a/drivers/irqchip/Kconfig > +++ b/drivers/irqchip/Kconfig > @@ -372,3 +372,16 @@ config QCOM_PDC > IRQs for Qualcomm Technologies Inc (QTI) mobile chips. > > endmenu > + > +config RISCV_PLIC > + bool "Platform-Level Interrupt Controller" > + depends on RISCV > + default y > + help > + This enables support for the PLIC chip found in standard RISC-V > + systems. The PLIC controls devices interrupts and connects them to > + each core's local interrupt controller. Aside from timer and > + software interrupts, all other interrupt sources (MSI, GPIO, etc) > + are subordinate to the PLIC. > + > + If you don't know what to do here, say Y. > diff --git a/drivers/irqchip/Makefile b/drivers/irqchip/Makefile > index 15f268f646bf..bf9238da8a31 100644 > --- a/drivers/irqchip/Makefile > +++ b/drivers/irqchip/Makefile > @@ -87,3 +87,4 @@ obj-$(CONFIG_MESON_IRQ_GPIO) += irq-meson-gpio.o > obj-$(CONFIG_GOLDFISH_PIC) += irq-goldfish-pic.o > obj-$(CONFIG_NDS32) += irq-ativic32.o > obj-$(CONFIG_QCOM_PDC) += qcom-pdc.o > +obj-$(CONFIG_RISCV_PLIC) += irq-riscv-plic.o > diff --git a/drivers/irqchip/irq-riscv-plic.c b/drivers/irqchip/irq-riscv-plic.c > new file mode 100644 > index 000000000000..274fe2cba544 > --- /dev/null > +++ b/drivers/irqchip/irq-riscv-plic.c > @@ -0,0 +1,219 @@ > +// SPDX-License-Identifier: GPL-2.0 > +/* > + * Copyright (C) 2017 SiFive > + * Copyright (C) 2018 Christoph Hellwig > + */ > +#define pr_fmt(fmt) "plic: " fmt > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > + > +/* > + * From the RISC-V Priviledged Spec v1.10: > + * > + * Global interrupt sources are assigned small unsigned integer identifiers, > + * beginning at the value 1. An interrupt ID of 0 is reserved to mean "no > + * interrupt". Interrupt identifiers are also used to break ties when two or > + * more interrupt sources have the same assigned priority. Smaller values of > + * interrupt ID take precedence over larger values of interrupt ID. > + * > + * While the RISC-V supervisor spec doesn't define the maximum number of > + * devices supported by the PLIC, the largest number supported by devices > + * marked as 'riscv,plic0' (which is the only device type this driver supports, > + * and is the only extant PLIC as of now) is 1024. As mentioned above, device > + * 0 is defined to be non-existent so this device really only supports 1023 > + * devices. > + */ > +#define MAX_DEVICES 1024 > +#define MAX_CONTEXTS 15872 > + Is there any way we can preserve some of the comments in the original patch about memory-mapped control registers or at least a reference where to find the register offset calculations? IMHO, it is helpful for anybody who is not familiar with the details. > +/* > + * Each interrupt source has a priority register associated with it. > + * We always hardwire it to one in Linux. > + */ > +#define PRIORITY_BASE 0 > +#define PRIORITY_PER_ID 4 > + > +/* > + * Each hart context has a vector of interupt enable bits associated with it. > + * There's one bit for each interrupt source. > + */ > +#define ENABLE_BASE 0x2000 > +#define ENABLE_PER_HART 0x80 > + > +/* > + * Each hart context has a set of control registers associated with it. Right > + * now there's only two: a source priority threshold over which the hart will > + * take an interrupt, and a register to claim interrupts. > + */ > +#define CONTEXT_BASE 0x200000 > +#define CONTEXT_PER_HART 0x1000 > +#define CONTEXT_THRESHOLD 0x00 > +#define CONTEXT_CLAIM 0x04 > + > +static void __iomem *plic_regs; > + > +static inline void __iomem *plic_hart_offset(int ctxid) > +{ > + return plic_regs + CONTEXT_BASE + ctxid * CONTEXT_PER_HART; > +} > + > +/* > + * Protect mask operations on the registers given that we can't assume that > + * atomic memory operations work on them. > + */ > +static DEFINE_SPINLOCK(plic_toggle_lock); > + > +static inline void plic_toggle(int ctxid, int hwirq, int enable) > +{ > + u32 __iomem *reg = plic_regs + ENABLE_BASE + ctxid * ENABLE_PER_HART; shouldn't it be u32 __iomem *reg = plic_regs + ENABLE_BASE + ctxid * ENABLE_PER_HART + (hwirq / 32) * 4; Without that change, plic_handle_irq() gets called before irq mapping as plic was not disabled for that irq. As per comment in the original patch, -------------------------------------------------------------- * base + 0x002000: Enable bits for sources 0-31 on context 0 * base + 0x002004: Enable bits for sources 32-63 on context 0 -------------------------------------------------------------- > + u32 hwirq_mask = 1 << (hwirq % 32); > + > + spin_lock(&plic_toggle_lock); > + if (enable) > + writel(readl(reg) | hwirq_mask, reg); > + else > + writel(readl(reg) & ~hwirq_mask, reg); > + spin_unlock(&plic_toggle_lock); > +} > + > +static inline void plic_irq_toggle(struct irq_data *d, int enable) > +{ > + int cpu; > + > + writel(enable, plic_regs + PRIORITY_BASE + d->hwirq * PRIORITY_PER_ID); > + for_each_present_cpu(cpu) > + plic_toggle(cpu, d->hwirq, enable); > +} > + > +static void plic_irq_enable(struct irq_data *d) > +{ > + plic_irq_toggle(d, 1); > +} > + > +static void plic_irq_disable(struct irq_data *d) > +{ > + plic_irq_toggle(d, 0); > +} > + > +static struct irq_chip plic_chip = { > + .name = "riscv,plic0", > + /* > + * There is no need to mask/unmask PLIC interrupts. They are "masked" > + * by reading claim and "unmasked" when writing it back. > + */ > + .irq_enable = plic_irq_enable, > + .irq_disable = plic_irq_disable, > +}; > + > +static int plic_irqdomain_map(struct irq_domain *d, unsigned int irq, > + irq_hw_number_t hwirq) > +{ > + irq_set_chip_and_handler(irq, &plic_chip, handle_simple_irq); > + irq_set_chip_data(irq, NULL); > + irq_set_noprobe(irq); > + return 0; > +} > + > +static const struct irq_domain_ops plic_irqdomain_ops = { > + .map = plic_irqdomain_map, > + .xlate = irq_domain_xlate_onecell, > +}; > + > +static struct irq_domain *plic_irqdomain; > + > +/* > + * Handling an interrupt is a two-step process: first you claim the interrupt > + * by reading the claim register, then you complete the interrupt by writing > + * that source ID back to the same claim register. This automatically enables > + * and disables the interrupt, so there's nothing else to do. > + */ > +static void plic_handle_irq(struct pt_regs *regs) > +{ > + void __iomem *claim = > + plic_hart_offset(smp_processor_id()) + CONTEXT_CLAIM; > + irq_hw_number_t hwirq; > + > + csr_clear(sie, SIE_STIE); > + while ((hwirq = readl(claim))) { > + int irq = irq_find_mapping(plic_irqdomain, hwirq); > + > + if (unlikely(irq <= 0)) { > + pr_warn_ratelimited("can't find mapping for hwirq %lu\n", > + hwirq); Ratlimiting the warning message here didn't help as ack_bad_irq() still print message still flooded the console without any useful info. Regards, Atish > + ack_bad_irq(irq); > + } else { > + generic_handle_irq(irq); > + } > + writel(hwirq, claim); > + } > + csr_set(sie, SIE_STIE); > +} > + > +static int __init plic_init(struct device_node *node, > + struct device_node *parent) > +{ > + int error = 0, nr_mapped = 0, nr_handlers, cpu; > + u32 nr_irqs; > + > + if (plic_regs) { > + pr_warning("PLIC already present.\n"); > + return -ENXIO; > + } > + > + plic_regs = of_iomap(node, 0); > + if (WARN_ON(!plic_regs)) > + return -EIO; > + > + error = -EINVAL; > + of_property_read_u32(node, "riscv,ndev", &nr_irqs); > + if (WARN_ON(!nr_irqs)) > + goto out_iounmap; > + > + nr_handlers = of_irq_count(node); > + if (WARN_ON(!nr_handlers)) > + goto out_iounmap; > + if (WARN_ON(nr_handlers < num_possible_cpus())) > + goto out_iounmap; > + > + error = -ENOMEM; > + plic_irqdomain = irq_domain_add_linear(node, nr_irqs + 1, > + &plic_irqdomain_ops, NULL); > + if (WARN_ON(!plic_irqdomain)) > + goto out_iounmap; > + > + /* > + * We assume that each present hart is wire up to the PLIC. > + * If that isn't the case in the future this code will need to be > + * modified. > + */ > + for_each_present_cpu(cpu) { > + irq_hw_number_t hwirq; > + > + /* priority must be > threshold to trigger an interrupt */ > + writel(0, plic_hart_offset(cpu) + CONTEXT_THRESHOLD); > + for (hwirq = 1; hwirq <= nr_irqs; ++hwirq) > + plic_toggle(cpu, hwirq, 0); > + nr_mapped++; > + } > + > + pr_info("mapped %d interrupts to %d (out of %d) handlers.\n", > + nr_irqs, nr_mapped, nr_handlers); > + set_handle_irq(plic_handle_irq); > + return 0; > + > +out_iounmap: > + iounmap(plic_regs); > + return error; > +} > + > +IRQCHIP_DECLARE(plic0, "riscv,plic0", plic_init); >