All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	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:21:36 +0100	[thread overview]
Message-ID: <20141030132136.GA23852@katana> (raw)
In-Reply-To: <1441244.9DO8HMds24@avalon>

[-- Attachment #1: Type: text/plain, Size: 365 bytes --]


> > 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.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-10-30 13:21 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
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 [this message]
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=20141030132136.GA23852@katana \
    --to=wsa@the-dreams.de \
    --cc=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 \
    /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.