linux-kernel - Re: [PATCH v3 6/9] pinctrl: Add IRQ support to STM32 gpios

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <670d8249-0f72-50d1-5c1f-07fe53ac524b@st.com>
Date:   Mon, 5 Sep 2016 01:53:40 -0600
From:   Alexandre Torgue <alexandre.torgue@...com>
To:     Thomas Gleixner <tglx@...utronix.de>
CC:     Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Jason Cooper <jason@...edaemon.net>,
        Marc Zyngier <marc.zyngier@....com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Mark Rutland <mark.rutland@....com>,
        Rob Herring <robh+dt@...nel.org>, <linux-gpio@...r.kernel.org>,
        <arnd@...db.de>, <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        Daniel Thompson <daniel.thompson@...aro.org>,
        <bruherrera@...il.com>, <lee.jones@...aro.org>
Subject: Re: [PATCH v3 6/9] pinctrl: Add IRQ support to STM32 gpios

Hi Thomas,

On 09/02/2016 09:10 PM, Thomas Gleixner wrote:
> On Fri, 2 Sep 2016, Alexandre TORGUE wrote:
>> +static int stm32_gpio_domain_translate(struct irq_domain *d,
>> +				       struct irq_fwspec *fwspec,
>> +				       unsigned long *hwirq,
>> +				       unsigned int *type)
>> +{
>> +	if ((fwspec->param_count != 2) ||
>> +		(fwspec->param[0] >= STM32_GPIO_IRQ_LINE))
>> +		return -EINVAL;
>
> Just a nitpick. This is unnecessarily hard to parse because you indented
> the line break like a conditional statement

I agree. I will modify it as the one below.
>
>> +	if ((fwspec->param_count != 2) ||
>> +	    (fwspec->param[0] >= STM32_GPIO_IRQ_LINE))
>> +		return -EINVAL;
>
> Makes it immediately obvious that the second line belongs to the if.
>
>> +static void stm32_gpio_domain_activate(struct irq_domain *d,
>> +				       struct irq_data *irq_data)
>> +{
>> +	struct stm32_gpio_bank *bank = d->host_data;
>> +	struct stm32_pinctrl *pctl = dev_get_drvdata(bank->gpio_chip.parent);
>> +
>> +	if (gpiochip_lock_as_irq(&bank->gpio_chip, irq_data->hwirq)) {
>> +		dev_err(pctl->dev,
>> +			"Unable to configure STM32 %s%ld as IRQ\n",
>> +			bank->gpio_chip.label, irq_data->hwirq);
>> +		return;
>
> Hmm, that's nasty. When an interrupt is mapped then we don't expect the
> activate function to fail. You really should lock that interrupt when it's
> mapped.

Ok. I will remove it from here.

>
>> +	}
>> +	regmap_field_write(pctl->irqmux[irq_data->hwirq], bank->range.id);
>> +}
>
>> +static int stm32_gpio_domain_alloc(struct irq_domain *domain,
>> +				   unsigned int virq,
>> +				   unsigned int nr_irqs, void *data)
>> +{
>> +	struct irq_fwspec *fwspec = data;
>> +	struct irq_fwspec parent_fwspec;
>> +	struct stm32_pinctrl *pctl = domain->host_data;
>> +	irq_hw_number_t hwirq;
>> +	unsigned int i;
>> +
>> +	hwirq = fwspec->param[0];
>> +	for (i = 0; i < nr_irqs; i++)
>> +		irq_domain_set_hwirq_and_chip(domain, virq + i, hwirq + i,
>> +					      &stm32_gpio_irq_chip, pctl);
>> +
>> +	parent_fwspec.fwnode = domain->parent->fwnode;
>> +	parent_fwspec.param_count = 2;
>> +	parent_fwspec.param[0] = fwspec->param[0];
>> +	parent_fwspec.param[1] = fwspec->param[1];
>> +
>> +	return irq_domain_alloc_irqs_parent(domain, virq, nr_irqs,
>> +			&parent_fwspec);
>
> So doing it here would be probably the right thing to do:
>
>
> 	ret = gpiochip_lock_as_irq();
> 	if (ret)
> 		return ret;
>
>    	ret = irq_domain_alloc_irqs_parent(domain, virq, nr_irqs,
> 	      				   &parent_fwspec);
> 	if (ret)
> 		gpiochip_unlock_as_irq();
>
> 	return ret;
>
> So of course you need your own free() function which undoes that lock
> thingy.

Ok thanks for proposal.

Best regards.

Alex


>
> Thanks,
>
> 	tglx
>

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html