From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Michal Simek <monstr@monstr.eu>
Cc: Michal Simek <michal.simek@xilinx.com>,
Grant Likely <grant.likely@linaro.org>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH] of: Export of_irq_count for using in modules
Date: Fri, 31 May 2013 17:16:01 +0200 [thread overview]
Message-ID: <20130531151601.GG19834@game.jcrosoft.org> (raw)
In-Reply-To: <51A8AC4B.906@monstr.eu>
On 15:57 Fri 31 May , Michal Simek wrote:
> On 05/31/2013 01:00 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 10:14 Fri 31 May , Michal Simek wrote:
> >> Hi Jean-Christophe,
> >>
> >> On 05/30/2013 10:17 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >>> On 15:49 Thu 30 May , Michal Simek wrote:
> >>>> Export of_irq_count for modules.
> >>>
> >>> can you explain why do you need to call of_irq_count
> >>
> >> I need to count number of irq written in the DTS node.
> >> It is not fixed size that's why I need to proper way how to
> >> find it out.
> >>
> >> I am using this loop.
> >> count = of_irq_count(pdev->dev.of_node);
> >> /* Alloc IRQ based on DTS to be sure that no other driver will use it */
> >> while (count--) {
> >> tmp->irq = irq_of_parse_and_map(pdev->dev.of_node, count);
> >> dev_info(&pdev->dev, "%d: Alloc irq: %d\n", count, tmp->irq);
> >> ret = request_irq(tmp->irq, zynq_remoteproc_interrupt, 0,
> >> dev_name(&pdev->dev), &pdev->dev);
> >> if (ret) {
> >> ...
> >> }
> >> }
> >>
> >> But of course if you think that this is incorrect to export it
> >> I can use what it is in of_irq_count body
> >> 368 int of_irq_count(struct device_node *dev)
> >> 369 {
> >> 370 int nr = 0;
> >> 371
> >> 372 while (of_irq_to_resource(dev, nr, NULL))
> >> 373 nr++;
> >> 374
> >> 375 return nr;
> >> 376 }
> >>
> >> Because of_irq_to_resource is exported for modules.
> >> Or is there any better way how to loop over all interrupts in DT node?
> >
> > can just explain me why you need to call irq_of_parse_and_map in your driver?
> >
> > as the irq will be provided in the resources normally
>
> It is quite a long time I have written this driver on v3.1 or 3.3.
> But is this better?
>
> struct resource *res;
> int i = 0;
> do {
> res = platform_get_resource(pdev, IORESOURCE_IRQ, i++);
> if (res)
> do something
> } while(res);
>
> Also what about of_irq_to_resource()? Is it deprecated and all drivers
> shouldn't use it?
>
> I have no problem to rewrite the driver to use platform_get_resource.
yeah it's better but be aware there is a but in DT that I'm working on to fix
if you use irq that are registered by a pdev this will not work
I hope to fix it for 3.11
and already send an RFC that fix it
Best Regards,
J.
>
> Thanks,
> Michal
>
> --
> Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
> w: www.monstr.eu p: +42-0-721842854
> Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
> Maintainer of Linux kernel - Xilinx Zynq ARM architecture
> Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
>
>
next prev parent reply other threads:[~2013-05-31 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 13:49 Michal Simek
2013-05-30 20:17 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-31 8:14 ` Michal Simek
2013-05-31 11:00 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-31 13:57 ` Michal Simek
2013-05-31 15:16 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2013-05-31 16:45 ` Michal Simek
2013-06-06 8:29 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06 8:39 ` Michal Simek
2013-06-06 11:55 ` Grant Likely
2013-06-06 13:26 ` Michal Simek
2013-06-06 14:49 ` Jean-Christophe PLAGNIOL-VILLARD
2013-07-18 7:02 ` Michal Simek
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=20130531151601.GG19834@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=rob.herring@calxeda.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome