Core-chat-meeting-2016-08-09 10:01 < geertu> Welcome to today's Core Group Chat 10:02 < geertu> It seems everybody is online (whatever that may mean), except for dammsan. 10:02 < khiemnguyen> hi 10:04 < geertu> So let's start with the status updates. I'll go first 10:04 < geertu> A) What have I done since last time 10:04 < geertu> Meetings, conferences, holidays 10:04 < geertu> B) What I plan to do till next time 10:04 < geertu> - MSIOF parent clock prototype, 10:04 < geertu> - Resume RST, MODEMR, ... 10:04 < geertu> C) Problems I have currently 10:04 < geertu> Nothing 10:04 < geertu> If you have questions/comments, feel free to interrupt ;-) 10:06 < geertu> "sort -R < members" tells me the next person is Shimoda-san 10:06 < shimoda> yes 10:07 < geertu> Shall I quote what you emailed? Or will you? 10:07 < shimoda> i will do 10:07 < geertu> OK, thx 10:07 < shimoda> A) What have I done since last time 10:07 < shimoda> I have no tasks for core group. But, 10:07 < shimoda> - I found an issue in usb-dmac driver. So, I sent a patch and Vinod applied this. 10:07 < shimoda> - I got a question about bias function from the BSP team. 10:07 < shimoda> And, I got information from Laurent-san and forwarded to the BSP team. 10:07 < shimoda> B) What I plan to do till next time 10:07 < shimoda> I will describe the lossy function to eLinux this time... 10:07 < shimoda> C) Problems I have currently 10:07 < shimoda> On Gen3, USB EHCI + IPMMU doesn't work correctly. 10:07 < shimoda> (But, this depends on data size. (Small data (within 4KB) can be transferred.)) 10:07 < shimoda> So, I'm investigating this with HW guy. 10:08 < pinchartl> is this related to the known IPMMU hardware bug on H3 ? 10:08 < shimoda> please let me know if you have any questions :) 10:09 < khiemnguyen> shimoda: USB XHCI + IPMMU does not have same issue, right ? 10:10 < shimoda> khiemnguyen: correct. this issue is just EHCI 10:10 -!- neg [~neg@unaffiliated/neg] has quit [Read error: Connection reset by peer] 10:10 -!- neg [~neg@unaffiliated/neg] has joined #periperi 10:10 < pinchartl> have you tested this on H3 or M3 ? 10:12 < shimoda> pinchartl: about EHCI? 10:12 < pinchartl> yes 10:12 < shimoda> yes, I tested EHCI on both H3 and M3 10:12 < pinchartl> thanks 10:14 < geertu> shimoda: Thank you. 10:14 < geertu> Next person is Ulrich. 10:15 < uli___> a) and b), nothing 10:15 < uli___> c) my m3-w sys-dmac task is not included in my additional task sow 10:15 < uli___> i guess that will be worked out once magnus is back 10:16 < morimoto> uli___: I'm waiting reply from you about M3 board export 10:16 < uli___> sent it a minute ago, sorry for the delay 10:16 < morimoto> Oh thanks 10:17 < geertu> uli___: The m3-w sys-dmac task was planned for Q3 phase 1, and sent to Magnus. 10:18 < horms> (my connection is a bit flakey; if I drop off that will be why) 10:19 < geertu> uli___: Do you plan to send a v2 for the r8a7796 PFC support? 10:19 < uli___> yes, i will 10:20 < geertu> OK 10:20 < geertu> So I'll add that to B) :-) 10:20 < uli___> please :) 10:21 < geertu> uli___: Thank you 10:21 < geertu> Next person is Simon 10:21 < horms> A) What have I done since last time 10:21 < horms> Verified Suspend-to-RAM appears to work as well on M3-3/Salvator-X as 10:21 < horms> on H3/Salvator-X. That is suspend seems to work but resume occurs 10:21 < horms> immediately due to side effects of work arounds in firmware for hardware 10:21 < horms> problems with DDR timing. 10:21 < horms> Summer vacation, moved to the Netherlands. 10:21 < horms> B) What I plan to do till next time 10:21 < horms> Finalise Suspend-to-RAM work by writing report, test procedure, etc... 10:21 < horms> Begin work on kexec for M3-W. 10:21 < horms> C) Problems I have currently 10:21 < horms> What to do about H3ULCB board patches from Cogent. 10:21 < horms> Lets discuss this in this meeting if there is time. 10:21 < horms> 10:21 < horms> Any and all questions about above welcome. 10:22 < geertu> horms: OK, we can discuess H3ULCB after the status updates 10:22 < horms> great 10:23 < geertu> (that gives some time to Morimoto-san to dig up the documentation ;-) 10:23 < geertu> horms: Thank you 10:23 < geertu> Next person is Magnus, but he's not here 10:23 < geertu> Next person is Morimoto-san 10:24 < morimoto> OK, but Unfortunately, I have no Core task today. So I have nothing for a) b) c) 10:24 < geertu> I do have from you for A) 10:24 < geertu> - I started export paper work for M3 board for you guys 10:24 < geertu> - I had worked for Multimedia, no task for Core 10:24 < geertu> B) 10:24 < geertu> - I need to continue export paper work, and ship it ASAP if possible 10:24 < geertu> - No plan for Core 10:24 < geertu> C) 10:24 < geertu> - I don't like paper work 10:24 < geertu> - Decision of Summer Vacation plan 10:24 < morimoto> Thanks. C) is very big issue for me :) 10:25 < geertu> First or last subtopic? 10:25 < morimoto> both 10:25 < geertu> It seems the M3-W shipping is on track? 10:25 < morimoto> I'm working for export paper work for M3 10:25 < morimoto> But under paper work 10:26 < morimoto> Niklas and Kilan's board goes through Magnu/Laurent 10:26 < morimoto> s/Magnu/Magnus/ 10:26 < morimoto> Because of Japanese Summer Vacation timing, shipping might be after Summer Vacation 10:27 < horms> I see the two items in C) are related to each other :) 10:27 < morimoto> I would like to shipping immediately, but... 10:27 < morimoto> geertu: that's it from me 10:28 < geertu> morimoto: Thank you 10:28 < geertu> Next person is Niklas 10:28 < neg> a: Nothing for core 10:28 < neg> b: Find a core task and start to work on it 10:29 < neg> c: no core task 10:29 < neg> I also have a question but we can save it to after the status part of the meeting. 10:29 < geertu> OK 10:29 < geertu> neg: Thank you! 10:29 < geertu> Next person is Khiem 10:30 < khiemnguyen> > A) What have I done since last time 10:30 < khiemnguyen> Tracking the update of CPUFreq in in-house BSP v3.3.2. 10:30 < khiemnguyen> BTW, I found that Kaneko-san has sent 2 patches to update Z-clock calculation for H3. 10:30 < khiemnguyen> However, it seems that the patches applied to wrong source file (clk-rcar-gen2.c) 10:30 < khiemnguyen> I will try to look into that patches and reply the emails. 10:30 < khiemnguyen> I will try to look into that patches and reply the emails. 10:30 < khiemnguyen> > B) What I plan to do till next time 10:30 < khiemnguyen> Complete Gen3 CPUFreq patchset. 10:30 < khiemnguyen> > C) Problems I have currently 10:30 < khiemnguyen> Time flies but nothing complete. 10:30 < khiemnguyen> Will need to check my to-do list again. 10:31 < khiemnguyen> that's all from me. 10:32 < horms> About those patches 10:32 < horms> they are from the BSP 10:32 < horms> I assumed Kaneko-san would rebase them to use the correct source file 10:33 < horms> sorry that he didn't but if you could look into them anyway I would be grateful 10:33 < khiemnguyen> horms: yes, I will reply his email. 10:34 < horms> great, thanks! 10:37 < pinchartl> morimoto: regarding the M3 boards, you mentioned shipment could get delayed after summer vacation, when would that be, roughly ? 10:37 < geertu> khiemnguyen: Thank you! 10:37 < morimoto> pinchartl: we don't know at this point. I'm tring hard for it now 10:38 < morimoto> If I can do *before* summer vacation, we can ship end of this week 10:38 < pinchartl> ok 10:38 < morimoto> If I couldn't, It will be after summer vacation, it will be 22th's week 10:38 < pinchartl> I will be away from home from the 18th to the 30 of August 10:39 < morimoto> Ohh.. 10:39 < geertu> Ship it to Toronto ;-) 10:40 < pinchartl> geertu: given that I'll be in Belgium and France, I don't think that would help 10:40 < horms> Probably it is not helpful, but if it is I'm happy to act as an intermediary 10:40 < geertu> pinchartl: Oh, you're skipping LinuxCon 10:41 < geertu> I'm in Belgium between 18th and 30th of August anyway 10:41 < pinchartl> :-) 10:42 < pinchartl> morimoto: so, there's no urgency for me. Kieran will also be back at the end of the month only 10:42 < pinchartl> you can thus ship the boards at end of August 10:42 < pinchartl> no need to rush, enjoy your summer vacation :-) 10:43 < shimoda> morimoto-san is now calling to someone 10:44 < shimoda> this seems related to the peper work :) 10:46 < morimoto> Sorry, it was shipment guy. 10:46 < morimoto> We try to ship board 11th from Renesas, but it seems shipment side is busy 10:46 < geertu> Last person is Laurent 10:47 < pinchartl> nothing to report for core 10:47 < pinchartl> no work done, no work to do, no issue :-) 10:48 < morimoto> Perfect !! 10:48 < geertu> pinchartl: Thank you! 10:49 < pinchartl> nyt on lounasaika ! 10:49 < pinchartl> (now is lunch time) 10:49 < geertu> Let's eat H3ULCB 10:49 < geertu> pinchartl: enjoy your lunch! 10:49 < morimoto> :P 10:49 < pinchartl> talk to you later 10:50 < neg> I have a question if it would be bad to send a patch to enable CONFIG_CGROUPS in shmobile_defconfig? 10:50 < geertu> So it seems Renesas/Cogent have a low-cost H3 board called H3ULCB 10:50 < neg> ohh my bad please go ahead with H3ULCB talk 10:50 < geertu> neg: No objection. It's what makes shmobile_defconfig boot on my koelsch 10:50 < horms> neg: I'm ok with that if there is a reason for it 10:51 < geertu> Although my personal koelsch config doesn' 10:51 < geertu> t hav it set 10:51 < horms> MY position on the H3ULCB patches is this: 10:51 < neg> horms: is i need it for systemd init and I keep forgeting to enable it and it bugs me a good reason? Other then that I have no real technical reason to wish to enable it :) 10:51 < horms> 1) I'm mostly ok with adding a board we can't test as its for an SoC that is already in mainline 10:51 < geertu> So in shmobile_defconfig, it seems to avoid the strange lock ups during boot, which I could also avoid by adding the right number of nop()s 10:52 < horms> neg: sounds good. systemd is standard on Debian these days. I would probably have the same problem if I updated userspace. And Debian is the defacto user-space test imho 10:52 -!- khiemnguyen [d2a0fca8@gateway/web/cgi-irc/kiwiirc.com/ip.210.160.252.168] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 10:53 < neg> OK thanks I will send a patch enableing it then 10:53 < horms> 2) I'd like them to split up the patch to enable IP blocks one by one 10:53 < horms> 3) I'd prefer if any IP blocks not enabled on H3/Salvator-X were at the end of the patch-set 10:53 -!- khiemnguyen [d2a0fca8@gateway/web/cgi-irc/kiwiirc.com/ip.210.160.252.168] has joined #periperi 10:54 < horms> 4) I would value input from the group, especially Morimoto-san and Shimoda-san -> I think Renesas should be aware of this 10:54 < horms> --- thats about it from my side --- 10:54 < geertu> I agree with all four points 10:54 < geertu> 5) Can we get documentation? 10:55 < geertu> 6) Can we get access to a board (e.g. in Magnus' farm)? 10:56 < shimoda> geertu: at the moment, i don't have the board. 10:57 < morimoto> shimoda: we can have 1 or 2 boards. 10:57 < horms> shimoda: do you think some kind of discussion with e.g. Munakata-san would be best before adding the board to mainline? 10:57 < morimoto> Maybe we will ask to Magnus about remove-access ? 10:59 < horms> I think that would be ideal 11:00 < morimoto> horms: about discussion with Munakata-san, maybe no discussion is needed, but we will re-check 11:00 < horms> Thanks! 11:01 < geertu> That's good to hear. 11:01 < geertu> I assume documentation will follow, too? 11:02 < morimoto> depends on which documentation. "board" documentation ? 11:02 < morimoto> you can get it from elinux on some board. (I don't know which board...) 11:02 < geertu> morimoto: Yes, e.g. schematics, so we can review the DTS 11:03 < geertu> morimoto: Not for H3ULCB AFAIK (porter and silk you can) 11:03 < morimoto> schematics is a little bit difficult. 11:03 < morimoto> I can say case-by-case 11:04 < horms> well, probably anything for the H3ULCB would be helpful 11:05 < horms> but if there is nothing available 11:05 < horms> we can just trust Cogent 11:05 < morimoto> hmm... 11:07 < khiemnguyen> for Porter or Silk, if we buy the boards, I think the schematics files are available in the CD. 11:10 < geertu> khiemnguyen: For porter and silk, there are links to the schematics on the eLinux wiki. You need to register with Renesas to access the links, though. 11:11 < khiemnguyen> I think H3ULCB will be the same, but we need to wait till next year ? 11:14 < horms> Ok, sounds like we should wait 11:15 < shimoda> about the documentation of H3ULCB, i will ask Munakata-san or Ito-san 11:15 < shimoda> if no doc, we should wait 11:17 < geertu> shimoda: ok, thx! 11:23 < morimoto> Is meeting finished ?? 11:24 < uli___> not sure :) 11:24 < geertu> Sorry, too distracted by SoW paperwork issues... 11:25 < geertu> Yes, unless someone has something to add, I think the meeting is finished 11:25 < neg> I would like to know if there is any core task I can start to work on, but maybe we can take that my mail :-) 11:26 < morimoto> OK, thanks. 11:26 < morimoto> geertu: please enjoy your paperwork :) 11:29 -!- morimoto [~user@relprex2.renesas.com] has left #periperi ["ERC Version 5.3 (IRC client for Emacs)"] 11:31 < geertu> neg: yes, email please 11:31 < geertu> Thanks for joining!