summaryrefslogtreecommitdiff
path: root/projects/linux/mm/bsp41x_vsp-Add-V3U-support.yaml
diff options
context:
space:
mode:
authorWolfram Sang <wsa+renesas@sang-engineering.com>2022-03-10 09:45:07 +0100
committerWolfram Sang <wsa+renesas@sang-engineering.com>2022-03-10 09:45:07 +0100
commit11345028ca7a5cd71da8f8ebbcb4e6fd9b1a741f (patch)
treeaea0b87bcf45a370fbf6bdb8dea2a7065c55240e /projects/linux/mm/bsp41x_vsp-Add-V3U-support.yaml
parent2b383e1e933b74b5aa00e2651ab8e8b50aa0821f (diff)
wiki: Hardware: H3 ULCB and KingFisher moved to Wolfram
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Diffstat (limited to 'projects/linux/mm/bsp41x_vsp-Add-V3U-support.yaml')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-28 12:22:14 +0000
id='n117' href='#n117'>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 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 
Core-chat-meeting-2016-04-12

10:10 < geertu> Agenda:
10:10 < geertu> 1. Upcoming Gen3 development for the Core group,
10:10 < geertu> 2. Firmware upgrade and consequences (hotplug, DDR, ...)
10:10 < geertu> 3. Does it make sense to have "renesas,cpg = <&cpg_clocks>;" in the SYSC device node? Or do we want to avoid that at all cost?
10:10 < geertu> 4. Status check for tasks from last meeting - what is remaining?
10:10 < geertu> horms: So that would mostly by Topics 1 and 2?
10:10 < geertu> s/1 and 2/2 and 3/?
10:10 < geertu> Topic 2. Firmware upgrade and consequences (hotplug, DDR, ...)
10:10 < geertu> horms: You've already tried v2.7.0?
10:10 < horms> geertu: yes, i lightly tested it
10:11 < horms> hotplug appears to work as per my email
10:11 < khiemnguyen> For topic 2, what is current version that all are using ? Yocto v2.3.0 ?
10:11 < horms> so that seems positive
10:11 < geertu> v2.5.0, IIRC
10:11 < geertu> Any known regressions?
10:11 < khiemnguyen> yes, hotplug has been able to work from Yocto v2.4.0
10:11 < horms> n.b. firmware version != yocto version
10:12 < horms> I think geert was referring to the former
10:12 < geertu> khiemnguyen: Only the first time. After hot-unplug, hot-plug no longer works in v2.5.0
10:12 < horms> _I_ am not aware of any regressions
10:12 < khiemnguyen> you tried with CPU0, right ?
10:12 < horms> let me check
10:12 < khiemnguyen> CPU0 has a limitation for CPU Hotplug, since the secure side will run some secure services in CPU0 all the time.
10:13 < khiemnguyen> Please try CPU Hotplug with CPU1/2/3 only.
10:13 < horms> I only tried CPU1
10:13 < horms> What happens on CPU0?
10:14 < khiemnguyen> the secure side will run some secure services in CPU0 all the time.
10:14 < khiemnguyen> CPU0 should not be hotplug.
10:14 < horms> ok
10:15 < horms> so if it is unplugged we might see some problems? like undefinded behaviour?
10:15 < khiemnguyen> so if it is unplugged we might see some problems? like undefinded behaviour?  --> yes.
10:16 < geertu> Hmm...