From: Thierry Reding <thierry.reding@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.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 14:43:57 +0100 [thread overview]
Message-ID: <20141030134354.GA19802@ulmo.nvidia.com> (raw)
In-Reply-To: <2020186.tp9cWKgsNl@avalon>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Thu, Oct 30, 2014 at 03:22:49PM +0200, Laurent Pinchart wrote:
> Hi Wolfram,
>
> On Thursday 30 October 2014 14:21:36 Wolfram Sang wrote:
> > > > 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 ?
> >
> > I'd think it will look pretty similar to platform_get_irq, no? That is
> > fine with me.
>
> It would, but as Thierry pointed out it should be possible to hide the details
> in the I2C core. I'll submit a patch shortly.
i2c_device_probe() seems exactly the right place to do this. It's in
fact the equivalent of what I had proposed in my original patch series
where this was done in platform_drv_probe().
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-30 13:43 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
2014-10-30 13:21 ` Wolfram Sang
2014-10-30 13:22 ` Laurent Pinchart
2014-10-30 13:43 ` Thierry Reding [this message]
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=20141030134354.GA19802@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).