Skip to content

VC4 backwards-compatible code changes #1213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 5, 2015

Conversation

anholt
Copy link
Contributor

@anholt anholt commented Dec 4, 2015

I've now submitted the 3D driver upstream: http://lists.freedesktop.org/archives/dri-devel/2015-December/095834.html

This is a merge to get downstream closer to upstream, but without requiring ABI or DT changes.

Remaining differences between upstream and downstream:

  • Upstream has MSAA support (requires updated Mesa packages, changes for MSAA haven't landed in master yet).
  • Upstream changed "hpd-gpio" to "hpd-gpios". It would be nice to sync that before our DT gets too settled.
  • Upstream is using generic PM domains instead of firmware calls from vc4. I still need to test GPU reset with the new code.
  • Upstream doesn't have the "wait for rendering to finish" out-of-memory fallback yet.

I'm currently working on landing the MSAA bits, and I'll try to get a branch together for rebuilding the .debs.

This can be parsed with vc4-gpu-tools tools for trying to figure out
what was going on.

Signed-off-by: Eric Anholt <[email protected]>
This gets almost everything matching, except for the MSAA support and
using generic PM domains.

Signed-off-by: Eric Anholt <[email protected]>
@popcornmix
Copy link
Collaborator

Builds and runs okay for me. @pelwell happy to merge?

pelwell added a commit that referenced this pull request Dec 5, 2015
VC4 backwards-compatible code changes
@pelwell pelwell merged commit a6ddf6b into raspberrypi:rpi-4.2.y Dec 5, 2015
@pelwell
Copy link
Contributor

pelwell commented Dec 5, 2015

I'm happy for you to change hpd-gpio to hpd-gpios whenever you want. Although it isn't really the done thing, our DT has been through several incompatible changes, but because the kernel is always packaged with the DT and overlays this hasn't been a problem. Just put the overlay change and any code change in the same commit.

popcornmix pushed a commit that referenced this pull request Jul 4, 2017
This reverts commit 88bb942.

It introduced a new CONFIG_DEBUG_ATOMIC_SLEEP warning in v4.12-rc1:

[ 7226.716713] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:238
[ 7226.716716] in_atomic(): 0, irqs_disabled(): 0, pid: 1708, name: bash
[ 7226.716722] CPU: 1 PID: 1708 Comm: bash Not tainted 4.12.0-rc6+ #1213
[ 7226.716724] Hardware name: Google Kevin (DT)
[ 7226.716726] Call trace:
[ 7226.716738] [<ffffff8008089928>] dump_backtrace+0x0/0x24c
[ 7226.716743] [<ffffff8008089b94>] show_stack+0x20/0x28
[ 7226.716749] [<ffffff8008371370>] dump_stack+0x90/0xb0
[ 7226.716755] [<ffffff80080cd2a0>] ___might_sleep+0x10c/0x124
[ 7226.716760] [<ffffff80080cd330>] __might_sleep+0x78/0x88
[ 7226.716765] [<ffffff800879e210>] mutex_lock+0x2c/0x64
[ 7226.716771] [<ffffff80083ad678>] rockchip_irq_bus_lock+0x30/0x3c
[ 7226.716777] [<ffffff80080f6d40>] __irq_get_desc_lock+0x78/0x98
[ 7226.716782] [<ffffff80080f7e6c>] irq_set_irq_wake+0x44/0x12c
[ 7226.716787] [<ffffff8008486e18>] dev_pm_arm_wake_irq+0x4c/0x58
[ 7226.716792] [<ffffff800848b80c>] device_wakeup_arm_wake_irqs+0x3c/0x58
[ 7226.716796] [<ffffff80084896fc>] dpm_suspend_noirq+0xf8/0x3a0
[ 7226.716800] [<ffffff80080f1384>] suspend_devices_and_enter+0x1a4/0x9a8
[ 7226.716803] [<ffffff80080f21ec>] pm_suspend+0x664/0x6a4
[ 7226.716807] [<ffffff80080f04d8>] state_store+0xd4/0xf8
...

It was reported on -rc1, and it's still not fixed in -rc6, so it should
just be reverted.

Cc: John Keeping <[email protected]>
Signed-off-by: Brian Norris <[email protected]>
Reviewed-by: Heiko Stuebner <[email protected]>
Signed-off-by: Linus Walleij <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants