From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Matthias Brugger <matthias.bgg@gmail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vladimir Zapolskiy <vz@mleia.com>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Emil Renner Berthing <kernel@esmil.dk>,
kernel-team@android.com
Subject: Re: [PATCH 05/10] irqchip/mvebu-pic: Switch to dynamic chip name output
Date: Mon, 14 Feb 2022 15:48:24 +0100 [thread overview]
Message-ID: <87zgmtjyh3.fsf@BL-laptop> (raw)
In-Reply-To: <20220209162607.1118325-6-maz@kernel.org>
Hello Marc;
> Instead of overriding the name field, track the corresponding device
> and use the relevant callback to output its name.
>
> This allows us to make the irq_chip structure const.
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Thanks,
Gregory
> ---
> drivers/irqchip/irq-mvebu-pic.c | 28 ++++++++++++++++++----------
> 1 file changed, 18 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/irqchip/irq-mvebu-pic.c b/drivers/irqchip/irq-mvebu-pic.c
> index 870f9866b8da..ef3d3646ccc2 100644
> --- a/drivers/irqchip/irq-mvebu-pic.c
> +++ b/drivers/irqchip/irq-mvebu-pic.c
> @@ -18,6 +18,7 @@
> #include <linux/module.h>
> #include <linux/of_irq.h>
> #include <linux/platform_device.h>
> +#include <linux/seq_file.h>
>
> #define PIC_CAUSE 0x0
> #define PIC_MASK 0x4
> @@ -29,7 +30,7 @@ struct mvebu_pic {
> void __iomem *base;
> u32 parent_irq;
> struct irq_domain *domain;
> - struct irq_chip irq_chip;
> + struct platform_device *pdev;
> };
>
> static void mvebu_pic_reset(struct mvebu_pic *pic)
> @@ -66,6 +67,20 @@ static void mvebu_pic_unmask_irq(struct irq_data *d)
> writel(reg, pic->base + PIC_MASK);
> }
>
> +static void mvebu_pic_print_chip(struct irq_data *d, struct seq_file *p)
> +{
> + struct mvebu_pic *pic = irq_data_get_irq_chip_data(d);
> +
> + seq_printf(p, dev_name(&pic->pdev->dev));
> +}
> +
> +static const struct irq_chip mvebu_pic_chip = {
> + .irq_mask = mvebu_pic_mask_irq,
> + .irq_unmask = mvebu_pic_unmask_irq,
> + .irq_eoi = mvebu_pic_eoi_irq,
> + .irq_print_chip = mvebu_pic_print_chip,
> +};
> +
> static int mvebu_pic_irq_map(struct irq_domain *domain, unsigned int virq,
> irq_hw_number_t hwirq)
> {
> @@ -73,8 +88,7 @@ static int mvebu_pic_irq_map(struct irq_domain *domain, unsigned int virq,
>
> irq_set_percpu_devid(virq);
> irq_set_chip_data(virq, pic);
> - irq_set_chip_and_handler(virq, &pic->irq_chip,
> - handle_percpu_devid_irq);
> + irq_set_chip_and_handler(virq, &mvebu_pic_chip, handle_percpu_devid_irq);
> irq_set_status_flags(virq, IRQ_LEVEL);
> irq_set_probe(virq);
>
> @@ -120,22 +134,16 @@ static int mvebu_pic_probe(struct platform_device *pdev)
> {
> struct device_node *node = pdev->dev.of_node;
> struct mvebu_pic *pic;
> - struct irq_chip *irq_chip;
>
> pic = devm_kzalloc(&pdev->dev, sizeof(struct mvebu_pic), GFP_KERNEL);
> if (!pic)
> return -ENOMEM;
>
> + pic->pdev = pdev;
> pic->base = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(pic->base))
> return PTR_ERR(pic->base);
>
> - irq_chip = &pic->irq_chip;
> - irq_chip->name = dev_name(&pdev->dev);
> - irq_chip->irq_mask = mvebu_pic_mask_irq;
> - irq_chip->irq_unmask = mvebu_pic_unmask_irq;
> - irq_chip->irq_eoi = mvebu_pic_eoi_irq;
> -
> pic->parent_irq = irq_of_parse_and_map(node, 0);
> if (pic->parent_irq <= 0) {
> dev_err(&pdev->dev, "Failed to parse parent interrupt\n");
> --
> 2.30.2
>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2022-02-14 14:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 16:25 [PATCH 00/10] irqchip: Prevent drivers abusing irq_chip::name Marc Zyngier
2022-02-09 16:25 ` [PATCH 01/10] irqdomain: Let irq_domain_set_{info,hwirq_and_chip} take a const irq_chip Marc Zyngier
2022-02-15 12:20 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2022-02-09 16:25 ` [PATCH 02/10] genirq: Allow irq_chip registration functions to " Marc Zyngier
2022-02-15 12:20 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2022-02-09 16:26 ` [PATCH 03/10] irqchip/gic: Switch to dynamic chip name output Marc Zyngier
2022-02-10 23:38 ` Linus Walleij
2022-02-11 9:08 ` Marc Zyngier
2022-02-15 12:19 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2022-02-09 16:26 ` [PATCH 04/10] irqchip/lpc32xx: " Marc Zyngier
2022-02-15 12:19 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2022-02-09 16:26 ` [PATCH 05/10] irqchip/mvebu-pic: " Marc Zyngier
2022-02-14 14:48 ` Gregory CLEMENT [this message]
2022-02-15 12:19 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2022-02-09 16:26 ` [PATCH 06/10] irqchip/ts4800: " Marc Zyngier
2022-02-15 12:19 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2022-02-09 16:26 ` [PATCH 07/10] irqchip/versatile-fpga: " Marc Zyngier
2022-02-10 23:29 ` Linus Walleij
2022-02-15 12:19 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2022-02-09 16:26 ` [PATCH 08/10] gpio: mt7621: " Marc Zyngier
2022-02-09 16:26 ` [PATCH 09/10] gpio: omap: " Marc Zyngier
2022-02-09 16:26 ` [PATCH 10/10] pinctrl: starfive: " Marc Zyngier
2022-02-09 23:30 ` Emil Renner Berthing
2022-02-10 9:06 ` Marc Zyngier
2022-02-10 12:59 ` Emil Renner Berthing
2022-02-10 13:32 ` Marc Zyngier
2022-02-10 13:44 ` Emil Renner Berthing
2022-02-10 13:50 ` Marc Zyngier
2022-02-10 14:14 ` Emil Renner Berthing
2022-02-10 14:22 ` Marc Zyngier, Linus Walleij
2022-02-10 14:34 ` Marc Zyngier
2022-02-10 14:46 ` Emil Renner Berthing
2022-02-11 0:18 ` Linus Walleij
2022-02-11 0:15 ` Linus Walleij
2022-02-11 9:20 ` Marc Zyngier
2022-02-10 23:41 ` [PATCH 00/10] irqchip: Prevent drivers abusing irq_chip::name Linus Walleij
2022-02-15 12:13 ` Marc Zyngier
2022-02-15 15:37 ` Andy Shevchenko
2022-02-19 1:03 ` Linus Walleij
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=87zgmtjyh3.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=grygorii.strashko@ti.com \
--cc=kernel-team@android.com \
--cc=kernel@esmil.dk \
--cc=khilman@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=ssantosh@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=vz@mleia.com \
/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