Age | Commit message (Collapse) | Author |
|
|
|
wifi: ath11k: remove extra warning message, move to debug
See merge request jupiter/linux-integration!30
|
|
This reverts commit a4904c47fcd7fc9152b6b04409feac1130e2033d.
This results in some USB devices to fail to enumerate. Revert pending
further investigation.
|
|
|
|
Add 2s delay before enabling DP link for dock
See merge request jupiter/linux-integration!31
|
|
|
|
|
|
|
|
Jupiter platform doesn't support s2idle - system appears to
sleep and never wakeup again. So, disable it based on DMI
checking for platforms named "Valve Jupiter".
Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
(cherry picked from commit 3956de585667cfd9f91a3ee8af34f6c0d44f4381)
|
|
|
|
MAX98388 resume from suspend fix
See merge request jupiter/linux-integration!29
|
|
from S3.
The issue was that when we flush the regmap to the amp on resume, we were also flushing a value of 1 to the SW_RESET pin.
Theoretically, this is fixed by marking the SW_RESET register volatile. However, we did not observe a fix after marking the register volatile, so we opted for a more complete fix of ensuring SW_RESET is zero in our regmap after we have waited for the reset loop to be complete.
|
|
Brings in galileo support
|
|
|
|
Galilypad: Walking back the churn on nau8821 to match 6.1.52-valve3.
For jupiter-only drivers we don't want to pull in new upstream work as
part of the galileo merge currently, so we'll work on reconciling this
on our next proper rebase.
This reverts commit 0965dc61324818deae73773f76a9b1c729750e5d.
|
|
Galilypad: Walking back the churn on nau8821 to match 6.1.52-valve3.
For jupiter-only drivers we don't want to pull in new upstream work as
part of the galileo merge currently, so we'll work on reconciling this
on our next proper rebase.
This reverts commit 75aea88af91e763d3d890ed6da2f5c348f901815.
|
|
Galilypad: Walking back the churn on nau8821 to match 6.1.52-valve3.
For jupiter-only drivers we don't want to pull in new upstream work as
part of the galileo merge currently, so we'll work on reconciling this
on our next proper rebase.
This reverts commit 41197b693b30eeefcf0e4af1fc67991f6416f0de.
|
|
Galilypad: The following commits pulled in a new version of this that
omitted the config needed for jupiter boards with the cs35l41 codec.
This restores the missing sections. This should be folded into the
final upstreaming of the galileo patchset
08507ab4a662 ASoC: amd: Add acpi machine id's for vangogh platform
7c7ae3a5eecd Revert "ASoC: SOF: amd: Add acpi machine id's for vangogh
platform"
|
|
Galilypad: Dropped as part of the patch series for galileo, but
jupiter actually wants this so restoring for the merge
This reverts commit 6c90260c6f7ef7b3e72dcc34a0a6733829d21f91.
|
|
Signed-off-by: Venkata Prasad Potturu <venkataprasad.potturu@amd.com>
(cherry picked from commit 50f20ef9bcf6fdf6e6cc64a031be26fb9cb54849)
|
|
Galilypad: Reverting max98388 work on the amd (not sof) driver. May
be useful to pull in in future, but not needed for SOF galileo sound
to work.
This reverts commit 087eb9a6e8ae93f15d8111bdeb0091689ba5dfae.
|
|
Galilypad: Walking back the churn on nau8821 to match 6.1.52-valve3.
For jupiter-only drivers we don't want to pull in new upstream work as
part of the galileo merge currently, so we'll work on reconciling this
on our next proper rebase.
This reverts commit e7c5a8b39ecffac9a49065ec36c2eb32396f302c.
|
|
Galilypad: Walking back the churn on nau8821 to match 6.1.52-valve3.
For jupiter-only drivers we don't want to pull in new upstream work as
part of the galileo merge currently, so we'll work on reconciling this
on our next proper rebase.
This reverts commit 6a8421963a7723b2131f763729711fc9fd5116c9.
|
|
|
|
Brings in BT wake kernel changes needed for release
See merge request valve/galileo/linux-integration!24
|
|
because it continued advertizing after the Steam Controller was disconnected.
<Change Type>: Poor experience
<<< Test Notes >>>
<Test-Proposal>:
1)BT BR/EDR gamepad wakeup function
1)BT BLE gamepad wakeup function
<Stress-Test>: Y
|
|
<Change Type>: FR(Feature Request)
<<< Test Notes >>>
<Test-Proposal>:
1)BT function(power on/restart/connect/disconnect/iop)
2)BT BR/EDR gamepad wakeup function
3)BT BLE gamepad wakeup function
<Stress-Test>: Y
|
|
|
|
500k uNits * 65k max brightness range overflows in the conversion code.
Scale back brightness range to 12bit max.
|
|
|
|
This reverts commit f1f63fbd6a31efad6165f4b35b20ba65f25f877b.
|
|
|
|
This reverts commit bfcc5dc2cb01d06e64c53e00fb027c2c53c372e9.
This cherry-pick is a merge accident -- independently resolved by
9185a24cc5f7f3a0890836801b41c7bc08eb0781, and the changes in the
cherry-pick are unrelated to the upstream patch regardless.
|
|
This reverts commit 234dbec4a5c34ab7c1c3ea9809d65511beb07260.
This was double-cherry-picked -- superceded by newer commit
3a19a3217d9d0145589d9d94c8579823a3b801c1
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit 36301114e8a32e7f13985cbbeff7282d4c599aed)
|
|
- OLED TV front porch workarounds
- AMDGPU Color state management froggery 🐸🐸🐸🐸🐸🐸 :D
- Dock 1200MHz pxl clock WAR
|
|
|
|
|
|
porch time
Changing refresh rates on OLED displays works differently to typical
LCD panels in that instead of changing the clock, the vertical porch
is extended significantly for lower rates.
This can mean that the vertical porch can be incredibly large for
non-base refresh rates eg. 60Hz on a 90Hz display.
This isn't an issue for X11/typical compositors as their present slop
is 1/2th of the refresh interval so the issue never manifests.
However in Gamescope, the present slop very small and tuned to be
optimal in real-time to try and reduce display latency significantly.
This results in us queueing up the atomic commit inside the vertical
porch region which, due to legacy X11/sync control reasons, means that
AMDGPU must target the next vblank.
This patch changes that behaviour to make FRR displays match what occurs
on VRR/Freesync displays where the vertical porch time is not included
in determining what vblank to target and solves the issue.
This means that smarter compositors can get large input latency
reductions when using OLED displays at lower than base refresh rates.
For upstreaming this patch, it will need to be considered what the best
solution is to enable this behaviour from the userspace side.
Obviously the X11/legacy stuff probably cannot change here -- so we
either need to enable this new behaviour globally for all DRM atomic
clients (ie. basically Wayland compositors) or have a
new DRM_MODE_ATOMIC flag.
Signed-off-by: Joshua Ashton <joshua@froggi.es>
|
|
amdgpu_dm_plane_set_color_properties
Pure luck we didn't run into this before.
Could be a newly allocated dc_plane_state.
Signed-off-by: Joshua Ashton <joshua@froggi.es>
|
|
This was done on the new copy rather the old one, so it was never actually duplicating any of this state.
Signed-off-by: Joshua Ashton <joshua@froggi.es>
|
|
Signed-off-by: Joshua Ashton <joshua@froggi.es>
|
|
Otherwise we can end up with a frame on unsuspend where color management
is not applied when userspace has not committed themselves.
Fixes re-applying color management on Steam Deck/Gamescope on S3 resume.
Signed-off-by: Joshua Ashton <joshua@froggi.es>
|
|
DCN2 family and older only support pre-blending DPP gamut remap matrix.
As DRM interface only exposes post-blending CTM property, the driver
maps DRM CRTC CTM to stream gamut remap matrix and applies it to DPP
color block. However, DCN3 and newer has gamut remap matrix on both DPP
and MPC blocks. Since we are exposing a driver-specific property for
plane CTM we want to prioritize plane gamut remap matrix programming
instead of the stream one on DPP block.
We still need to figure out how to detach stream gamut remap matrix from
DPP to MPC block in newer drivers. So that, we won't need to choose
between pre- and post-blending CTM, because we can have both.
Signed-off-by: Melissa Wen <mwen@igalia.com>
|
|
|
|
amdgpu_dm_plane_set_color_properties
Pure luck we didn't run into this before.
Could be a newly allocated dc_plane_state.
Signed-off-by: Joshua Ashton <joshua@froggi.es>
|