All of lore.kernel.org
 help / color / mirror / Atom feed
From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: Clock problems in i.MX27 Visstrim M10 (linux-3.5-rc5).
Date: Wed, 4 Jul 2012 08:41:08 -0300	[thread overview]
Message-ID: <CAOMZO5CLV6TuQUTzYUSvoi6apNUtSLhkbh8Jj3onAnc99TWxWg@mail.gmail.com> (raw)
In-Reply-To: <CACKLOr1OYmoWXCU=Q_0O1H5jYcAGXO11ji6d_j7SjyaLZuygAA@mail.gmail.com>

On Wed, Jul 4, 2012 at 8:30 AM, javier Martin
<javier.martin@vista-silicon.com> wrote:

> mx2_emmaprp.c is a different driver for the same device. Its a mem2mem
> driver that gets frames from memory in one video format and then
> outputs frames in another video format. It hasn't got anything to do
> with the mx2_camera.c apart from the fact they can't be used at the
> same time since they share emma resources.

Ok, understood.

So the original mx2_camera patch i sent you plus the clk-imx27.c
changes (calling clk_register_clkdev again with the
second name) fixes the issue for you?

If so, then maybe I can send the original mx2_camera patch to the
linux-media list.

Please confirm.

I will be able to test it later today.

Regards,

Fabio Estevam

  reply	other threads:[~2012-07-04 11:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 11:09 Clock problems in i.MX27 Visstrim M10 (linux-3.5-rc5) javier Martin
2012-07-03 11:18 ` javier Martin
2012-07-03 13:13 ` Fabio Estevam
2012-07-03 17:56   ` Fabio Estevam
2012-07-04  7:48   ` javier Martin
2012-07-04  8:30     ` javier Martin
2012-07-04  8:35       ` Sascha Hauer
2012-07-04  8:49         ` javier Martin
2012-07-04 11:26     ` Fabio Estevam
2012-07-04 11:30       ` javier Martin
2012-07-04 11:41         ` Fabio Estevam [this message]
2012-07-04 18:23           ` Fabio Estevam
2012-07-04 19:55             ` Fabio Estevam
2012-07-06  6:44               ` javier Martin
2012-07-06 12:32                 ` Fabio Estevam
2012-07-09  7:00                   ` javier Martin
2012-07-04  7:11 ` Sascha Hauer

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=CAOMZO5CLV6TuQUTzYUSvoi6apNUtSLhkbh8Jj3onAnc99TWxWg@mail.gmail.com \
    --to=festevam@gmail.com \
    --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.