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
110
111
112
113
114
115
116
117
118
119
120
121
|
09:03 < wsa_> so, let's start the IO meeting and be welcome to that
09:04 < wsa_> I prepared a summary for the status-updates:
09:04 < wsa_> A)
09:04 < wsa_> Geert:
09:04 < wsa_> * Working on MSIOF (GPIO/SS1/SS2 slave select),
09:04 < wsa_> * Ethernet PHY reset v4 (needed for Salvator-XS resume).
09:04 < wsa_> Shimoda:
09:04 < wsa_> * Got feedback from HW team about HS-USB and investigate the driver how to implement it.
09:04 < wsa_> * Investigate runtime PM issue on R-Car Gen3 + USB host controllers.
09:04 < wsa_> * Submitted the following patch(es):
09:04 < wsa_> * Fix the USB3.0 peripheral driver that has just 5 pipes.
09:04 < wsa_> * Merged the "Add PWM dt-binding for r8a77995." into v4.15-rc1.
09:04 < wsa_> Simon:
09:04 < wsa_> * Got some patches accepted
09:04 < wsa_> * worked on HS400 support for SDHI
09:04 < wsa_> Wolfram:
09:04 < wsa_> * cured some kind of indigestion, back to full strength now
09:04 < wsa_> * implemented various IIC fixes requested by Shimoda-san/
09:04 < wsa_> customer team
09:04 < wsa_> * improved I2C core bus recovery and implemented recovery for
09:04 < wsa_> i2c-rcar on top of that
09:04 < wsa_> * discussed SDHI naming scheme with Yamada-san
09:04 < wsa_> * reviewed various SDHI patches, mainly from Yamada-san
09:04 < wsa_> * quite some stuff got merged after rc1 :)
09:04 < wsa_> (IIC fixes, mmc_delay refactoring, I2C DMA series)
09:04 < wsa_> * had a look at Uli's D3 patches, but usually Geert is
09:04 < wsa_> faster than me ;)
09:04 < wsa_> Uli:
09:04 < wsa_> * Sent various Draak integration patches (SYS-DMAC, I2C, SDHI/eMMC, CAN)
09:04 < wsa_> * resent "R-Car D3 (r8a77995) SDHI (eMMC) integration"
09:04 < wsa_> B)
09:04 < wsa_> Geert:
09:04 < wsa_> * Continue MSIOF (GPIO/SS1/SS2 slave select, ...),
09:04 < wsa_> * Post Ethernet PHY reset v4 after opening of net-next merge window.
09:04 < wsa_> Shimoda:
09:04 < wsa_> * Submit renesas_usbhs driver paches about dequeue handling.
09:04 < wsa_> * Continue to investigate the runtime PM issue.
09:04 < wsa_> * Investigate USB3.0 role swap issue.
09:04 < wsa_> Simon:
09:04 < wsa_> * Continue work on enabling HS400
09:04 < wsa_> * Try to enable SDR-50 and SRR-104 on porter (patch posted, needs testing)
09:04 < wsa_> * Upport BSP patch
09:04 < wsa_> ed8730231a98 arm64: dts: r8a7795-es1-h3ulcb: Enable UHS-I SDR-104
09:04 < wsa_> Wolfram:
09:04 < wsa_> * write elinux test page for i2c-rcar bus recovery
09:04 < wsa_> * upstream I2C core switcher DTS changes
09:04 < wsa_> * prepare add. tasks for Q1/2018
09:05 < wsa_> Uli:
09:05 < wsa_> * Send new revision of Draak I2C series.
09:05 < wsa_> C)
09:05 < wsa_> none!
09:05 < wsa_> The notes/questions I have:
09:06 < wsa_> horms: the SDR104 thing on porter might not working because the issue we have seen on alt is not fixed yet
09:07 < wsa_> I hope I can have a look after finishing the I2C bus recovery add. task
09:07 < horms> ahh. so I did test it. and it did not work. but I assumed I was doing something wrong and planned to come back to it.
09:07 < horms> I also noticed brokenness on Alt yesterday when testing something else (SMP)
09:07 < wsa_> uh, nice to know
09:07 < geertu> wsa_: So your assumption is that it's not SoC-specific, but board-specific?
09:08 < wsa_> geertu: it might even be a driver thing
09:08 < wsa_> neg found a revert which made it work for him again on Koelsch
09:08 < wsa_> have to verify this on alt, though
09:09 < neg> I think the sum of my findings are in '[RFC] mmc: tmio: fix tuning for stubborn cards'
09:10 < wsa_> horms: in general, how is HS400 coming along? did hell break loose, or is it not as bad? ;)
09:10 < horms> Its not going great
09:10 < horms> I backported a bunch of patches.
09:10 < wsa_> geertu: and well, yes, it is card specific
09:10 < horms> M3-W seems to not detect devices any more
09:11 < horms> H3 ES1.0 detects the device but it is slower
09:11 < horms> I need to make sure I have the latest from uptream as my base, in particular drive strength featues in the driver and DT
09:11 < Marex> horms: HS400 had issues in uboot too, just FYI, I didnt manage to tune it
09:12 < horms> My plan was to try to do some triage and report to the ML
09:12 < geertu> Non-matched PCB traces?
09:12 < wsa_> drive_strength is in 4.16-rc1
09:13 < horms> s/15/16/ ?
09:13 < wsa_> 15
09:13 < wsa_> heh, sorry
09:13 < horms> I think I had the driver portion in my most recent branch, as I based it on mmc/next
09:13 < wsa_> does the BSP work?
09:13 < horms> But I also think I was missing the DT bit which is in my devel branch (I didn't realise that at the time)
09:14 < horms> That is a good question. My assumption is yes. I will test.
09:14 < wsa_> If so, it would rule out HW problems to a high degree
09:14 < horms> good point
09:15 < wsa_> so, good luck with that!
09:16 < wsa_> shimoda: could you kindly provide me with a diff-style update for the io-todo file? I am not sure I can map the patch descriptions from your patches to the task titles 100% correctly :)
09:17 < horms> Thanks
09:17 < shimoda> wsa_: sure. I will send it by email later
09:17 < wsa_> Thank you!
09:18 < wsa_> So, the final not from me is that I'd like to start looking at add tasks for Q1/2018 slowly.
09:19 < wsa_> Maybe we can start talking about it in 2 weeks during an all-groups-meeting?
09:19 < wsa_> I will contact you individually for tasks I might have at hand to negotiate if there is interest
09:20 < wsa_> And please contact me if you see IO related tasks for you
09:21 < horms> Two from me, if there is time.
09:21 < geertu> Sounds good to me
09:21 < wsa_> horms: nice, can you mail them to me?
09:22 < horms> Not tasks, questsions for now :)
09:22 < wsa_> :D
09:22 < wsa_> then, please
09:22 < wsa_> fire away now
09:22 < horms> 1. If you have any small tasks that Kaneko-san might handle in the immediate future feel free to ask
09:23 < horms> 2. Does v4.15-rc1 work on Salvator-X/H3 ES1.0 or is it just me?
09:23 < horms> -- fin --
09:23 < geertu> horms: Last renesas-drivers is supposed to work on that
09:24 < wsa_> horms: Thanks! I'll check if I have something for Kaneko-san...
09:24 < horms> geertu: ok, but v4.15-rc1 is broken?
09:24 < geertu> horms: Not AFAIK
09:24 < horms> wsa_: thanks. I've been mining the BSP but a lot of what was on my list is now upstream
09:24 < horms> geertu: ok, I'll assume it was just me
09:25 < horms> that was all, thanks!
09:25 < neg> horms: quick question, what is the upstream plan (if any) for 'arm64: dts: r8a7795: Add OPPs table for cpu devices' et. al. ?
09:25 < horms> ok, that is a good question
09:26 < wsa_> horms: I'll check the I2C bus recovery on ES1.0, too, later this week. This is based on i2c/for-next which is based on v4.15-rc1. I'll let you know
09:26 < shimoda> horms: about small tasks, i have some items that issues in v4.14 but bsp patches can resolve it. it is related to suspend to ram
09:26 < geertu> horms: renesas-drivers with renesas_defconfig boots on Salvator-X/H3 ES1.0
09:27 < horms> possibly it can go upstream if I clean it up a bit. would that help you? the bigger question is CPUFreq. THere I seem to have some problem getting the Z clk patches working. The fixed /2 divider seems to be a problem for me. I wonder if I could get some advice on how to fix it. Or at least what the propper behaviour to be observied in /sys is. My previous effort seemed to go in the wrong direction :(
09:27 < horms> shimoda: thanks, they sound like great candidates. Perhaps we can discuss on the periperi ML?
09:27 < geertu> horms: With the fix from the BSP, Z and Z2 are correct for me on H3 ES2.0 and M3-W
09:27 < wsa_> okay, we entered the core realm already, me thinks
09:27 < horms> Or here, a bit later, if you like
09:27 * wsa_ throws the mic to Geert
09:28 * geertu misses
09:28 < wsa_> thank you all for the IO meeting!
|
