From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: I2C OF IRQ parsing issue due to probe ordering
Date: Thu, 30 Oct 2014 15:05:18 +0200 [thread overview]
Message-ID: <1441244.9DO8HMds24@avalon> (raw)
In-Reply-To: <20141030125645.GA19386@ulmo>
Hi Thierry,
On Thursday 30 October 2014 13:56:46 Thierry Reding wrote:
> On Mon, Oct 27, 2014 at 01:58:19PM +0100, Wolfram Sang wrote:
> > > The i2c@e6520000 node is probed before the gpio@e6051000 node. The
> > > of_i2c_register_devices() function tries to register all children,
> > > including hdmi@39. It tries to parse and map the I2C client IRQ by
> > > calling irq_of_parse_and_map(), which returns 0 as the interrupt
> > > controller isn't probed yet. The adv7511 driver later probes the hdmi@39
> > > device and gets client->irq set to 0.
> >
> > I've got this strange feeling of deja vu... Ah, here: Thierry Reding
> > tackled this problem a year ago. His series:
> >
> > https://lkml.org/lkml/2013/9/16/111 (of/irq: Defer interrupt reference
> > resolution)
> >
> > He did a V2 (which never made it to the i2c list). Seems like the first
> > two patches made it and the rest got stalled without discussion?
> >
> > https://lkml.org/lkml/2013/9/18/216
> >
> > Adding Thierry to the queue. Maybe he can bring some light to what
> > happened to his series.
>
> I tried to fix it in a proper way, but it seems people were uneasy with
> how invasive the change was.
It was a bit invasive indeed and I can share the uneasiness, but on the other
hand there was no real nack. I think I still prefer your approach, but can
live with something simpler.
> At some point I lost interest. People ended up merging something that was
> similar, but side-stepped the issue of propagating error codes all the way
> up by introducing a new API and in case of of_irq_parse_one() failing doing
> an additional check to see if the reason was the missing IRQ domain.
>
> See:
>
> 9ec36cafe43b of/irq: do irq resolution in platform_get_irq
>
> I suspect a similar thing could be done for I2C.
That could work. We would need to introduce a new i2c_get_irq() function
though. Wolfram, would you be fine with that ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-10-30 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 22:13 I2C OF IRQ parsing issue due to probe ordering Laurent Pinchart
2014-10-27 12:58 ` Wolfram Sang
2014-10-30 12:53 ` Laurent Pinchart
2014-10-30 13:02 ` Thierry Reding
2014-10-30 13:12 ` Laurent Pinchart
2014-10-30 12:56 ` Thierry Reding
2014-10-30 13:05 ` Laurent Pinchart [this message]
2014-10-30 13:21 ` Wolfram Sang
2014-10-30 13:22 ` Laurent Pinchart
2014-10-30 13:43 ` Thierry Reding
2014-10-30 11:58 ` Ezequiel Garcia
[not found] ` <545227E4.5070507-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-10-30 12:15 ` Laurent Pinchart
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=1441244.9DO8HMds24@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=wsa@the-dreams.de \
/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).