From: Thomas Gleixner <tglx@linutronix.de>
To: Frank Li <Frank.Li@nxp.com>
Cc: agross@kernel.org, ammarfaizi2@gnuweeb.org, andersson@kernel.org,
andrew@lunn.ch, bhelgaas@google.com, festevam@gmail.com,
gregkh@linuxfoundation.org, gregory.clement@bootlin.com,
jgg@mellanox.com, kristo@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
lorenzo.pieralisi@arm.com, lpieralisi@kernel.org,
mark.rutland@arm.com, maz@kernel.org, nm@ti.com,
okaya@kernel.org, robin.murphy@arm.com, s.hauer@pengutronix.de,
sebastian.hesselbarth@gmail.com,
shameerali.kolothum.thodi@huawei.com, shawnguo@kernel.org,
ssantosh@kernel.org, vkoul@kernel.org, will@kernel.org,
yuzenghui@huawei.com, imx@lists.linux.dev
Subject: Re: [patch V2 33/40] irqchip/imx-mu-msi: Switch to MSI parent
Date: Mon, 28 Nov 2022 22:03:20 +0100 [thread overview]
Message-ID: <87tu2ivlk7.ffs@tglx> (raw)
In-Reply-To: <20221128204710.2084706-1-Frank.Li@nxp.com>
Frank!
On Mon, Nov 28 2022 at 15:47, Frank Li wrote:
> On Mon, Nov 21, 2022 at 03:40:09PM +0100, Thomas Gleixner wrote:
>> * The device MSI domain can never have a set affinity callback it
>> --- a/drivers/irqchip/irq-imx-mu-msi.c
>> +++ b/drivers/irqchip/irq-imx-mu-msi.c
>> @@ -24,6 +24,8 @@
>> #include <linux/pm_domain.h>
>> #include <linux/spinlock.h>
>>
>> +#include "irq-gic-msi-lib.h"
>> +
>
> I think irq-gic-msi-lib.h is not good name. Actually mu-msi is not arm gic.
> irq-gic-msi-lib do common work, which not related arm gic at all.
I realized that after a while too, but the main purpose of this series
was to establish that the core design holds up to handle the gazillions
of ARM variants out there and to solicit technical feedback from the
involved parties.
>> static int imx_mu_msi_domains_init(struct imx_mu_msi *msi_data, struct device *dev)
>> {
>> struct fwnode_handle *fwnodes = dev_fwnode(dev);
>> struct irq_domain *parent;
>>
>> /* Initialize MSI domain parent */
>> - parent = irq_domain_create_linear(fwnodes,
>> - IMX_MU_CHANS,
>> - &imx_mu_msi_domain_ops,
>> - msi_data);
>> + parent = irq_domain_create_linear(fwnodes, IMX_MU_CHANS, &imx_mu_msi_domain_ops, msi_data);
>
> coding style change should be in sperated patch.
Thanks for the thorough technical feedback!
tglx
prev parent reply other threads:[~2022-11-28 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221121140050.386216606@linutronix.de>
2022-11-28 20:47 ` [patch V2 33/40] irqchip/imx-mu-msi: Switch to MSI parent Frank Li
2022-11-28 21:03 ` Thomas Gleixner [this message]
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=87tu2ivlk7.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Frank.Li@nxp.com \
--cc=agross@kernel.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=imx@lists.linux.dev \
--cc=jgg@mellanox.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=nm@ti.com \
--cc=okaya@kernel.org \
--cc=robin.murphy@arm.com \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shawnguo@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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