All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
	Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Mark Brown <broonie@kernel.org>, Lee Jones <lee@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 07/10] irqdomain: Allow giving name suffix for domain
Date: Mon, 03 Jun 2024 12:20:42 +0200	[thread overview]
Message-ID: <87h6ea72f9.ffs@tglx> (raw)
In-Reply-To: <2ea1749587d9e5a74a80a8eee7caf58c3e954a6e.1716533790.git.mazziesaccount@gmail.com>

On Fri, May 24 2024 at 11:18, Matti Vaittinen wrote:
> When multiple IRQ domains are created from same device-tree node they

s/IRQ/interrupt/

Also most of your sentences lack a substantial amount of articles.

> will get same name based on the device-tree path. This will cause a
> naming collision in debugFS when IRQ domain specific entries are
> created.
>
> One use-case for being able to create multiple IRQ domains / single
> device node is using regmap-IRQ controller code for devices which
> provide more than one physical IRQ.

This does not make sense. Why do you need multiple interrupt domains if
there is more than one physical interrupt?

> It seems much cleaner to instantiate

'It seems' is not a technical argument.

> own regmap-IRQ controller for each parent IRQ because most of the regmap
> IRQ properties are really specific to parent IRQ.

Now you start talking about parent interrupts. Can you please make your
mind up and concisely explain what this is about?

> -struct irq_domain *irq_domain_create_legacy(struct fwnode_handle *fwnode,
> +struct irq_domain *irq_domain_create_legacy_named(struct fwnode_handle *fwnode,
>  					 unsigned int size,
>  					 unsigned int first_irq,
>  					 irq_hw_number_t first_hwirq,
>  					 const struct irq_domain_ops *ops,
> -					 void *host_data)
> +					 void *host_data, const char *name_suffix)
>  {
>  	struct irq_domain *domain;
>  
> -	domain = __irq_domain_add(fwnode, first_hwirq + size, first_hwirq + size, 0, ops, host_data);
> +	domain = __irq_domain_add(fwnode, first_hwirq + size, first_hwirq + size,
> +				  0, ops, host_data, name_suffix);
>  	if (domain)
>  		irq_domain_associate_many(domain, first_irq, first_hwirq, size);
>  
>  	return domain;
>  }
> +EXPORT_SYMBOL_GPL(irq_domain_create_legacy_named);

What for? This new stuff is not going to be used for legacy setups with
hard coded Linux interrupt numbers. So there is no point to add a
function plus an export which is never used.

Thanks,

        tglx

  reply	other threads:[~2024-06-03 10:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  8:15 [PATCH v2 00/10] Support ROHM BD96801 Scalable PMIC Matti Vaittinen
2024-05-24  8:16 ` [PATCH v2 01/10] dt-bindings: ROHM BD96801 PMIC regulators Matti Vaittinen
2024-05-25 18:39   ` Krzysztof Kozlowski
2024-05-24  8:17 ` [PATCH v2 02/10] dt-bindings: mfd: bd96801 PMIC core Matti Vaittinen
2024-05-25 18:58   ` Krzysztof Kozlowski
2024-05-24  8:17 ` [PATCH v2 03/10] mfd: support ROHM BD96801 " Matti Vaittinen
2024-05-24  8:17 ` [PATCH v2 04/10] regulator: bd96801: ROHM BD96801 PMIC regulators Matti Vaittinen
2024-05-30 12:55   ` Mark Brown
2024-05-24  8:18 ` [PATCH v2 05/10] watchdog: ROHM BD96801 PMIC WDG driver Matti Vaittinen
2024-05-24  8:18 ` [PATCH v2 06/10] MAINTAINERS: Add ROHM BD96801 'scalable PMIC' entries Matti Vaittinen
2024-05-24  8:18 ` [PATCH v2 07/10] irqdomain: Allow giving name suffix for domain Matti Vaittinen
2024-06-03 10:20   ` Thomas Gleixner [this message]
2024-06-03 12:19     ` Matti Vaittinen
2024-06-03 13:40       ` Matti Vaittinen
2024-06-03 16:38       ` Thomas Gleixner
2024-06-03 17:38         ` Matti Vaittinen
2024-06-03 21:03           ` Thomas Gleixner
2024-05-24  8:19 ` [PATCH v2 08/10] regmap: Allow setting IRQ domain name suffix Matti Vaittinen
2024-05-24  8:19 ` [PATCH v2 09/10] mfd: bd96801: Add ERRB IRQ Matti Vaittinen
2024-05-24  8:19 ` [PATCH v2 10/10] regulator: " Matti Vaittinen
2024-05-30 12:56   ` Mark Brown

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=87h6ea72f9.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=broonie@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.