From 55e3b2f45880faaf06f3c660ca9e8a6d9aa14bce Mon Sep 17 00:00:00 2001 From: Kuninori Morimoto Date: Mon, 9 Dec 2019 15:29:52 +0900 Subject: wiki: Porting wiki: Porting Chat Log Signed-off-by: Kuninori Morimoto --- wiki/Chat_log/20170411-core-chatlog | 169 ++++++++++++++++++++++++++++++++++++ 1 file changed, 169 insertions(+) create mode 100644 wiki/Chat_log/20170411-core-chatlog (limited to 'wiki/Chat_log/20170411-core-chatlog') diff --git a/wiki/Chat_log/20170411-core-chatlog b/wiki/Chat_log/20170411-core-chatlog new file mode 100644 index 0000000..3bb4208 --- /dev/null +++ b/wiki/Chat_log/20170411-core-chatlog @@ -0,0 +1,169 @@ +Core-chat-meeting-2017-04-11 + +10:03 < geertu> Welcome to today's Core Group Chat! +10:03 < geertu> Agenda: +10:03 < geertu> 1. Status updates +10:04 < geertu> Topic 1. Status updates +10:04 < geertu> First is Niklas +10:05 < geertu> A) What have I done since last time +10:05 < geertu> B) What I plan to do till next time +10:05 < geertu> C) Problems I have currently +10:05 < geertu> D) Posted/Accepted bugfix patches +10:06 < neg> a) Nothing for core +10:06 < neg> b) Hope to pick something new from core TODO +10:06 < neg> c) None +10:06 < neg> d) None +10:06 < neg> --eot-- +10:07 < geertu> Thank you, Niklas +10:07 < geertu> Next is Jacopo +10:07 < jmondi> let me retreive the email I sent +10:07 < jmondi> A) +10:08 < jmondi> - v4 of RZ pin controller +10:08 < jmondi> - RZ clock tested and enabled on Genmai +10:08 < jmondi> - tested pin controller driver with DT overlays +10:08 < jmondi> - working on using JTAG debugger on Genmai +10:09 < geertu> So it's v4, not v5? +10:09 < jmondi> B) = C) = D) = NULL +10:09 < jmondi> geertu: I wrote v5 in the email, but I got confused +10:09 < jmondi> it's v4 +10:09 < jmondi> -- eot -- +10:10 < geertu> Thank you, Jacopo. +10:10 < geertu> Next is Laurent. I assume he's just lurking around? +10:10 < pinchartl> correct +10:10 < pinchartl> I have no core task +10:10 < geertu> Next is Morimoto-san +10:11 < morimoto> A) What have I done since last time +10:11 < morimoto> I posted "SYS-DMAC + 40bit + descriptor mode" patch to ML, and it was accepted. +10:11 < morimoto> I created/fixed periupport script. I hope it is now useful :) +10:11 < morimoto> I updated "R-Car Gen3 datasheet" export paper work (Not related to PeriPeri Member/Task :) +10:11 < morimoto> B) What I plan to do till next time +10:11 < morimoto> C) Problems I have currently +10:11 < morimoto> D) Posted/Accepted bugfix patch +10:11 < morimoto> Nothing for Core group +10:11 < morimoto> --EOT-- +10:12 < geertu> Thank you, Morimoto-san +10:12 < geertu> Next is Magnus +10:12 < dammsan> no update from me, just lurking +10:13 < geertu> Next is myself +10:13 < geertu> A) +10:13 < geertu> - Finished R-Car H3 ES2.0 for clk/pfc/sysc +10:13 < geertu> - R-Car Gen2 CPG/MSSR +10:13 < geertu> - Started DTS sharing on H3 ES1.x/ES2.0, Salvator-X/ULCB +10:13 < geertu> - Some Easter holidays +10:13 < geertu> B) +10:13 < geertu> - More Easter holidays +10:13 < geertu> - Rework drivers/{clk,soc}/renesas/Kconfig +10:13 < geertu> - Publish R-Car Gen2 CPG/MSSR +10:13 < geertu> - DTS sharing +10:13 < geertu> C) None +10:14 < geertu> D) More clock fixes detected during R-Car Gen2 CPG/MSSR conversion: +10:14 < geertu> - [PATCH 1/3] ARM: dts: r8a7790: Correct parent of SSI[0-9] clocks +10:14 < geertu> - [PATCH 2/3] ARM: dts: r8a7791: Correct parent of SSI[0-9] clocks +10:14 < geertu> - [PATCH 3/3] ARM: dts: r8a7793: Correct parent of SSI[0-9] clocks +10:14 < geertu> - [PATCH] ARM: dts: r8a7792: Correct Z clock +10:14 < geertu> - [PATCH] ARM: dts: r8a7794: Add Z2 clock +10:14 < geertu> - [PATCH] ARM: dts: koelsch: Correct clock frequency of X2 DU clock +10:14 < geertu> - [PATCH] clk: renesas: rcar-gen2: Fix PLL0 on R-Car V2H and E2 +10:14 < geertu> - [PATCH] clk: renesas: r8a7745: Remove nonexisting scu-src[0789] +10:14 < geertu> - [PATCH] clk: renesas: r8a7745: Remove PLL configs for MD19=0 +10:14 < geertu> EOT +10:14 < geertu> Next is Shimoda-san +10:14 < shimoda> A) +10:14 < shimoda> - I'm testing a new IPMMU workaround on R-Car H3 ES2.0. +10:14 < shimoda> B) +10:14 < shimoda> - Intend to make some plans about implementing IPMMU features with Magnus-san +10:14 < shimoda> C) and D) +10:15 < shimoda> - Nothing for core. +10:15 < shimoda> -- EOT -- +10:15 < geertu> Thank you, Shimoda-san +10:15 < geertu> Simon is excused, arriving in Kobe. His ABCD are: +10:15 < geertu> A) No Core task at this time +10:15 < geertu> B) No Core task at this time +10:15 < geertu> C) Selecting patches for upporting +10:15 < geertu> D) None +10:16 < geertu> Marek is also excused, he let me know the following: +10:16 < geertu> A) BD9571 MFD, GPIO, and regulator drivers +10:16 < geertu> B) Publish BD9571 drivers +10:16 < geertu> It's been a while I saw Khiem and Uli +10:17 < horms> I assume Khiem has been reassigned +10:18 < geertu> Probably +10:19 < geertu> And his email routed to (the Windows equivalent of) /dev/null +10:19 < geertu> Well, that went smooth! +10:19 < horms> likely +10:19 < geertu> Any other topics to discuss? +10:19 < dammsan> at least it is translated to CR LR before going into NULL +10:19 * horms has arrived in Kobe +10:19 -!- horms [~horms@g1-27-253-251-9.bmobile.ne.jp] has quit [Quit: Leaving] +10:19 < geertu> Perhaps periupport? +10:20 < geertu> I plan to go over the core related patches, as I believe several of them were upstreamed in some form +10:21 < geertu> I already did that for the patches that had identical patch IDs in upstream +10:22 < morimoto> geertu: I posted periupport patch again. I hope you can accept it +10:23 < geertu> morimoto: Thank you. But that will probably happen only next week. +10:24 < morimoto> OK, np +10:25 < geertu> Any other topics to discuss? +10:26 < geertu> For next meeting, I propose Tuesday, April 25, 08:00 GMT / 10:00 CEST / 11:00 EEST / 17:00 JST +10:26 < neg> I have a question about JTAG :-) +10:26 < geertu> neg: shoot! +10:26 < jmondi> I have -many- questions about JTAG +10:26 < jmondi> (joking, go on neg) +10:27 < geertu> neg: Machine gun questions? +10:27 < geertu> sorry, jmondi: Machine gun questions? +10:27 < neg> A while back I got my Flyswatter 2 and managed to find and modify some OpenOCD config files to get ut running on Gen2. If those could be tested on more boards then my Koelsch I think we could (re)try to get them picked up in upstream OpenOCD. Do you think there would be value in this? +10:28 < neg> I posted the configs at https://git.ragnatech.se/renesas-jtag/ and intend to write up elinux wiki page, I assume the SW settings to enable JTAG are OK to describe there as well? +10:30 < geertu> Cool! +10:30 < geertu> I only have +10:30 < geertu> source [find interface/ftdi/flyswatter2.cfg] +10:30 < geertu> reset_config trst_and_srst +10:30 < geertu> jtag_rclk 8 +10:30 < neg> last question is aimed at Morimoto-san :-) +10:30 < geertu> (most from Magnus, IIRC) so I never got that far... +10:31 < jmondi> neg: I will send you patches to use OpenOCD+Flyswatter on RZ as well :) +10:32 < neg> jmondi: nice :-) +10:35 < kbingham> neg: I guess you haven't looked at G3 yet :) +10:36 < neg> kbingham: thats right :-) +10:36 * geertu assumes kbingham is not talking about SH7367 (SH-Mobile G3) +10:37 < kbingham> geertu: Well, maybe I was ... :D +10:37 < geertu> Every spelling mistake is a different SoC ;-) +10:37 * morimoto geertu solved my confusion +10:37 < geertu> morimoto: cs2000? +10:37 < morimoto> No, about G3 :) +10:37 * kbingham coughs : Gen 3 +10:37 < geertu> kbingham: R-Car Gen3? +10:39 * morimoto I think neg's "last question" is not yet coming ? +10:39 < neg> morimoto: sry, my question was if it's OK to mention wich SW on the board you need to flip to enable JTAG, is this OK to mention on the elinux wiki? +10:40 < neg> for Gen2 that is +10:40 < morimoto> Ahh, OK. I think it is no problem +10:41 < neg> OK thanks +10:42 < neg> So I will let them stew in the reop and write a elinux page. If you try them out on Alt or Lager please let me know if all works I can resubmit them to OpenOCD and se what happens +10:43 < neg> that was all from me, thanks +10:46 < geertu> neg: Have you tried JTAG on the KZM9D? +10:46 -!- dammsan [~dammsan@s214090.ppp.asahi-net.or.jp] has quit [Remote host closed the connection] +10:46 < geertu> It may help to solve the SMP issue +10:46 < neg> geertu: no not yet, lurking in the back of my head tho +10:47 < neg> geertu: but I think Magnus once told me some special magic where needed to get it working +10:48 < geertu> OK +10:49 < geertu> Then I think we are finished? +10:49 < geertu> Thanks for joining, and have a nice continued day! +10:50 < shimoda> thank you! +10:50 < neg> I have nothing further, and the 25th works fine for me +10:50 < neg> thanks all +10:50 < jmondi> 25th is kind of bad for me +10:50 < jmondi> national holiday here and I don't plan to be home... +10:51 < jmondi> sorry I forgot to tell +10:52 < morimoto> 25th is OK for me too +10:52 < morimoto> thanks +11:01 < morimoto> geertu: are you still here ? +11:01 < morimoto> I want to ask you about cs2000 +11:07 < geertu> morimoto: yes, still here +11:07 < morimoto> what does your "a mux clock driver with three parents" ? +11:08 < geertu> morimoto: it's a very simple driver where you can select between 3 parents +11:08 < morimoto> How to select it ? by DT ? +11:08 < geertu> By clk_ops.set_parent() +11:09 < geertu> or .determine_rate(), which selects the best parent for the requested rate +11:09 < geertu> drivers/clk/clk-mux.c +11:09 < morimoto> Ahh.. +11:10 < morimoto> OK, thanks. I will check clk-mux.c +11:17 < morimoto> 1 question again. Who/How to select parent clock of .set_parent() ? +11:17 < morimoto> This AUX_OUT usage is board specific +11:18 < morimoto> Ahh, OK, I understand +11:18 < morimoto> Thanks -- cgit v1.2.3