mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: "open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB)" 
	<linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	hverkuil@xs4all.nl, kernel@collabora.com, dafna3@gmail.com,
	Robert Beckett <bob.beckett@collabora.com>,
	kiril.bicevski@collabora.com,
	Nas Chung <nas.chung@chipsnmedia.com>,
	lafley.kim@chipsnmedia.com, scott.woo@chipsnmedia.com,
	olivier.crete@collabora.com, dan.carpenter@oracle.com,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v4 0/6] staging: media: wave5: add wave5 codec driver
Date: Mon, 13 Dec 2021 22:27:00 +0200	[thread overview]
Message-ID: <02a9c780-49e0-7a61-4443-7825d6a1271e@collabora.com> (raw)
In-Reply-To: <CAFr9PXnvbqtx-SpxjyO2uvoBR3ueNBD9vSFnbqjbAHz_7Lh8VA@mail.gmail.com>



On 02.12.21 12:11, Daniel Palmer wrote:
> Hi Dafna,
> 
> On Thu, 2 Dec 2021 at 02:56, Dafna Hirschfeld
> <dafna.hirschfeld@collabora.com> wrote:
>> Testing on BeagleV shows buffer corruption that is currently attributed to a
>> known silicon issue in the SoC that makes the cache coherent interconnect not
>> so coherent.
> 
> Maybe it's mentioned somewhere else and I missed it but would it be
> possible to tell me which version of the IP is in the BeagleV chip?
> The reason I ask is I'm trying to get this going on the SigmaStar
> SSD202D which seems to have the "Wave 511".
> I can see the firmware binary get uploaded and it seems to do
> something as the register that exposes the vcpu program counter is
> doing something (and the addresses look the same as the addresses seem
> when the working vendor kernel + binary .ko are running so I think
> it's not just running garbage).
> 
> I'm wondering if the BeagleV is a different version and the driver
> just won't work as is on mine or maybe the firmware I have has hacks
> for the vendors version of the driver which I don't have source for.

Hi, thank you for trying this out. The versions I see on the Beaglv are 511 for the
decoder and 521c for the encoder.
This driver is also based on a vendor driver from cnm: https://gitlab.collabora.com/chipsnmedia/wave5-driver
Also, a patch to add the firmware was also sent to linux-firmware ml https://lore.kernel.org/linux-firmware/20211126093014.1385752-1-nas.chung@chipsnmedia.com/T/

Thanks,
Dafna

> 
> Thanks,
> 
> Daniel
> 

      reply	other threads:[~2021-12-13 20:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 17:56 Dafna Hirschfeld
2021-12-01 17:56 ` [PATCH v4 1/6] staging: media: wave5: Add vpuapi layer Dafna Hirschfeld
2021-12-04 13:43   ` Daniel Palmer
2021-12-14  5:33     ` Dafna Hirschfeld
2021-12-14  7:48       ` Dafna Hirschfeld
2021-12-14 10:20         ` Daniel Palmer
2022-01-21  9:22           ` Dafna Hirschfeld
2022-01-21  9:33             ` Daniel Palmer
2021-12-01 17:56 ` [PATCH v4 2/6] staging: media: wave5: Add the vdi layer Dafna Hirschfeld
2021-12-01 17:56 ` [PATCH v4 3/6] staging: media: wave5: Add the v4l2 layer Dafna Hirschfeld
2021-12-01 17:56 ` [PATCH v4 4/6] staging: media: wave5: Add TODO file Dafna Hirschfeld
2021-12-01 17:56 ` [PATCH v4 5/6] dt-bindings: media: staging: wave5: add yaml devicetree bindings Dafna Hirschfeld
2021-12-01 17:56 ` [PATCH v4 6/6] media: wave5: Add wave5 driver to maintainers file Dafna Hirschfeld
2021-12-02 10:11 ` [PATCH v4 0/6] staging: media: wave5: add wave5 codec driver Daniel Palmer
2021-12-13 20:27   ` Dafna Hirschfeld [this message]

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=02a9c780-49e0-7a61-4443-7825d6a1271e@collabora.com \
    --to=dafna.hirschfeld@collabora.com \
    --cc=bob.beckett@collabora.com \
    --cc=dafna3@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=daniel@0x0f.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil@xs4all.nl \
    --cc=kernel@collabora.com \
    --cc=kiril.bicevski@collabora.com \
    --cc=lafley.kim@chipsnmedia.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.com \
    --cc=olivier.crete@collabora.com \
    --cc=rdunlap@infradead.org \
    --cc=scott.woo@chipsnmedia.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

all inboxes | Powered by JetHome®