From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 13/28] drm/i2c: tda998x: use irq for connection status and EDID read
Date: Fri, 17 Jan 2014 18:27:08 +0100 [thread overview]
Message-ID: <20140117182708.3758acb1@armhf> (raw)
In-Reply-To: <52D2EC5D.2010800@gmail.com>
On Sun, 12 Jan 2014 20:26:21 +0100
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> On 01/12/2014 07:51 PM, Jean-Francois Moine wrote:
> > On Sat, 11 Jan 2014 19:35:21 +0100
> > Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> >
> >> At least for the DT part, I'd suggest to not ask for interrupt directly
> >> but use a proper gpios property. The can of course be converted to
> >> priv->int_irq in some tda998x_dt_probe.
> >
> > May you give me more information?
>
> Sure, see [1].
>
> [1] http://lists.freedesktop.org/archives/dri-devel/2013-May/038822.html
Thanks for the link, but I still don't see the advantage of the gpio
(which value?) over the irq number.
--
Ken ar c'henta? | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: devicetree@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 13/28] drm/i2c: tda998x: use irq for connection status and EDID read
Date: Fri, 17 Jan 2014 18:27:08 +0100 [thread overview]
Message-ID: <20140117182708.3758acb1@armhf> (raw)
In-Reply-To: <52D2EC5D.2010800@gmail.com>
On Sun, 12 Jan 2014 20:26:21 +0100
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> On 01/12/2014 07:51 PM, Jean-Francois Moine wrote:
> > On Sat, 11 Jan 2014 19:35:21 +0100
> > Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> >
> >> At least for the DT part, I'd suggest to not ask for interrupt directly
> >> but use a proper gpios property. The can of course be converted to
> >> priv->int_irq in some tda998x_dt_probe.
> >
> > May you give me more information?
>
> Sure, see [1].
>
> [1] http://lists.freedesktop.org/archives/dri-devel/2013-May/038822.html
Thanks for the link, but I still don't see the advantage of the gpio
(which value?) over the irq number.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
Rob Clark <robdclark@gmail.com>, Dave Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 13/28] drm/i2c: tda998x: use irq for connection status and EDID read
Date: Fri, 17 Jan 2014 18:27:08 +0100 [thread overview]
Message-ID: <20140117182708.3758acb1@armhf> (raw)
In-Reply-To: <52D2EC5D.2010800@gmail.com>
On Sun, 12 Jan 2014 20:26:21 +0100
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> On 01/12/2014 07:51 PM, Jean-Francois Moine wrote:
> > On Sat, 11 Jan 2014 19:35:21 +0100
> > Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> >
> >> At least for the DT part, I'd suggest to not ask for interrupt directly
> >> but use a proper gpios property. The can of course be converted to
> >> priv->int_irq in some tda998x_dt_probe.
> >
> > May you give me more information?
>
> Sure, see [1].
>
> [1] http://lists.freedesktop.org/archives/dri-devel/2013-May/038822.html
Thanks for the link, but I still don't see the advantage of the gpio
(which value?) over the irq number.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2014-01-17 17:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 11:04 [PATCH v2 13/28] drm/i2c: tda998x: use irq for connection status and EDID read Jean-Francois Moine
2014-01-09 11:04 ` Jean-Francois Moine
2014-01-09 11:04 ` Jean-Francois Moine
2014-01-11 18:14 ` Russell King - ARM Linux
2014-01-11 18:14 ` Russell King - ARM Linux
2014-01-11 18:14 ` Russell King - ARM Linux
2014-01-11 18:35 ` Sebastian Hesselbarth
2014-01-11 18:35 ` Sebastian Hesselbarth
2014-01-11 18:35 ` Sebastian Hesselbarth
2014-01-12 18:51 ` Jean-Francois Moine
2014-01-12 18:51 ` Jean-Francois Moine
2014-01-12 18:51 ` Jean-Francois Moine
2014-01-12 19:26 ` Sebastian Hesselbarth
2014-01-12 19:26 ` Sebastian Hesselbarth
2014-01-12 19:26 ` Sebastian Hesselbarth
2014-01-17 17:27 ` Jean-Francois Moine [this message]
2014-01-17 17:27 ` Jean-Francois Moine
2014-01-17 17:27 ` Jean-Francois Moine
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=20140117182708.3758acb1@armhf \
--to=moinejf@free.fr \
--cc=linux-arm-kernel@lists.infradead.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.