1. Feb 01, 2023
    • Mario Limonciello's avatar
      drm/amd: Allow s0ix without BIOS support · cf488dcd
      Mario Limonciello authored
      
      
      We guard the suspend entry code from running unless we have proper
      BIOS support for either S3 mode or s0ix mode.
      
      If a user's system doesn't support either of these modes the kernel
      still does offer s2idle in `/sys/power/mem_sleep` so there is an
      expectation from users that it works even if the power consumption
      remains very high.
      
      Rafael Ávila de Espíndola reports that a system of his has a
      non-functional graphics stack after resuming.  That system doesn't
      support S3 and the FADT doesn't indicate support for low power idle.
      
      Through some experimentation it was concluded that even without the
      hardware s0i3 support provided by the amd_pmc driver the power
      consumption over suspend is decreased by running amdgpu's s0ix
      suspend routine.
      
      The numbers over suspend showed:
      * No patch: 9.2W
      * Skip amdgpu suspend entirely: 10.5W
      * Run amdgpu s0ix routine: 7.7W
      
      As this does improve the power, remove some of the guard rails in
      `amdgpu_acpi.c` for only running s0ix suspend routines in the right
      circumstances.
      
      However if this turns out to cause regressions for anyone, we should
      revert this change and instead opt for skipping suspend/resume routines
      entirely or try to fix the underlying behavior that makes graphics fail
      after resume without underlying platform support.
      
      Reported-by: default avatarRafael Ávila de Espíndola <rafael@espindo.la>
      Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2364
      
      
      Acked-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      Signed-off-by: default avatarMario Limonciello <mario.limonciello@amd.com>
      Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      cf488dcd
    • Vitaly Prosyak's avatar
      Revert "drm/amdgpu: TA unload messages are not actually sent to psp when amdgpu is uninstalled" · 39934d3e
      Vitaly Prosyak authored
      This reverts commit fac53471
      
      .
      The following change: move the drm_dev_unplug call after
      amdgpu_driver_unload_kms in amdgpu_pci_remove. The reason is
      the following: amdgpu_pci_remove calls drm_dev_unregister
      and it should be called first to ensure userspace can't access the
      device instance anymore. If we call drm_dev_unplug after
      amdgpu_driver_unload_kms then we observe IGT PCI software unplug
      test failure (kernel hung) for all ASICs. This is how this
      regression was found.
      
      After this revert, the following commands do work not, but it would
      be fixed in the next commit:
       - sudo modprobe -r amdgpu
       - sudo modprobe amdgpu
      
      Signed-off-by: default avatarVitaly Prosyak <vitaly.prosyak@amd.com>
      Reviewed-by Alex Deucher <alexander.deucher@amd.com>
      Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      39934d3e
  2. Jan 31, 2023
    • Daniel Vetter's avatar
      Merge v6.2-rc6 into drm-next · aebd8f0c
      Daniel Vetter authored
      
      
      Due to holidays we started -next with more -fixes in-flight than
      usual, and people have been asking where they are. Backmerge to get
      things better in sync.
      
      Conflicts:
      - Tiny conflict in drm_fbdev_generic.c between variable rename and
        missing error handling that got added.
      - Conflict in drm_fb_helper.c between the added call to vgaswitcheroo
        in drm_fb_helper_single_fb_probe and a refactor patch that extracted
        lots of helpers and incidentally removed the dev local variable.
        Readd it to make things compile.
      
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      aebd8f0c
  3. Jan 30, 2023
  4. Jan 29, 2023
    • Linus Torvalds's avatar
      Fix up more non-executable files marked executable · c9661827
      Linus Torvalds authored
      Joe found another DT file that shouldn't be executable, and that
      frustrated me enough that I went hunting with this script:
      
          git ls-files -s |
              grep '^100755' |
              cut -f2 |
              xargs grep -L '^#!'
      
      and that found another file that shouldn't have been marked executable
      either, despite being in the scripts directory.
      
      Maybe these two are the last ones at least for now.  But I'm sure we'll
      be back in a few years, fixing things up again.
      
      Fixes: 8c6789f4 ("ASoC: dt-bindings: Add Everest ES8326 audio CODEC")
      Fixes: 4d8e5cd2
      
       ("locking/atomics: Fix scripts/atomic/ script permissions")
      Reported-by: default avatarJoe Perches <joe@perches.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      c9661827
    • Linus Torvalds's avatar
      Merge tag '6.2-rc5-ksmbd-server-fixes' of git://git.samba.org/ksmbd · 2543fdbd
      Linus Torvalds authored
      Pull ksmbd server fixes from Steve French:
       "Four smb3 server fixes, all also for stable:
      
         - fix for signing bug
      
         - fix to more strictly check packet length
      
         - add a max connections parm to limit simultaneous connections
      
         - fix error message flood that can occur with newer Samba xattr
           format"
      
      * tag '6.2-rc5-ksmbd-server-fixes' of git://git.samba.org/ksmbd:
        ksmbd: downgrade ndr version error message to debug
        ksmbd: limit pdu length size according to connection status
        ksmbd: do not sign response to session request for guest login
        ksmbd: add max connections parameter
      2543fdbd
  5. Jan 28, 2023
  6. Jan 27, 2023