From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Laurent Pinchart
<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: I2C OF IRQ parsing issue due to probe ordering
Date: Mon, 27 Oct 2014 13:58:19 +0100 [thread overview]
Message-ID: <20141027125819.GA12641@katana> (raw)
In-Reply-To: <2287003.09eTeKUr1V@avalon>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
> 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.
Regards,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: 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: Mon, 27 Oct 2014 13:58:19 +0100 [thread overview]
Message-ID: <20141027125819.GA12641@katana> (raw)
In-Reply-To: <2287003.09eTeKUr1V@avalon>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
> 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.
Regards,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-27 12:58 UTC|newest]
Thread overview: 15+ 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 [this message]
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
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
2014-10-30 11:58 ` Ezequiel Garcia
[not found] ` <545227E4.5070507-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-10-30 12:15 ` Laurent Pinchart
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=20141027125819.GA12641@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.