#linux-exynos on 2017-10-23 — irc logs at freenode.irclog.whitequark.org

2014-05-14 17:51 Wizzup changed the topic of #linux-exynos to: This channel is logged: http://irclog.whitequark.org/linux-exynos | http://linux-exynos.org | http://lists.linux-exynos.org/listinfo/linux-exynos | https://github.com/linux-exynos

02:04 nighty- has joined #linux-exynos

02:21 _whitelogger has joined #linux-exynos

02:24 ansiwon has joined #linux-exynos

04:05 TheSeven has quit [Ping timeout: 252 seconds]

04:06 TheSeven has joined #linux-exynos

04:14 TheSeven has quit [Ping timeout: 255 seconds]

04:14 TheSeven has joined #linux-exynos

04:48 _whitelogger has joined #linux-exynos

05:24 _whitelogger has joined #linux-exynos

05:41 kloczek_ has joined #linux-exynos

05:44 kloczek has quit [Ping timeout: 248 seconds]

05:44 kloczek_ is now known as kloczek

08:50 aballier has joined #linux-exynos

09:02 <mszyprow> memeka: ping

09:30 kxkamil has joined #linux-exynos

10:42 nighty- has quit [Quit: Disappears in a puff of smoke]

10:57 <memeka> mszyprow: hi, sorry busy day

10:58 <memeka> mszyprow: compiling now latest patch

10:58 <mszyprow> memeka: no problem

11:01 <memeka> mszyprow: ERROR: from element /GstPipeline:pipeline0/v4l2video1h264enc:v4l2video1h264enc0: Failed to process frame.

11:01 <memeka> gst_v4l2_video_enc_handle_frame (): /GstPipeline:pipeline0/v4l2video1h264enc:v4l2video1h264enc0:

11:01 <memeka> Maybe be due to not enough memory or failing driver

11:02 <memeka> i would say failing driver, i am encoding 480p video

11:02 <memeka> :P

11:02 <mszyprow> okay, so more hack are needed then

11:03 <memeka> mszyprow: http://paste.debian.net/992238/

11:03 <memeka> after echo 4 > /sys/module/s5p_mfc/parameters/debug

11:04 <memeka> is level 4 enough, or you want more messages?

11:04 <memeka> (they include mfc dec too)

11:04 <memeka> s5p_mfc_try_run_v6:1694: Couldn't lock HW.

11:04 <memeka> maybe this is the issue

11:06 <mszyprow> okay for now, I would need to understand that part of the driver first...

11:07 <memeka> mszyprow: for the pmu counters, you think it's ok to add a "soc" node under which to put the affinities, in the -cpus dts?

11:09 <mszyprow> memeka: I have other idea, maybe both pmus should be kept in 54xx.dtsi and only the affinity property is moved to -cpus.dtsi

11:09 <mszyprow> memeka: this way it would be okay even for 5410

11:09 <memeka> ^^ like i said :P

11:10 <memeka> affinities in there :)

11:10 <mszyprow> right, I didn't read the whole message ;)

11:10 <memeka> affinities + status = okay, in 54xx status = disabled ?

11:10 <mszyprow> you would need to add labels to both pmus

11:11 <mszyprow> sounds good

11:11 <memeka> but i need to put them under soc node in the -cpus dtsi, right?

11:11 <mszyprow> and use &label { } style in -cpus.dtsi

11:14 <memeka> then i don't need the soc node to put them under, right?

11:14 <mszyprow> right

11:29 <memeka> mszyprow: http://paste.debian.net/992240/

11:29 <memeka> this looks good? (sorry i am not good with dts :P)

11:32 <mszyprow> yes, looks good

11:33 <mszyprow> wait

11:34 <mszyprow> memeka: in 5420 - have you checked which cpus are a7/a15?

11:35 <mszyprow> exynos5420-cpus.dtsi says that cpu0-4 are a15s and 4-7 a7s

11:42 <memeka> yes

11:42 <memeka> wait

11:42 <memeka> i checked only 5410

11:43 <memeka> mszyprow: yes you are right, thanks for spotting that

11:43 <memeka> it's 11pm here :|

12:17 prahal has joined #linux-exynos

12:41 prahal has quit [Quit: prahal]

12:44 prahal has joined #linux-exynos

12:46 <krzk> memeka: mszyprow: The PMU counters I think are not part of Soc

12:46 <krzk> but like CPU-s, outside. This is part of ARM design, right?

12:47 <mszyprow> krzk: in 5250 and 5250 they are already under soc

12:47 <mszyprow> krzk: and gic and other arm specific modules are also under soc

12:47 <krzk> mszyprow: ah, okay, arch timer is there anyway

12:47 <krzk> true

12:47 <mszyprow> krzk: you cannot put it under cpu node

12:48 <krzk> mszyprow: I was thinking next to it, but let's follow convention and other ARM stuff is also under soc

12:49 <mszyprow> krzk: the nodes next to soc are typically board specific periperals...

12:49 <krzk> mszyprow: so... cpus should be under soc as well :)

12:50 <mszyprow> right, but for some historical reason they have to be under root

12:50 <mszyprow> afair

12:50 <krzk> mszyprow: in few DTSI from other boards (e.g. keystone.dtsi) arm generic stuff is outside of SoC

12:51 <krzk> mszyprow: also omap, axm... seems this is not well-defined

12:52 <mszyprow> once we already have arch_timer under soc node, then lets follow this convention

12:53 <krzk> makes sense, someday we will move everything outside making even more commits, ha!

13:20 nighty- has joined #linux-exynos

13:51 nighty-- has joined #linux-exynos

14:03 mszyprow has quit [Ping timeout: 240 seconds]

14:08 nighty-- has quit [Ping timeout: 248 seconds]

14:54 nighty-- has joined #linux-exynos

15:23 nighty-- has quit [Ping timeout: 260 seconds]

16:22 kxkamil has quit [Quit: Leaving]

16:29 Vasco_O is now known as Vasco

16:33 snawrocki has quit [Quit: Leaving]

16:34 prahal has quit [Quit: prahal]

16:38 3NAABQ8S8 has joined #linux-exynos

16:51 snawrocki has joined #linux-exynos

17:45 kloczek_ has joined #linux-exynos

17:48 kloczek has quit [Ping timeout: 240 seconds]

17:48 kloczek_ is now known as kloczek

18:29 3NAABQ8S8 has quit [Ping timeout: 255 seconds]

19:01 prahal has joined #linux-exynos

20:23 aballier has quit [Quit: leaving]

20:29 libv_ has joined #linux-exynos

20:32 libv has quit [Ping timeout: 260 seconds]

20:34 libv has joined #linux-exynos

20:37 libv_ has quit [Ping timeout: 260 seconds]

20:39 libv_ has joined #linux-exynos

20:41 libv has quit [Ping timeout: 260 seconds]

20:53 libv has joined #linux-exynos

20:57 libv_ has quit [Ping timeout: 260 seconds]

22:48 prahal has quit [Read error: Connection reset by peer]

22:50 prahal has joined #linux-exynos

22:55 prahal has quit [Ping timeout: 240 seconds]