{"action":"created","issue":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/595","repository_url":"https://api.github.com/repos/raspberrypi/firmware","labels_url":"https://api.github.com/repos/raspberrypi/firmware/issues/595/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/firmware/issues/595/comments","events_url":"https://api.github.com/repos/raspberrypi/firmware/issues/595/events","html_url":"https://github.com/raspberrypi/firmware/issues/595","id":153504807,"number":595,"title":"Disabling dispmanx in the presence of vc4 driver","user":{"login":"anholt","id":3431811,"avatar_url":"https://avatars.githubusercontent.com/u/3431811?v=3","gravatar_id":"","url":"https://api.github.com/users/anholt","html_url":"https://github.com/anholt","followers_url":"https://api.github.com/users/anholt/followers","following_url":"https://api.github.com/users/anholt/following{/other_user}","gists_url":"https://api.github.com/users/anholt/gists{/gist_id}","starred_url":"https://api.github.com/users/anholt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anholt/subscriptions","organizations_url":"https://api.github.com/users/anholt/orgs","repos_url":"https://api.github.com/users/anholt/repos","events_url":"https://api.github.com/users/anholt/events{/privacy}","received_events_url":"https://api.github.com/users/anholt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-05-06T17:54:44Z","updated_at":"2016-05-10T13:21:08Z","closed_at":null,"body":"Working on DSI support, the current problem I think I'm facing is that VC is taking my DSI interrupts and clearing their status bits before ARM gets to see them.  The DSI interrupt isn't being masked because the firmware only disables interrupt handling for a few previously-known vc4 DT nodes.  Adding \"mask_gpu_interrupt1=0x1000\" means the board hangs at boot, presumably when it's trying to first turn on DSI.\r\n\r\nMeanwhile, we have users trying to use tvservice to control graphics and breaking graphics, and the undervoltage warning trashing display lists.  So, while the current interrupt-masking solution has served us well until now, I think we need a better solution to get vc4 ready to enable by default.\r\n\r\nIdeally, to me, we'd still have the firmware setting up graphics at boot, and then once vc4 loads but before it sets a mode, we'd send a property request asking that dispmanx disable everything it's doing and refuse further requests.  It would be nice if dispmanx could still leave the outputs running (since that means we can implement flicker-free boot eventually), but not required.\r\n\r\nDoes this seem feasible?\r\n"},"comment":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/comments/218154845","html_url":"https://github.com/raspberrypi/firmware/issues/595#issuecomment-218154845","issue_url":"https://api.github.com/repos/raspberrypi/firmware/issues/595","id":218154845,"user":{"login":"popcornmix","id":1053730,"avatar_url":"https://avatars.githubusercontent.com/u/1053730?v=3","gravatar_id":"","url":"https://api.github.com/users/popcornmix","html_url":"https://github.com/popcornmix","followers_url":"https://api.github.com/users/popcornmix/followers","following_url":"https://api.github.com/users/popcornmix/following{/other_user}","gists_url":"https://api.github.com/users/popcornmix/gists{/gist_id}","starred_url":"https://api.github.com/users/popcornmix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/popcornmix/subscriptions","organizations_url":"https://api.github.com/users/popcornmix/orgs","repos_url":"https://api.github.com/users/popcornmix/repos","events_url":"https://api.github.com/users/popcornmix/events{/privacy}","received_events_url":"https://api.github.com/users/popcornmix/received_events","type":"User","site_admin":false},"created_at":"2016-05-10T13:21:08Z","updated_at":"2016-05-10T13:21:08Z","body":"What about DSI? Do you want ``mask_gpu_interrupt1=0x1000`` to be added when we parse config.txt and the overlay? That should occur after DSI initialisation, but should stop firmware subsequently reacting to interrupts.\r\n\r\nHow do I use DSI with your driver? I have the new commits from your active PR in kernel."}}