public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	liu.y.victor@gmail.com, Sascha Hauer <s.hauer@pengutronix.de>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, B02280@freescale.com
Subject: Re: [PATCH 3/9] Add a mfd IPUv3 driver
Date: Tue, 01 Feb 2011 13:07:35 +0100	[thread overview]
Message-ID: <87wrlkyn3s.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <20110201115125.GE31216@n2100.arm.linux.org.uk> (Russell King's message of "Tue, 1 Feb 2011 11:51:25 +0000")

Hi,

Russell King - ARM Linux <linux@arm.linux.org.uk> writes:

> On Tue, Feb 01, 2011 at 12:44:54PM +0100, Samuel Ortiz wrote:
>> Ok, so would moving it do drivers/video/ make sense ?
>
> Isn't that for framebuffer drivers?

For now, the ipu driver is used for framebuffer on imx5.

Arnaud

  reply	other threads:[~2011-02-01 12:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 10:48 [PATCH v2] i.MX51 Framebuffer support Sascha Hauer
2010-12-20 10:48 ` [PATCH 1/9] ARM i.MX51: Add ipu clock support Sascha Hauer
2010-12-20 10:48 ` [PATCH 2/9] ARM i.MX51: rename IPU irqs Sascha Hauer
2010-12-20 10:48 ` [PATCH 3/9] Add a mfd IPUv3 driver Sascha Hauer
2011-01-03 15:42   ` Sascha Hauer
2011-01-07 12:08     ` Samuel Ortiz
2011-01-31  8:20       ` Sascha Hauer
2011-02-01 10:51   ` Samuel Ortiz
2011-02-01 10:59     ` Sascha Hauer
2011-02-01 11:44       ` Samuel Ortiz
2011-02-01 11:51         ` Russell King - ARM Linux
2011-02-01 12:07           ` Arnaud Patard [this message]
2011-02-01 12:51             ` Sascha Hauer
2011-02-01 16:47               ` Uwe Kleine-König
2011-02-01 14:03           ` Samuel Ortiz
2010-12-20 10:48 ` [PATCH 4/9] fb: export fb mode db table Sascha Hauer
2010-12-20 10:48 ` [PATCH 5/9] Add i.MX5 framebuffer driver Sascha Hauer
2010-12-20 10:48 ` [PATCH 6/9] ARM i.MX51: Add IPU device support Sascha Hauer
2010-12-20 10:48 ` [PATCH 7/9] ARM i.MX5: Allow to increase max zone order Sascha Hauer
2010-12-20 10:48 ` [PATCH 8/9] ARM i.MX5: increase dma consistent size for IPU support Sascha Hauer
2010-12-20 10:48 ` [PATCH 9/9] ARM i.MX51 babbage: Add framebuffer support Sascha Hauer
2010-12-20 12:35   ` arden jay
2010-12-22  7:56 ` [PATCH v2] i.MX51 Framebuffer support Arnaud Patard
2010-12-22 10:17   ` Peter Korsgaard
2010-12-23 20:45     ` Arnaud Patard
2011-01-05 13:04 ` Julien Boibessot
2011-01-06  9:42   ` Russell King - ARM Linux
2011-01-14  9:17     ` Julien Boibessot
2011-01-06 10:23   ` Sascha Hauer
     [not found] <33F32152BE7EC740BC2C838D2836AC8704A4FD@039-SN1MPN1-002.039d.mgd.msft.net>
2010-12-14 12:02 ` [PATCH 3/9] Add a mfd IPUv3 driver Chen Jie-B02280
  -- strict thread matches above, loose matches on Subject: below --
2010-12-09 13:47 [PATCH RFC] i.MX51 Framebuffer support Sascha Hauer
2010-12-09 13:47 ` [PATCH 3/9] Add a mfd IPUv3 driver Sascha Hauer
2010-12-12  5:21   ` Liu Ying
2010-12-13 11:23     ` Sascha Hauer
2010-12-14  4:05       ` Liu Ying
2010-12-14  8:40         ` Sascha Hauer
2010-12-14 13:13           ` Liu Ying

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=87wrlkyn3s.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=B02280@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=liu.y.victor@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sameo@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox