[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f56780af-b2d4-42d7-bc5d-c35b295d7c52@lunn.ch>
Date: Thu, 3 Oct 2024 01:52:20 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: Oleksij Rempel <o.rempel@...gutronix.de>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Jonathan Corbet <corbet@....net>,
Donald Hunter <donald.hunter@...il.com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-doc@...r.kernel.org, Kyle Swenson <kyle.swenson@....tech>,
Dent Project <dentproject@...uxfoundation.org>,
kernel@...gutronix.de
Subject: Re: [PATCH net-next 11/12] net: pse-pd: Add support for event
reporting using devm_regulator_irq_helper
> +int devm_pse_irq_helper(struct pse_controller_dev *pcdev, int irq,
> + int irq_flags, int supported_errs,
> + const struct pse_irq_desc *d)
> +{
> + struct regulator_dev **rdevs;
> + void *irq_helper;
> + int i;
> +
> + rdevs = devm_kcalloc(pcdev->dev, pcdev->nr_lines,
> + sizeof(struct regulator_dev *), GFP_KERNEL);
> + if (!rdevs)
> + return -ENOMEM;
> +
> + for (i = 0; i < pcdev->nr_lines; i++)
> + rdevs[i] = pcdev->pi[i].rdev;
> +
> + /* Register notifiers - can fail if IRQ is not given */
> + irq_helper = devm_regulator_irq_helper(pcdev->dev, d, irq,
> + 0, supported_errs, NULL,
> + &rdevs[0], pcdev->nr_lines);
Should irq_flags be passed through? I'm guessing one usage of it will
be IRQF_SHARED when there is one interrupt shared by a number of
controllers.
Andrew
Powered by blists - more mailing lists