summaryrefslogtreecommitdiff
path: root/bsd-core/mach64_drv.h
diff options
context:
space:
mode:
authorEric Anholt <eric@anholt.net>2008-08-08 13:13:46 -0700
committerEric Anholt <eric@anholt.net>2008-08-08 13:58:29 -0700
commit46e9274e8538e5b0517f611dca99dde611f4e95d (patch)
treebd2dac93efeb25aa62d08ea01cd95317ed3d116a /bsd-core/mach64_drv.h
parent5968e061db90451b19c3948bbd91c6d5ac9af941 (diff)
Replace the check_aperture API with one we can make thread-safe.
While the bufmgr isn't thread-safe at the moment, we need it to be for shared objects between contexts.
Diffstat (limited to 'bsd-core/mach64_drv.h')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-18 10:19:25 +0000
9' href='#n99'>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 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 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 
Multimedia-chat-meeting-2016-05-25

<pinchartl> hello Morimoto-san
<morimoto> Hi 
<morimoto> sorry for my late
<pinchartl> we've just started
<pinchartl> no worries, you're excused
<pinchartl> I've posted the topics for the day
<pinchartl> Topic 1. Status check for the multimedia tasks
<pinchartl> Topic 2. Additional '50%' tasks
<pinchartl> Topic 3. New upstream DRM/KMS rules
<pinchartl> Topic 4. Next meeting
<pinchartl> would anyone like to add another topic ?  [17:02]
<morimoto> I added Renesas request to peripelist
<dammsan> hi guys, sorry about the delay
<morimoto> (it was already requested by email to each member, but not listed)
<pinchartl> in multimedia/request ?  [17:03]
<morimoto> Yes
<pinchartl> (kbingham: for your information, the lists of pending and
	    requested tasks are maintained in text format in a git tree called
	    peripelist)  [17:04]
<kbingham> pinchartl: I see :)
<pinchartl> I have a question about that, let's add it as a topic  [17:05]
<pinchartl> Topic 4. Renesas requests
<morimoto> thanks  [17:06]
<pinchartl> let's get started with the status, and let's try to keep it short
<morimoto> :)
<pinchartl> in alphabetical order  [17:07]
<pinchartl> FDP,v4.8,plan,laurent,Develop and upstream driver
<pinchartl> (which is handled by Kieran, otherwise I wouldn't be first in
	    alphabetical order)
<pinchartl> kbingham: what's the status ?  [17:08]
<kbingham> FDP1: M2M driver can handle frames, and support MPLANE/MPIX
	   api. Now working with getting the hardware to do
	   'something'. IPBlock is powered up, (using RuntimePM) and
	   interrupts are firing. Not currently getting 'successful' FrameEnd
	   status yet though.
<kbingham> Switched to using OPMODE_INTERRUPT with a VPERIOD setting, and that
	   fires regular VSyncs
<pinchartl> do you have ideas regarding what to explore or are you getting
	    blocked ?  [17:09]
<kbingham> Starting to feel blocked. I've gone through most of the register
	   settings, and the programming sequence and I'm running out of
	   ideas. My next plan is to try moving away from Progressive mode and
	   try de-int mode to see if there is a difference there but I fear
	   that is complicating things rather than simplifying. The only other
	   thing I have thought needs checking is the FCP  [17:10]
<pinchartl> have you linked the FDP to the FCP in DT ?  [17:11]
<kbingham> No!  [17:12]
<kbingham> That sounds like a step I've missed :)
<pinchartl> and do you call rcar_fcp_enable() and rcar_fcp_disabled() in your
	    driver ?
<kbingham> Ok - I'm unblocked :)
<pinchartl> at least temporarily :-)
<pinchartl> the FCP driver isn't upstream yet
<pinchartl> you need to get it from my git tree at
	    git://linuxtv.org/pinchartl/media.git  [17:13]
<kbingham> I do have a pending action to confirm the CPG clock parents
	   though. morimoto - are you able to look into that for me?
<pinchartl> branches drm/next/dt and vsp1/next
<kbingham> pinchartl: Ok - thanks. I'll get on that  next.
<morimoto> kbingham: can you send question email to me or periperil ML ?
								        [17:14]
<morimoto> kbingham: I can send it to HW / datasheet guys
<kbingham> morimoto: Sure. I'll send a dedicated mail. thanks :)
<morimoto> kbingham: np
<pinchartl> next, Magnus  [17:15]
<pinchartl> VIN,?,plan,magnus,IPMMU integration on Gen2
<pinchartl> VIN,?,plan,magnus,IPMMU integration on Gen3
<pinchartl> VIN,?,plan,magnus,IPMMU support on Gen2
<pinchartl> VIN,?,plan,magnus,IPMMU support on Gen3
<pinchartl> no progress on that I assume ?
<dammsan> nothing done yet, but i intend to try Gen3 early next month
<dammsan> with VIN in mean
<pinchartl> but not with the IPMMU, right ?  [17:16]
<dammsan> s/in/i/g
<dammsan> test with the IPMMU
<dammsan> just to figure out what is needed
<pinchartl> so we're not blocked by the IPMMU hardware bug anymore ?
<morimoto> kbingham: for your information: I asked to BSP team about FDP
	   sample code / test code now. I'm not sure it exists or not. please
	   wait :)
<dammsan> it is probably flakey on H3
<dammsan> but worth looking into to see what our limitations are  [17:17]
<dammsan> M3 may work better
<kbingham> morimoto: Thanks. Will be useful reference if it exists.
<dammsan> same situation as DU
<pinchartl> morimoto: thank you !
<pinchartl> morimoto: there's a 'fdpm-driver.tar.bz2' archive mentioned in the
	    yocto recipes, but that file is nowhere to be found  [17:18]
<pinchartl> so I assume code exists
<pinchartl> dammsan: thanks
<dammsan> np
<pinchartl> next, morimoto
<pinchartl> RSND,2016-06-30,plan,morimoto,DT bindings for HDMI sound
<pinchartl> RSND,2016-06-30,plan,morimoto,dw-hdmi-ahb-audio prototype on Gen3
<pinchartl> RSND,2016-06-30,plan,morimoto,HDMI SSI prototype on Gen3
<pinchartl> RSND,2016-06-30,plan,morimoto,HDMI sound Upstream support without
	    hotplug on Gen2
<pinchartl> RSND,2016-09-30,plan,morimoto,Hotplug support upstream on Gen3
<morimoto> graph base HDMI sound needs hack.  [17:19]
<morimoto> I posted its 1st step patches to ALSA and Renesas ML
<morimoto> It is under reviewing now
<morimoto> And now, I'm hacking of prototype of graph base sound card
<morimoto> not yet finished.
<morimoto> over  [17:20]
<dammsan> (and i bothered morimoto-san by asking about HDMI-in audio-input)
<pinchartl> as you've posted patches, which of the tasks should now be
	    'public'  [17:21]
<morimoto> I'm bothering it, yes
<morimoto> well...
<morimoto> RSND,2016-06-30,plan,morimoto,DT bindings for HDMI sound
<morimoto> but, 30% for it
<morimoto> 30% of it  [17:22]
<pinchartl> I wonder how to report the 30% in the tasks list :-)
<pinchartl> should I leave it as 'plan' for now until we reach 50% ?  [17:23]
<morimoto> can you separate it into more small tasks ?
<morimoto> split ? separate ?
<pinchartl> sure  [17:24]
<pinchartl> how would you like me to split it ?
<morimoto> 1. clean up simle-card  [17:25]
<morimoto> 2. create simple-card core
<morimoto> 3. share simple-card core with DPCM
<morimoto> 4. share simple-card core with graph
<morimoto> 5. use graph simple-card on ASoC
<morimoto> 6. use graph simple-card on Gen2
<morimoto> 7. use graph simple-card on Gen3
<morimoto> 
<morimoto> Maybe these are enough
<morimoto> 1, 2, 3 are posted
<morimoto> I mean public
<pinchartl> that's very fine-grained. do we really need to go to that level of
	    details in the tasks list, or can I just list that in the meeting
	    report ?  [17:27]
<morimoto> OK, please wait
<morimoto> I will clean up again
<pinchartl> thanks  [17:28]
<pinchartl> I'll include that in the report anyway
<pinchartl> I'll move on to Niklas' tasks in the meantime
<pinchartl> ADV7482,v4.7,plan,niklas,Prototype on Gen3
<pinchartl> ADV7482,v4.9,plan,niklas,Gen3 support upstream
<pinchartl> ADV7482,v4.9,plan,niklas,Interlace support upstream
<pinchartl> VIN,v4.7,plan,niklas,CSI2 prototype (Gen3)  [17:29]
<pinchartl> VIN,v4.8,plan,niklas,Gen3 support
<pinchartl> VIN,v4.8,plan,niklas,Scaler support (on Gen3)
<pinchartl> VIN,v4.8,public,niklas,New VIN driver without soc-camera (tested
	    on Gen2)
<pinchartl> VIN,v4.9,plan,niklas,CSI2 interlace support upstream (Gen3)
<pinchartl> VIN,v4.9,plan,niklas,CSI2 support upstream (Gen3)
<pinchartl> VIN,v4.9,plan,niklas,Gen3 support upstream (without CSI-2)
<neg> I will post the Gen3 VIN patches today
<pinchartl> including CSI ?  [17:30]
<neg> yes it will include the CSI2 and ADV7482 prototypes from BSP with some
      small fixes ontop
<pinchartl> so that covers
<pinchartl> - ADV7482,v4.7,plan,niklas,Prototype on Gen3
<pinchartl> - VIN,v4.7,plan,niklas,CSI2 prototype (Gen3)
<pinchartl> - VIN,v4.8,plan,niklas,Gen3 support  [17:31]
<pinchartl> right ?
<neg> yes,  but I will not include the CSI2 and ADV in the patch sereis but
      make them avaliable in a topic branch for testing
<neg> so I don't think they should be marked public
<pinchartl> for prototype patches that's fine, and I think it's enough to
	    consider them as public  [17:32]
<neg> OK
<pinchartl> are the Gen3 support patches in a good enough shape to be reviewed
	    ?
<pinchartl> or are they prototype code ?
<neg> yes I hope they are ready for review, they use s_input for input