Hi,
On Sat, Mar 30, 2019 at 7:25 AM Ezequiel Garcia
<ezequiel@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Fri, 29 Mar 2019 at 20:28, Ezequiel Garcia
> <ezequiel@xxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > On Fri, 29 Mar 2019 at 18:55, Douglas Anderson <dianders@xxxxxxxxxxxx> wrote:
> > >
> > > It appears that there is a typo in the rk3288 TRM. For
> > > GRF_SOC_CON0[7] it says that 0 means "vepu" and 1 means "vdpu". It's
> > > the other way around.
> > >
> > > How do I know? Here's my evidence:
> > >
> > > 1. Prior to commit 4d3e84f99628 ("clk: rockchip: describe aclk_vcodec
> > > using the new muxgrf type on rk3288") we always pretended that we
> > > were using "aclk_vdpu" and the comment in the code said that this
> > > matched the default setting in the system. In fact the default
> > > setting is 0 according to the TRM and according to reading memory
> > > at bootup. In addition rk3288-based Chromebooks ran like this and
> > > the video codecs worked.
> > > 2. With the existing clock code if you boot up and try to enable the
> > > new VIDEO_ROCKCHIP_VPU as a module (and without "clk_ignore_unused"
> > > on the command line), you get errors like "failed to get ack on
> > > domain 'pd_video', val=0x80208". After flipping vepu/vdpu things
> > > init OK.
> > > 3. If I export and add both the vepu and vdpu to the list of clocks
> > > for RK3288_PD_VIDEO I can get past the power domain errors, but now
> > > I freeze when the vpu_mmu gets initted.
> > > 4. If I just mark the "vdpu" as IGNORE_UNUSED then everything boots up
> > > and probes OK showing that somehow the "vdpu" was important to keep
> > > enabled. This is because we were actually using it as a parent.
> > > 5. After this change I can hack "aclk_vcodec_pre" to parent from
> > > "aclk_vepu" using assigned-clocks and the video codec still probes
> > > OK.
> > >
> > > Fixes: 4d3e84f99628 ("clk: rockchip: describe aclk_vcodec using the new muxgrf type on rk3288")
> > > Signed-off-by: Douglas Anderson <dianders@xxxxxxxxxxxx>
> > > ---
> > > I currently have no way to test the JPEG mem2mem driver, so hopefully
> > > others can test this and make sure it's happy for them. I'm just
> > > happy not to get strange errors at boot anymore.
> > >
> >
> > I won't have access to this hardware for a few days, but I am happy
> > to provide a simple test tool.
> >
> > Still haven't reviewed this, but thanks for chasing it down!
> >
>
> Here's a simple tool that tests JPEG encoding. There are two branches,
> with request API and without request API:
>
> https://gitlab.collabora.com/ezequiel/v4l-jpeg
>
> Usage is fairly simple, there's a test.sh that runs three tests,
> writing three JPEG images.
Didn't work for me. I got:
unable to allocate media request 25
===
OK, after a bunch of debugging, I realized that I needed your series
from <https://patchwork.kernel.org/cover/10838323/>. I applied that
together with my patch to the to of Heiko's current for-next tree and
I see:
destination plane sizeimage 76800 bytes
source plane 0 sizeimage 76800 bytes
source plane 1 sizeimage 19200 bytes
source plane 2 sizeimage 19200 bytes
src plane 0 mapped 76800 bytes
src plane 1 mapped 19200 bytes
src plane 2 mapped 19200 bytes
capture buffer size: 76800
capture bytes: 6385
bars-i420-320_240.jpeg written, 6385 bytes
destination plane sizeimage 76800 bytes
source plane 0 sizeimage 76800 bytes
source plane 1 sizeimage 38400 bytes
src plane 0 mapped 76800 bytes
src plane 1 mapped 38400 bytes
capture buffer size: 76800
capture bytes: 6385
bars-nv12-320_240.jpeg written, 6385 bytes
destination plane sizeimage 76800 bytes
source plane 0 sizeimage 153600 bytes
src plane 0 mapped 153600 bytes
capture buffer size: 76800
capture bytes: 6385
bars-yuy2-320_240.jpeg written, 6385 bytes
-Doug
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-rockchip
