mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Andy Shevchenko <andy@black.fi.intel.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Mark Brown <broonie@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] regmap: Allow setting IRQ domain name suffix
Date: Tue, 13 Aug 2024 12:11:10 +0300	[thread overview]
Message-ID: <128893ca-121d-45c6-8b95-e8e4456c9c07@gmail.com> (raw)
In-Reply-To: <ZrpdBL7GZKmXZ60g@black.fi.intel.com>

On 8/12/24 22:05, Andy Shevchenko wrote:
> On Thu, Aug 08, 2024 at 03:36:28PM +0300, Matti Vaittinen wrote:
>> When multiple IRQ domains are created from the same device-tree node they
>> will get the same name based on the device-tree path. This will cause a
>> naming collision in debugFS when IRQ domain specific entries are created.
>>
>> The regmap-IRQ creates per instance IRQ domains. This will lead to a
>> domain name conflict when a device which provides more than one
>> interrupt line uses the regmap-IRQ.
>>
>> Add support for specifying an IRQ domain name suffix when creating a
>> regmap-IRQ controller.
> 
> ...
> 
>> +static int regmap_irq_create_domain(struct fwnode_handle *fwnode, int irq_base,
>> +				    const struct regmap_irq_chip *chip,
>> +				    struct regmap_irq_chip_data *d)
>> +{
>> +	struct irq_domain_info info = {
>> +		.fwnode = fwnode,
>> +		.size = chip->num_irqs,
>> +		.hwirq_max = chip->num_irqs,
>> +		.virq_base = irq_base,
>> +		.ops = &regmap_domain_ops,
>> +		.host_data = d,
>> +		.name_suffix = chip->domain_suffix,
>> +	};
>> +
>> +	d->domain = irq_domain_instantiate(&info);
>> +	if (IS_ERR(d->domain)) {
>> +		dev_err(d->map->dev, "Failed to create IRQ domain\n");
>> +		return PTR_ERR(d->domain);
>> +	}
>> +
>> +	return 0;
>> +}
>> +
>> +
> 
> One blank line is enough?

Sure. Thanks Andy!

Yours,
	--Matti

> 
>>   /**
> 

-- 
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~


  reply	other threads:[~2024-08-13  9:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 12:32 [PATCH v2 0/3] regmap IRQ support for devices with multiple IRQs Matti Vaittinen
2024-08-08 12:34 ` [PATCH v2 1/3] irqdomain: simplify simple and legacy domain creation Matti Vaittinen
2024-08-13 10:19   ` Jiaxun Yang
2024-08-13 10:54     ` Matti Vaittinen
2024-08-13 12:02       ` Matti Vaittinen
2024-08-13 12:14         ` Jiaxun Yang
2024-08-13 14:20         ` [tip: irq/core] irqdomain: Always associate interrupts for legacy domains tip-bot2 for Matti Vaittinen
2024-08-20 15:21         ` tip-bot2 for Matti Vaittinen
2024-08-13 12:03       ` [PATCH v2 1/3] irqdomain: simplify simple and legacy domain creation Jiaxun Yang
2024-08-08 12:35 ` [PATCH v2 2/3] irqdomain: Allow giving name suffix for domain Matti Vaittinen
2024-08-08 20:17   ` Thomas Gleixner
2024-08-08 20:19     ` [PATCH] irqdomain: Cleanup domain name allocation Thomas Gleixner
2024-08-08 20:23       ` [PATCH v2a 2/3] irqdomain: Allow giving name suffix for domain Thomas Gleixner
2024-08-09  5:03         ` Matti Vaittinen
2024-08-09 21:14         ` [tip: irq/core] " tip-bot2 for Matti Vaittinen
2024-08-09  5:19       ` [PATCH] irqdomain: Cleanup domain name allocation Matti Vaittinen
2024-08-09 21:14       ` [tip: irq/core] " tip-bot2 for Thomas Gleixner
2024-08-08 12:36 ` [PATCH v2 3/3] regmap: Allow setting IRQ domain name suffix Matti Vaittinen
2024-08-09 21:09   ` Thomas Gleixner
2024-08-12 19:05   ` Andy Shevchenko
2024-08-13  9:11     ` Matti Vaittinen [this message]
2024-08-14 12:05 ` (subset) [PATCH v2 0/3] regmap IRQ support for devices with multiple IRQs 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=128893ca-121d-45c6-8b95-e8e4456c9c07@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=andy@black.fi.intel.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®