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
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
Core-chat-meeting-2017-11-30
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!
09:28 < shimoda> horms: i got it. i'll send this topic to the ML later
09:28 * geertu picks it up from the floor
09:28 < horms> geertu: ok. but are they correct when you change CPU frequency?
09:28 < horms> I can check again but it seemed kinda bogus to me
09:28 < geertu> horms: Haven't checked that.
09:28 < horms> geertu: ok. How about I collect some results and we can discuss properly
09:28 < geertu> There's an /2 or *2 missing
09:28 < horms> Yes, I understand that
09:29 < wsa_> geertu: guess you were surprised because it was 2 minutes early ;)
09:29 < horms> what I'm confused about is what the correct values to be read out of /sys are
09:29 < horms> but I can collect data, using the BSP fixes
09:29 < horms> and we can take it from there
09:29 < geertu> It should be 1.5 GHz after boot
09:29 < horms> what should be 1.5 GHz after boot?
09:29 < neg> horms: my interest is that it's blocking the thermal cooling patches, no biggi but on my task list :-)
09:29 < geertu> z clock
09:29 < horms> ok
09:29 < horms> and the cpu frequencies too, I suppose
09:30 < geertu> I always look at /sys/.../clk_summary differences after every boot
09:30 < horms> what should z clock be after the CPU clock is changed, say to 1.0GHz?
09:30 < geertu> 1.0 GHz
09:30 < geertu> Z clock == the CPU clock
09:30 < horms> ok
09:30 < horms> I assume that is ~=
09:30 < geertu> v4.15-rc1 also boots on Salvator-X/H3 ES1.0
09:31 < horms> ok, it must have been me. did you use renesas_defconfig?
09:31 < geertu> Any chance Kaneko-san had the "move pmu nodes outside /soc" applied, without the interrupt-parent?
09:31 < geertu> Then it will hang, without output if not using earlycon
09:31 < geertu> For renesas-drivers I used renesas_defconfig
09:32 < geertu> After checking out v4.15-rc1, I ran oldconfig
09:32 < horms> It was me and it was without that patch
09:32 < horms> ok, thanks
09:32 < geertu> OK, so Welcome to today's Core Group Meeting!
09:32 < geertu> Although we've been in core territory for a few minutes
09:33 < neg> wsa_: thanks for IO meeting :-)
09:33 < geertu> Agenda:
09:33 < geertu> 1. Status updates
09:33 < geertu> 2. Discussion Topics
09:33 < geertu> I'll reply the status updates, FTR
09:34 < geertu> A) What have I done since last time
09:34 < geertu> Geert:
09:34 < geertu> - Sent v2 of genpd active_wakeup fixes (incl. interrupt routing),
09:34 < geertu> documented at
09:34 < geertu> https://elinux.org/R-Car/Tests:System-Suspend-and-Wake-Up
09:34 < geertu> - Reworked sh-sci Kconfig,
09:34 < geertu> - Fixed DT overlays for v4.14 and v4.15-rc1,
09:34 < geertu> - Resent patches after release of v4.15-rc1.
09:34 < geertu> Marek:
09:34 < geertu> - Massive cleanup of the Gen3 in U-Boot:
09:34 < geertu> - Removed most of the CONFIG_R8A779x checks, instead use PRR CPU ID
09:34 < geertu> - Wrote PRR syscon driver
09:34 < geertu> - Unified CONFIG_R8A779x as CONFIG_RCAR_GEN3 where applicable
09:34 < geertu> - Removed a lot of hard-coded config options and replaced them with
09:34 < geertu> fetching the configuration from DT
09:34 < geertu> - Removed _a_lot_ of unused macros
09:34 < geertu> - Implemented DT/DM capable IIC driver for the DVFS I2C bus
09:34 < geertu> - Fixed up minor bugs on M3/H3 ULCB
09:34 < geertu> - Fixed up the CPLD driver on ULCB so that reset actually works
09:34 < geertu> - Submitted all the stuff upstream [1]...[7]
09:34 < geertu> [1] http://patchwork.ozlabs.org/project/uboot/list/?series=15669
09:34 < geertu> [2] http://patchwork.ozlabs.org/patch/842402/
09:34 < geertu> [3] http://patchwork.ozlabs.org/patch/842403/
09:34 < geertu> [4] http://patchwork.ozlabs.org/patch/842404/
09:34 < geertu> [5] http://patchwork.ozlabs.org/patch/842405/
09:34 < geertu> [6] http://patchwork.ozlabs.org/patch/842406/
09:34 < geertu> [7] http://patchwork.ozlabs.org/patch/842407/
09:34 < geertu> Niklas:
09:34 < geertu> - Hooked up and verified V3M functionality.
09:34 < geertu> - Had first look at 'Add support for more than 32-bits IOVA space', not much
09:34 < geertu> progress. Please see 'Re: [PATCH/RFC] iommu/ipmmu-vmsa: Initial R-Car Gen3
09:34 < geertu> VA64 mode support' from 2017-11-13.
09:34 < geertu> Shimoda:
09:34 < geertu> - Test M3-N's IPMMU (stage-2 format).
09:34 < geertu> - Investigate M3-N IPMMU issue.
09:34 < geertu> Simon:
09:34 < geertu> - Posted, now accepted
09:34 < geertu> IPMMU integration patches
09:34 < geertu> pinctrl upports from BSP
09:34 < geertu> - Posted, changes requested:
09:34 < geertu> [PATCH v3] arm64: dts: renesas: r8a7795: Move nodes which have no reg
09:34 < geertu> - Posted, under review
09:34 < geertu> IPMMU bindings and driver patches
09:34 < geertu> Ulrich:
09:34 < geertu> - Sent various Draak integration patches (SYS-DMAC, I2C, SDHI/eMMC, CAN).
09:34 [Users #periperi]
09:34 [@pinchartl] [ horms ] [ kbingham[m]] [ mturquette] [ uli___]
09:34 [ dammsan ] [ jmondi ] [ Marex ] [ neg ] [ wsa_ ]
09:34 [ geertu ] [ kbingham] [ marex-cloud] [ shimoda ]
09:34 -!- Irssi: #periperi: Total of 14 nicks [1 ops, 0 halfops, 0 voices, 13 normal]
09:35 < geertu> B) What I plan to do till next time
09:35 < geertu> Geert:
09:35 < geertu> - Sent sh-sci Kconfig rework,
09:35 < geertu> - Initial support for Salvator-X with R-Car M3-N?
09:35 -!- wsa_ [~wsa@p54B33377.dip0.t-ipconnect.de] has quit [Quit: ...]
09:35 < geertu> Marek:
09:35 < geertu> - Continue with my quest to make U-Boot on Gen3 easy to use and port
09:35 < geertu> to new boards
09:35 < geertu> - Again push for HS200/SDR104 MMC core changes to get into U-Boot
09:35 < geertu> - Fix up U-Boot for V3M (and D3 when it become available to me)
09:35 < geertu> Niklas:
09:35 < geertu> - If free time keep banging at the 'Add support for more than 32-bits IOVA
09:35 < geertu> space', most likely not.
09:35 < geertu> Shimoda:
09:35 < geertu> - Add usb3.0 phy device node for r8a779[56].dtsi.
09:35 < geertu> Simon:
09:35 < geertu> - Continue fixing nodes which have no reg
09:35 < geertu> - Follow up on IPMMU bindings patches
09:35 < geertu> - Address review of CPUFreq/Z,Z2 Clock patches
09:35 < geertu> - Upport BSP patches
09:35 < geertu> 55f32e9ad018 clk: renesas: r8a7795: Change the RINT and OSC clocks frequency with reference to MD{13,14}
09:35 < geertu> 575998792004 clk: renesas: r8a7796: Change the RINT and OSC clocks frequency with reference to MD{13,14}
09:35 < geertu> fba4b288aba2 clk: renesas: rcar-gen3: Delete the RCKCR register definition
09:36 < geertu> C) Problems I have currently
09:36 < geertu> Geert:
09:36 < geertu> - Missing V3MSK docs hampering review.
09:36 < geertu> Marek:
09:36 < geertu> - The SD/MMC maintainer in U-Boot is slow
09:36 < geertu> EOT
09:36 < geertu> I don't think we can fix the second problem here?
09:37 < geertu> Anything I missed?
09:37 < geertu> I didn't receive reports fom
09:37 < geertu> jmondi: ?
09:37 < geertu> pinchartl: ?
09:37 < geertu> dammsan: ?
09:38 < jmondi> geertu: no core work for me!
09:38 < geertu> Morimoto-san is excused
09:38 < geertu> jmondi: Thanks for chiming in!
09:38 < jmondi> geertu: yeah, sorry, I should have told in advance
09:40 < geertu> Is V3MSK handled by a different business unit?
09:43 < shimoda> geertu: i don't know about V3MSK. oh, Cogent is submiting patches. So, I should ask V3M key person later
09:44 < geertu> shimoda: OK, thank you
09:44 < geertu> 2. Discussion Topics
09:44 < geertu> Seems core is quiet and going steady.
09:45 < geertu> Anything you want to discuss?
09:45 < Marex> geertu: I am suffering with RPC SPI on V3M, but I think I can manage somehow
09:46 < geertu> Marex: Good (the "manage" part ;-)
09:47 < geertu> I guess we will start thinking about core additional tasks for Q1/2018 soon, just like for I/O
09:51 < geertu> If there's nothing more to discuss, let's conclude the meeting.
09:51 < geertu> Thanks for joining, and have a nice continued day!
|
