<nasix>
Hi all. I'm going to use MFC on my custom HW (which is based on the old series of S5PV210 SoC).
<nasix>
Is it working correctly on the latest mainline kernel?
<nasix>
I could test it successfully on v3.12.66 LTS (for encoding) and v3.4.112 LTS (for decoding). None of them could be used in both encoding/decoding together. Do you have any advice?
<nasix>
I know that here is the exynos IRC (and not the old s5p series) but if you share your experience on exynos, it may be helpful to find my way.
LiquidAcid has joined #linux-exynos
nasix has quit [Ping timeout: 250 seconds]
LiquidAcid has quit [Quit: Leaving]
paulk-collins has joined #linux-exynos
nasix has joined #linux-exynos
<javier__>
nasix: hi, the s5p-mfc driver should work on latest mainline
<javier__>
I've only tried decoding though, since I tested with GStreamer and it doesn't have a encode element yet
<nasix>
javier__: Thank you for your reply. But then have anybody tested it on S5Pv210?
<nasix>
I know your name with the latest patches on that!
<nasix>
I mean GStreamer on exynos.
<javier__>
nasix: that's a good question. I've tested with Exynos5422 and Exynos5800 that has a MFC v7 and v8 respectively
<javier__>
but s5pv210 has a v5
<javier__>
the things I fixed are independent of the MFC version but I haven't tested on that IP version
ayaka has quit [Quit: byte]
ayaka has joined #linux-exynos
<nasix>
Ok. So there are so many things to try.
<nasix>
and test.
<javier__>
nasix: if you want to add something more to the list, there's a gst v4l2videoenc element that was developed by ayaka but never merged
<javier__>
nasix: Ok, please let me know if you find any issues with mainline
<nasix>
The first problem for the mainline kernel is I can not boot my hardware with the main line kernel. I have tried so many different kernel versions to make MFC decode and encode work.
<nasix>
When it comes to newer kernels, the booting problem starts to appear. When I use DTS, I have some divide by zero error (when setting clocks) when booting the kernel.
<javier__>
nasix: I see, so you are using a an old vendor tree that uses board files instead of DT?
<javier__>
I see a bunch of S5PV210 SoC based DTS in arch/arm/boot/dts/s5pv210*
<javier__>
but I wonder for how long no one has tested those...
<nasix>
I used to compile a vendor tree. But Now I can successfully compile the mainline stable branch like v3.12 LTS.
<javier__>
I see
<nasix>
I had not enough time to solve this problem. I'm using DTS from arch/arm/boot/dts/ which is for another HW but the same SoC.
<nasix>
I think it should at least boot correctly to some point after the clock initialization. Am I missing something?
<javier__>
nasix: problem is that support in mainline bit rot if someone is not looking at it
<javier__>
even for newer SoCs like Exynos5, I've a new regression on v4.9-rc1 where the SD is not detected in a board due a clock subsys change
<nasix>
I see
<javier__>
and the s5pv21 is an old SoC...
<javier__>
*s5pv210
<javier__>
nasix: but you could try providing your boot log and all the info to linux-samsung-soc@vger.kernel.org
<nasix>
Yes. We have some custom HW which are built around s5pv210 and I'm going to add some software stuff on them.
<nasix>
javier__: Thats a good idea. I definitely try it.
<javier__>
nasix: Ok
<javier__>
sorry that I could not be of too much help, I don't have neither experience with s5pv210 nor access to a board based on that SoC
<nasix>
But your info was helpful.
<nasix>
As another question, I have an fb based implementation of TV-out in my old source which works correctly. Do you know why we do not have such implementation anymore in the mainline?
<nasix>
do you know if analog TV-out is working properly in the mainline kernel? I mean as a v4l2 device?
<javier__>
nasix: you mean s5p-tv right?
<nasix>
yes.
<javier__>
nasix: in *theory* it has been superseded by the exynos-drm driver
<javier__>
and DRM has fb emulation so you could have the same functionality
<javier__>
in practice, I haven't tested so I can't tell you if everything is supported
<nasix>
I think DRM is not supported for s5pv210 in mainline kernel.
<javier__>
nasix: that's why I said in theory, but worth give it a try since otherwise it wouldn't had been removed from mainline
nasix_ has joined #linux-exynos
<javier__>
nasix: most v4l2 drivers have been replaced by their exynos-drm counterpart, but can't been removed yet due a lack of feature parity
nasix has quit [Ping timeout: 256 seconds]
nasix_ has quit [Quit: Leaving]
nasix_ has joined #linux-exynos
<nasix_>
javier__: so to have support for MFC on recent kernels for my SoC, I should first add the support to DRM?
<javier__>
nasix_: yes, or if is true that exynos-drm doesn't support s5pv210, you could ask for the s5p-tv to be brought back
<nasix_>
For using DRM, should I have to have a running GPU?
<javier__>
nasix_: no, that's orthogonal. KMS/DRM doesn't need 3D HW acceleration
<javier__>
IOW, the exynos-drm driver is just to support the display controller
<nasix_>
fimd, right?
<snawrocki>
nasix_, __javier: DRM is not needed for video decoding on s5pv210, only s5p-mfc driver for MFC (video decoding/encoding) and exynos4-is for video post processing (conversion of the tiled format to YUV/RGB)
<snawrocki>
DRM is only needed for display
<snawrocki>
I remember analog TV out working with v4l2 s5p-tv drivers a few years ago, but AFAICT this functionality is not ported to exynos_drm
<nasix_>
snawrocki: thank you for your info. could you remember the kernel version?
<snawrocki>
for s5pv210 it might be easier to restore s5p-tv, for HDMI and TV out
<javier__>
snawrocki: yes, I know that only s5p-mfc is needed for video {en,de}coding
<javier__>
snawrocki: but nasix_ also mentioned that he needed video output and I mentioned DRM since the s5p-tv was removed due being superseded by exynos-drm mixer/hdmi
<nasix_>
when I enable the support for s5p-tv, I think I should see a new node in /dev/video* or /sys/class/video4linux/video* but nothing appears.
<snawrocki>
nasix: unfortunately not, but it was before adding devicetree support s5pv210 in mainline
<snawrocki>
nasix: are you booting from DT or using board files?
<nasix_>
booting from DT fails. I'm using board files
<snawrocki>
javier__: fair enough, I just wrote to quick didn't have read your all replies
<snawrocki>
nasix: and you have required platform device added for s5p-tv? Does driver get probed? New video nodes should of course appear.
ayaka has quit [Quit: byte]
ayaka has joined #linux-exynos
<javier__>
snawrocki: no worries, sorry if my comments were confusing
<snawrocki>
nasix: perhaps you don't have regulator supplies specified in your board file and driver probing fails ?
<snawrocki>
nasix: you need s5p_device_mixer and s5p_device_sdo in your list of platform devices in board file
<snawrocki>
nasix: you should have 2 "probe successful" entries in kernel log - from sdo_probe() and mxr_probe(), if that's missing I wouldn't be expecting any new video nodes...
<nasix_>
snawrocki: OK, let me check it.
<nasix_>
snawrocki: There is no prob message in the kernel message. I should add them to the board file. Let me test it.
<snawrocki>
nasix_: Sure, take your time. AFAICS you should have "vdd33a_dac" and "vdet" regulator supplies attached you s5p_device_sdo in board file
<nasix_>
Thank you for your help. I'll try that.
nasix_ has quit [Ping timeout: 265 seconds]
nasix_ has joined #linux-exynos
ayaka has quit [Quit: byte]
ayaka has joined #linux-exynos
nasix_ has quit [Quit: Leaving]
afaerber has quit [Quit: Ex-Chat]
wiewo_ is now known as wiewo
wiewo is now known as Guest67598
afaerber has joined #linux-exynos
afaerber has quit [Ping timeout: 245 seconds]
afaerber has joined #linux-exynos
Guest67598 is now known as wiewo
LiquidAcid has joined #linux-exynos
amitk has quit [Quit: leaving]
theblazehen_ has joined #linux-exynos
Vasco is now known as Vasco_O
theblazehen_ has quit [Read error: No route to host]