Re: [patch V2 33/40] irqchip/imx-mu-msi: Switch to MSI parent

From: Thomas Gleixner
Date: Mon Nov 28 2022 - 16:03:27 EST


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