From: Manjunatha GK <manjugk-l0cyMroinI0@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org\""
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: Converting i2c-omap driver to use device tree
Date: Wed, 29 Jun 2011 10:23:25 +0530 [thread overview]
Message-ID: <BANLkTimDM6XYf3X=eRhZUDUij1TkhQGBnQ@mail.gmail.com> (raw)
In-Reply-To: <20110628193854.GA26182-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1300 bytes --]
On 29 June 2011 01:08, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
[...]
> > >
> > > Any specific reason for missing entries in device node structures?
> > >
> > > Since you explored other ARM boards, is this interrupts field used and
> > > tested?
>
> What tree do you have your work based on top of?
git://git.secretlab.ca/git/linux-2.6.git
branch: devicetree/test
Do you have the irq_domain patch applied?
If so, then the problem is most likely that an
> irq_domain has not been registered for the OMAP interrupt controller
> (which is not surprising since the gic has not been converted to use
> irq_domain yet). There are patches that have been posted to the list
> to do so, but they are not finished yet.
ok.
> In the mean time you can use
> irq_domain_generate_simple() to create an irq_domain registration for
> the OMAP that will get you past this step.
>
> Search the devicetree/test branch for irq_domain_generate_simple() to
> see how to use it.
>
> I realized this hence used
node = of_find_matching_node_by_address(NULL, omap_dt_gic_match,
OMAP44XX_GIC_DIST_BASE);
if (node)
irq_domain_add_simple(node, 0);
which resolved the irq issue.
Thanks for the info.
-Manjunath
[-- Attachment #1.2: Type: text/html, Size: 2284 bytes --]
[-- Attachment #2: Type: text/plain, Size: 192 bytes --]
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
prev parent reply other threads:[~2011-06-29 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 14:15 Converting i2c-omap driver to use device tree Manjunatha GK
[not found] ` <BANLkTin0zaE6M=0+9bq6sCvCVO_PJqYseA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-24 12:16 ` Manjunatha GK
[not found] ` <BANLkTi=DmNC6BbwDU+4smFvbc+LzFLiiOA@mail.gmail.com>
[not found] ` <BANLkTi=DmNC6BbwDU+4smFvbc+LzFLiiOA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-24 13:38 ` Manjunatha GK
[not found] ` <BANLkTi==YKS854=YDGG44BRy_km31LqifQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-26 8:12 ` Grant Likely
[not found] ` <20110626081202.GB24241-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-06-26 18:51 ` Manjunatha GK
[not found] ` <BANLkTimJU1ecxAroZMdWDdcAg6icH1mXyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-28 14:18 ` Manjunatha GK
[not found] ` <BANLkTinNVzgGhEXSfQf+WpSMtoUDN-5Jag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-28 19:38 ` Grant Likely
[not found] ` <20110628193854.GA26182-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-06-29 4:53 ` Manjunatha GK [this message]
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='BANLkTimDM6XYf3X=eRhZUDUij1TkhQGBnQ@mail.gmail.com' \
--to=manjugk-l0cymroini0@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@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).