All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: linux-media@vger.kernel.org,
	sakari.ailus@maxwell.research.nokia.com,
	kyungmin.park@samsung.com, s.nawrocki@samsung.com,
	laurent.pinchart@ideasonboard.com, mchehab@infradead.org,
	s.hauer@pengutronix.de
Subject: Re: [PATCH v3] media: coda: Add driver for Coda video codec.
Date: Wed, 18 Jul 2012 14:12:02 +0200	[thread overview]
Message-ID: <1342613522.2542.154.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <CACKLOr0861rZbOFZ2O0eXuTY7PB1yiFkSt62_4uXvJT+QMZe9A@mail.gmail.com>

Am Mittwoch, den 18.07.2012, 11:26 +0200 schrieb javier Martin:
> On 18 July 2012 11:22, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> > Hi Javier,
> >
> > Am Mittwoch, den 18.07.2012, 11:01 +0200 schrieb javier Martin:
> >> On 18 July 2012 10:35, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> >> > Hi Javier,
> >> >
> >> > Am Mittwoch, den 18.07.2012, 09:12 +0200 schrieb javier Martin:
> >> > [...]
> >> >> > I see there is a comment about the expected register setting not working
> >> >> > for CODA_REG_BIT_STREAM_CTRL in start_streaming(). Could this be
> >> >> > related?
> >> >>
> >> >> I don't think so. This means that the following line:
> >> >>
> >> >> coda_write(dev, (3 << 3), CODA_REG_BIT_STREAM_CTRL);
> >> >>
> >> >> should be:
> >> >>
> >> >> coda_write(dev, (CODADX6_STREAM_BUF_PIC_RESET |
> >> >> CODADX6_STREAM_BUF_PIC_FLUSH), CODA_REG_BIT_STREAM_CTRL);
> >> >>
> >> >> But the latter does not work.
> >> >
> >> > Looks to me like (3 << 3) == (CODA7_STREAM_BUF_PIC_RESET |
> >> > CODA7_STREAM_BUF_PIC_FLUSH) could be the explanation.
> >>
> >> You mean "!=", don't you?
> >
> > I mean "==". coda.h contains:
> >
> > #define         CODA7_STREAM_BUF_PIC_RESET      (1 << 4)
> > #define         CODA7_STREAM_BUF_PIC_FLUSH      (1 << 3)
> >
> > So maybe those are the correct bits for i.MX27 with the 2.2.5 firmware.
> > If that is the case, you could do s/CODA7_STREAM_BUF_/CODA_STREAM_BUF_/
> > and drop the incorrect CODADX6_STREAM_BUF_ defines.
> 
> Sorry, I didn't catch the 'CODA7' prefix in your defines.
> OK then, I'll do  s/CODA7_STREAM_BUF_/CODA_STREAM_BUF_/ and remove the
> comment too.

Hold on, I just read that there should be a ENC_DYN_BUFALLOC_EN bit
((1 << 5) on i.MX53, (1 << 4) on i.MX27) - so maybe the #defines are
right after all, just that bit needs to be set for the dynamic buffer
handling to work.

regards
Philipp


  reply	other threads:[~2012-07-18 12:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  7:11 [PATCH v3] media: coda: Add driver for Coda video codec Javier Martin
2012-07-16 17:21 ` Philipp Zabel
2012-07-18  7:12   ` javier Martin
2012-07-18  8:35     ` Philipp Zabel
2012-07-18  9:01       ` javier Martin
2012-07-18  9:22         ` Philipp Zabel
2012-07-18  9:26           ` javier Martin
2012-07-18 12:12             ` Philipp Zabel [this message]
2012-07-18 12:19               ` javier Martin

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=1342613522.2542.154.camel@pizza.hi.pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=javier.martin@vista-silicon.com \
    --cc=kyungmin.park@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=s.hauer@pengutronix.de \
    --cc=s.nawrocki@samsung.com \
    --cc=sakari.ailus@maxwell.research.nokia.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.