From: Marc Zyngier <maz@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Heiko Stuebner" <heiko@sntech.de>,
linux-rockchip@lists.infradead.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/4] PCI: dwc: rockchip: add legacy interrupt support
Date: Sat, 16 Apr 2022 13:54:49 +0100 [thread overview]
Message-ID: <308e9c47197d4f7ae5a31cfcb5a10886@kernel.org> (raw)
In-Reply-To: <20220416110507.642398-3-pgwipeout@gmail.com>
Peter,
May I suggest that you slow down on the number of versions you send?
This is the 7th in 5 days, the 3rd today.
At this stage, this is entirely counterproductive.
On 2022-04-16 12:05, Peter Geis wrote:
> The legacy interrupts on the rk356x pcie controller are handled by a
> single muxed interrupt. Add irq domain support to the pcie-dw-rockchip
> driver to support the virtual domain.
>
> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> ---
> drivers/pci/controller/dwc/pcie-dw-rockchip.c | 112 +++++++++++++++++-
> 1 file changed, 110 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> index c9b341e55cbb..863374604fb1 100644
> --- a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> +++ b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> @@ -10,9 +10,12 @@
>
> #include <linux/clk.h>
> #include <linux/gpio/consumer.h>
> +#include <linux/irqchip/chained_irq.h>
> +#include <linux/irqdomain.h>
> #include <linux/mfd/syscon.h>
> #include <linux/module.h>
> #include <linux/of_device.h>
> +#include <linux/of_irq.h>
> #include <linux/phy/phy.h>
> #include <linux/platform_device.h>
> #include <linux/regmap.h>
> @@ -36,10 +39,13 @@
> #define PCIE_LINKUP (PCIE_SMLH_LINKUP | PCIE_RDLH_LINKUP)
> #define PCIE_L0S_ENTRY 0x11
> #define PCIE_CLIENT_GENERAL_CONTROL 0x0
> +#define PCIE_CLIENT_INTR_STATUS_LEGACY 0x8
> +#define PCIE_CLIENT_INTR_MASK_LEGACY 0x1c
> #define PCIE_CLIENT_GENERAL_DEBUG 0x104
> -#define PCIE_CLIENT_HOT_RESET_CTRL 0x180
> +#define PCIE_CLIENT_HOT_RESET_CTRL 0x180
> #define PCIE_CLIENT_LTSSM_STATUS 0x300
> -#define PCIE_LTSSM_ENABLE_ENHANCE BIT(4)
> +#define PCIE_LEGACY_INT_ENABLE GENMASK(3, 0)
> +#define PCIE_LTSSM_ENABLE_ENHANCE BIT(4)
> #define PCIE_LTSSM_STATUS_MASK GENMASK(5, 0)
>
> struct rockchip_pcie {
> @@ -51,6 +57,8 @@ struct rockchip_pcie {
> struct reset_control *rst;
> struct gpio_desc *rst_gpio;
> struct regulator *vpcie3v3;
> + struct irq_domain *irq_domain;
> + raw_spinlock_t irq_lock;
> };
>
> static int rockchip_pcie_readl_apb(struct rockchip_pcie *rockchip,
> @@ -65,6 +73,94 @@ static void rockchip_pcie_writel_apb(struct
> rockchip_pcie *rockchip,
> writel_relaxed(val, rockchip->apb_base + reg);
> }
>
> +static void rockchip_pcie_legacy_int_handler(struct irq_desc *desc)
> +{
> + struct irq_chip *chip = irq_desc_get_chip(desc);
> + struct rockchip_pcie *rockchip = irq_desc_get_handler_data(desc);
> + unsigned long reg, hwirq;
> +
> + chained_irq_enter(chip, desc);
> +
> + reg = rockchip_pcie_readl_apb(rockchip,
> PCIE_CLIENT_INTR_STATUS_LEGACY);
> +
> + for_each_set_bit(hwirq, ®, 8)
8? And yet:
#define PCI_NUM_INTX 4
So whatever bits are set above bit 3, you are feeding garbage
to the irqdomain code.
> + generic_handle_domain_irq(rockchip->irq_domain, hwirq);
> +
> + chained_irq_exit(chip, desc);
> +}
> +
> +static void rockchip_intx_mask(struct irq_data *data)
> +{
> + struct rockchip_pcie *rockchip = irq_data_get_irq_chip_data(data);
> + unsigned long flags;
> + u32 val;
> +
> + /* disable legacy interrupts */
> + raw_spin_lock_irqsave(&rockchip->irq_lock, flags);
> + val = HIWORD_UPDATE_BIT(PCIE_LEGACY_INT_ENABLE);
> + val |= PCIE_LEGACY_INT_ENABLE;
> + rockchip_pcie_writel_apb(rockchip, val,
> PCIE_CLIENT_INTR_MASK_LEGACY);
> + raw_spin_unlock_irqrestore(&rockchip->irq_lock, flags);
This is completely busted. INTx lines must be controlled individually.
If I disable one device's INTx output, I don't want to see the
interrupt firing because another one has had its own enabled.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2022-04-16 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 11:05 [PATCH v7 0/4] Enable rk356x PCIe controller Peter Geis
2022-04-16 11:05 ` [PATCH v7 1/4] dt-bindings: pci: remove fallback from Rockchip DesignWare binding Peter Geis
2022-04-20 16:27 ` Rob Herring
2022-04-16 11:05 ` [PATCH v7 2/4] PCI: dwc: rockchip: add legacy interrupt support Peter Geis
2022-04-16 12:54 ` Marc Zyngier [this message]
2022-04-16 13:24 ` Peter Geis
2022-04-17 9:53 ` Marc Zyngier
2022-04-18 11:37 ` Peter Geis
2022-04-18 12:34 ` Marc Zyngier
2022-04-18 15:13 ` Peter Geis
2022-04-18 22:53 ` Marc Zyngier
2022-04-19 0:23 ` Peter Geis
2022-04-19 8:05 ` Marc Zyngier
2022-04-19 20:37 ` Peter Geis
2022-04-16 11:05 ` [PATCH v7 3/4] arm64: dts: rockchip: add rk3568 pcie2x1 controller Peter Geis
2022-04-16 11:05 ` [PATCH v7 4/4] arm64: dts: rockchip: enable pcie controller on quartz64-a Peter Geis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=308e9c47197d4f7ae5a31cfcb5a10886@kernel.org \
--to=maz@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pgwipeout@gmail.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).