On 27/12/2018 06:13, Lokesh Vutla wrote:
> Add an optional callback .msi_unprepare to struct msi_domain_ops.
> This is used to clear any effect that is done by .msi_prepare callback.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@xxxxxx>
> ---
> include/linux/msi.h | 3 +++
> kernel/irq/msi.c | 10 ++++++++++
> 2 files changed, 13 insertions(+)
>
> diff --git a/include/linux/msi.h b/include/linux/msi.h
> index 474490826f8c..f35dd19f6c69 100644
> --- a/include/linux/msi.h
> +++ b/include/linux/msi.h
> @@ -239,6 +239,8 @@ struct msi_domain_ops {
> int (*msi_prepare)(struct irq_domain *domain,
> struct device *dev, int nvec,
> msi_alloc_info_t *arg);
> + void (*msi_unprepare)(struct irq_domain *domain, int nvec,
> + void *data);
> void (*msi_finish)(msi_alloc_info_t *arg, int retval);
> void (*set_desc)(msi_alloc_info_t *arg,
> struct msi_desc *desc);
> @@ -319,6 +321,7 @@ void platform_msi_domain_free_irqs(struct device *dev);
> /* When an MSI domain is used as an intermediate domain */
> int msi_domain_prepare_irqs(struct irq_domain *domain, struct device *dev,
> int nvec, msi_alloc_info_t *args);
> +void msi_domain_unprepare_irqs(struct irq_domain *domain, int nvec, void *data);
> int msi_domain_populate_irqs(struct irq_domain *domain, struct device *dev,
> int virq, int nvec, msi_alloc_info_t *args);
> struct irq_domain *
> diff --git a/kernel/irq/msi.c b/kernel/irq/msi.c
> index eb7459324113..1a1738690519 100644
> --- a/kernel/irq/msi.c
> +++ b/kernel/irq/msi.c
> @@ -312,6 +312,16 @@ int msi_domain_prepare_irqs(struct irq_domain *domain, struct device *dev,
> return ret;
> }
>
> +void msi_domain_unprepare_irqs(struct irq_domain *domain, int nvec,
> + void *data)
> +{
> + struct msi_domain_info *info = domain->host_data;
> + struct msi_domain_ops *ops = info->ops;
> +
> + if (ops->msi_unprepare)
> + ops->msi_unprepare(domain, nvec, data);
> +}
> +
> int msi_domain_populate_irqs(struct irq_domain *domain, struct device *dev,
> int virq, int nvec, msi_alloc_info_t *arg)
> {
>
Again, this needs justification. What does this brings to the table?
What does this callback do that cannot be done when the MSI are freed?
Also, this only makes sense if it is plugged into the MSI framework. On
its own, this is pretty useless. This makes me think that there is a gap
in the way your MSI controller driver interacts with the reset of the
MSI code.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
