All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: cx88 invalid video opcodes when VBI enabled
Date: Tue, 17 Apr 2018 06:53:01 +0200	[thread overview]
Message-ID: <20180417045300.GA7723@minime.bse> (raw)
In-Reply-To: <CAGoCfiw_oD6PLOoot55zkNBVaujeG7ReNQORiqUbLuh-=iwcyw@mail.gmail.com>

Hi,

On Sun, Apr 15, 2018 at 01:37:50PM -0400, Devin Heitmueller wrote:
> Any suggestions on the best way to debug this without having to learn
> the intimate details of the RISC engine on the cx88?  From the state
> of the RISC engine it looks like there is some issue with queuing the
> opcodes/arguments (where in some cases arguments are interpreted as
> opcodes), but this is certainly not my area of expertise.

> [   54.427224] cx88[0]: irq vid [0x10088] vbi_risc1* vbi_risc2* opc_err*
> [   54.427232] cx88[0]/0: video risc op code error
> [   54.427238] cx88[0]: video y / packed - dma channel status dump

Since the video IRQ status register has vbi_risc2 set, which we never
generate with our RISC programs, I assume it is the VBI RISC engine
that is executing garbage. So the dump of the video y/packed RISC engine
does not help us here. Can you add a call to cx88_sram_channel_dump for
SRAM_CH24 next to the existing one in cx8800_vid_irq?

Best regards,

  Daniel

  reply	other threads:[~2018-04-17  4:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-15 17:37 cx88 invalid video opcodes when VBI enabled Devin Heitmueller
2018-04-17  4:53 ` Daniel Glöckner [this message]
2018-04-17 13:05   ` Devin Heitmueller
2018-04-18  1:49     ` Devin Heitmueller
2018-04-18 18:29       ` Daniel Glöckner
2018-04-20 21:54         ` Daniel Glöckner
2018-04-21 17:57           ` Devin Heitmueller

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=20180417045300.GA7723@minime.bse \
    --to=daniel-gl@gmx.net \
    --cc=dheitmueller@kernellabs.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.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.