1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
09:01 < wsa_> welcome to the io meeting
09:01 -!- morimoto` [~user@relprex1.renesas.com] has joined #periperi
09:01 -!- morimoto [~user@relprex1.renesas.com] has quit Read error: Connection reset by peer
09:01 < wsa_> here is my 'compiled' summary:
09:01 < wsa_> (of status updates)
09:01 < wsa_> A)
09:01 < wsa_> Geert worked on named i2c GPIO bindings, Ethernet PHY reset v4, SPI eeprom DT
09:01 < wsa_> support and MSIOF chip select support. Wolfram worked on R-Car I2C bus
09:01 < wsa_> recovery, I2C core switcher patches, add tasks for Q1/2018, and largely
09:01 < wsa_> reviewed a huge SDHI patch series. Shimoda-san worked on various USB issues and
09:01 < wsa_> sent them upstream, investigated RuntimePM issues and also forwarded questions
09:01 < wsa_> about SPI slave and IIC. Simon posted an RFC for eMMC HS400 support.
09:01 < wsa_> B)
09:01 < wsa_> Geert will work on more MSIOF issues. Wolfram will work on R-Car I2C bus
09:01 < wsa_> recovery V2, test DTS switcher patches remotely, add. tasks for Q1,
09:01 < wsa_> per-SoC-freq-calculation for IIC and continue to review the huge SDHI patch
09:01 < wsa_> series. Shimoda-san continues to work on the RuntimePM and USB role swap
09:01 < wsa_> issues, as well as resubmitting phy-rcar-gen3-usb2 and learning about KVM &
09:01 < wsa_> USB. Simon continues to work on the HS400 issues and wants to enable SDR on
09:01 < wsa_> Porter and H3ULCB. Ulrich wants to pick up outstanding patch series (SCIF
09:01 < wsa_> receive margin, D3 I2C patches)
09:01 < wsa_> C)
09:01 < wsa_> Wolfram struggled a little with the tax office again. Simon needs to mine
09:01 < wsa_> the BSP for more ideas about drive strength and HS400 issues.
09:02 < wsa_> anything I missed? or questions or other kinds of additions?
09:03 < wsa_> not the case
09:04 < wsa_> shimoda: the customer team seems happy with the IIC patches I did so far?
09:05 < wsa_> about the add. tasks:
09:05 < horms> wsa_: seems good, sorry for missing the 1 hour cutoff
09:05 < shimoda> wsa_: i hope so, but the team now continue to work for updating the doc with hw guys
09:06 < wsa_> I asked Niklas who expressed interest in bigger MTU handling for EtherAVB (if multimedia doesn't need him 100%)
09:06 < shimoda> so, we have to wait until thier work
09:06 < wsa_> shimoda: I understand. So, we could say: so far, so good :)
09:07 < wsa_> horms: no problem, if there is 1 exception I can handle it ;)
09:07 < shimoda> wsa_: yes :)
09:07 < wsa_> I asked Ulrich who expressed interest in hrtimer support for HSCIF
09:08 < wsa_> I asked Simon to continue on HS400. Did you get that mail, Simon?
09:08 < wsa_> I planned to work on NAK & REP_START issues for IIC as one task
09:08 < horms> wsa_: sorry, no i missed it
09:08 < wsa_> and on fixing SDHI PM issues as another task
09:08 < horms> I see it now
09:09 < wsa_> horms: ah, good, just wanted to know if it gets through
09:09 < horms> wsa_: I do have time. I do agree upstreaming is the easy part. The hard part is making the feature work (reliably).
09:09 < wsa_> that's all I have done now so far regarding add. tasks
09:09 < wsa_> Any more requests from Renesas side?
09:10 < wsa_> Someone with some free time and desire to work on an IO task? :)
09:12 < geertu> wsa_: Do you see anything missing in core that you need for I/O?
09:12 < wsa_> horms: great that you have time. so we need to phrase the add. task accordingly (maybe not so much about upstreaming?)
09:13 < horms> The way I see things is that we have many issues relating to handling tuning.
09:13 < wsa_> geertu: nope
09:14 < horms> And its hard to work out which BSP changes - issued addresst there - are a) real, b) upsreamable and c) related to hs400
09:14 < horms> BTW, the BSP works fine :)
09:14 < wsa_> ok
09:14 < wsa_> so, it could be worse ;)
09:16 < wsa_> BTW, isn't there a request for the GETHER device? A new Gigabit ethernet controller only found on the V3H?
09:16 < horms> Yes, there is hope
09:16 < horms> Oh, really???
09:17 < horms> Neither an SH-ETH or EtherAVB variant?
09:17 < geertu> Haven't looked at the spec, but probably it's SH-ETH? The one on R-Mobile A1 also does gigabit
09:18 < wsa_> chapter 51 in the 0.80 docs
09:18 < wsa_> geertu: ad, didn't know that
09:18 < geertu> I guess Cogent will work on V3H?
09:18 < wsa_> ah
09:18 < geertu> I always found it strange the one on R-Car Gen2 is limited to 100M
09:18 < geertu> given Armadillo has 1G
09:18 < horms> Is it?
09:19 < geertu> 7757, 7734, and 7763 also have 1G
09:20 < wsa_> well, from a glimpse the regs look a bit different
09:20 < horms> The stratergy for ethernet is somewhat of a puzzle for me. My only conclusion is its not that important. But then there are whole new IP blocks coming out from time to time...
09:20 < Marex> horms: maybe it's a matter of size of the block in the silicon ?
09:20 < Marex> horms: insert block which fits ... you have these three options
09:20 < horms> Marex: likely
09:21 < wsa_> but well, yeah, it seems there is no request anyhow
09:22 < wsa_> so, no more topics from me
09:22 < shimoda> wsa_: sorry for the delayed, from my side, i don't have any request from my side about add. tasks
09:22 < wsa_> thanks, shimoda-san
09:23 < wsa_> i will forward the task descriptions then to Magnus, once I know if Niklas is available in Q1
09:24 < wsa_> what about the next meeting?
09:25 < geertu> in the middle of the Xmas holidays?
09:25 < wsa_> not a good option, me thinks
09:25 < geertu> Postpone by 1 week?
09:25 < geertu> 2 weeks?
09:26 < wsa_> is 4.1.18 realistic? or are ppl still on holiday then?
09:26 * geertu was cobfused for a split second, thinking about a kernel version
09:26 < wsa_> :D
09:26 < geertu> s/cobfused/confused/
09:27 < neg> It would work for me
09:27 < geertu> 2018-01-04 is fine for me
09:27 < pinchartl> fine with me as well
09:27 < horms> "
09:27 < uli___> same here
09:27 < wsa_> I can make 4.1.2018 but very likely not 11.1.2018
09:27 < shimoda> in renesas, we will be off at 4th Jan
09:27 < geertu> I just wanted to ask: "any Japanese holidays?" ;-)
09:28 < wsa_> hmmmm
09:28 < horms> 4th is probably not good in Japan
09:28 < morimoto`> Renesas side guys will have holidays untile 2018-1-8
09:29 < horms> morimoto`: in general Japan closes for the first week of the year, right?
09:29 < shimoda> geertu: i'm not sure but some people will start at 3rd Jan in Japan companies
09:29 < wsa_> 9.1.2018 (Tue) would work for me
09:29 < shimoda> s/3rd/4th/
09:30 < geertu> Fine for me, too
09:31 < morimoto`> horms: shimoda answered your question :)
09:31 < horms> :)
09:32 < wsa_> ok, let's sum it up for now: I am available on 9.1. If it is going to be 11.1. we will likely do the IO meeting part by mail.
09:32 < wsa_> shouldn't be a big deal since there won't be too much work over Xmas/New Year anyhow
09:32 < geertu> Indeed. Sounds fine to me.
09:33 < horms> Either is fine by me
09:33 < wsa_> and with that I'd hand over to Geert for the core meeting
|
