From: Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] mfd: cottula: add cottula board
Date: Mon, 15 Dec 2014 16:45:03 +0100 [thread overview]
Message-ID: <877fxsapds.fsf@free.fr> (raw)
In-Reply-To: <4307800.p21Sk5E3dV@wuerfel> (Arnd Bergmann's message of "Mon, 15 Dec 2014 11:46:20 +0100")
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org> writes:
> On Monday 15 December 2014 00:10:06 Robert Jarzmik wrote:
>> +
>> + platform_set_drvdata(pdev, cot);
>> + cot->gpio0 = gpiod_get(&pdev->dev, "lubbock_irq", 0);
>> + if (IS_ERR(cot->gpio0)) {
>> + dev_err(&pdev->dev, "Couldn't request GPIO : ret = %d\n", ret);
>> + return PTR_ERR(cot->gpio0);
>> + }
>> + cot->irq = gpiod_to_irq(cot->gpio0);
>> + if (cot->irq < 0)
>> + return cot->irq;
>> +
>> + cot->irqdomain =
>> + irq_domain_add_linear(pdev->dev.of_node, COTTULA_NB_IRQ,
>> + &cottula_irq_domain_ops, cot);
>> + if (!cot->irqdomain)
>> + return -ENODEV;
>> +
>> + ret = 0;
>> + if (base_irq)
>> + ret = irq_create_strict_mappings(cot->irqdomain, base_irq, 0,
>> + COTTULA_NB_IRQ);
>>
>
> This looks a bit ambiguous: You get a GPIO line for the purpose of the
> IRQ nesting but don't use the GPIO otherwise, and you pass the device's
> own irq domain start as an IORESOURCE_IRQ resource.
>
> For consistency between DT and ATAGS based uses, and with similar DT
> based drivers, I would instead recommend passing the parent irq (from
> the GPIO) as an IORESOURCE_IRQ resource instead of a gpio lookup,
> and passing the base_irq as platform_data for the ATAGS case.
I understand Arnd, yet I wanted to avoid any platform data if possible, as this
is a motherboard, it will not be plugged anywhere else with different
parameters.
What would you say if I did this :
- remove the gpio
- use IORESOURCE_IRQ(0) as the parent irq (as you suggested)
- use IORESOURCE_IRQ(1) as the base_irq
=> this resource would be optional
- if exists, use it as base_irq
- if doesn't exist, let base_irq = 0
Will that look correct ?
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-15 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 23:10 [PATCH] mfd: cottula: add cottula board Robert Jarzmik
2014-12-15 10:46 ` Arnd Bergmann
2014-12-15 15:45 ` Robert Jarzmik [this message]
2014-12-15 16:01 ` Arnd Bergmann
2014-12-15 16:27 ` Robert Jarzmik
[not found] ` <877fxsapds.fsf-GANU6spQydw@public.gmane.org>
2014-12-20 9:43 ` Robert Jarzmik
2014-12-20 20:11 ` Arnd Bergmann
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=877fxsapds.fsf@free.fr \
--to=robert.jarzmik-ganu6spqydw@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).