1. 21 Dec, 2021 1 commit
  2. 20 Dec, 2021 2 commits
  3. 16 Dec, 2021 31 commits
  4. 15 Dec, 2021 1 commit
    • Maxime Ripard's avatar
      drm/vc4: kms: Wait for the commit before increasing our clock rate · 244a36e5
      Maxime Ripard authored
      Several DRM/KMS atomic commits can run in parallel if they affect
      different CRTC. These commits share the global HVS state, so we have
      some code to make sure we run commits in sequence. This synchronization
      code is one of the first thing that runs in vc4_atomic_commit_tail().
      
      Another constraints we have is that we need to make sure the HVS clock
      gets a boost during the commit. That code relies on clk_set_min_rate and
      will remove the old minimum and set a new one. We also need another,
      temporary, minimum for the duration of the commit.
      
      The algorithm is thus to set a temporary minimum, drop the previous
      one, do the commit, and finally set the minimum for the current mode.
      
      However, the part that sets the temporary minimum and drops the older
      one runs before the commit synchronization code.
      
      Thus, under the proper conditions, we can end up mixing up the minimums
      and ending up with the wrong one for our current step.
      
      To avoid it, let's move the clock setup in the protected section.
      
      Fixes: d7d96c00 ("drm/vc4: hvs: Boost the core clock during modeset")
      Signed-off-by: default avatarMaxime Ripard <maxime@cerno.tech>
      Reviewed-by: default avatarDave Stevenson <dave.stevenson@raspberrypi.com>
      Tested-by: default avatarJian-Hong Pan <jhp@endlessos.org>
      [danvet: re-apply this from 0c980a00 ("drm/vc4: kms: Wait for the
      commit before increasing our clock rate") because I lost that part in
      my merge resolution in 99b03ca6 ("Merge v5.16-rc5 into drm-next")]
      Fixes: 99b03ca6 ("Merge v5.16-rc5 into drm-next")
      Acked-by: default avatarMaxime Ripard <maxime@cerno.tech>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@intel.com>
      Link: https://lore.kernel.org/r/20211117094527.146275-2-maxime@cerno.tech
      244a36e5
  5. 14 Dec, 2021 2 commits
  6. 12 Dec, 2021 3 commits
    • Linus Torvalds's avatar
      Linux 5.16-rc5 · 2585cf9d
      Linus Torvalds authored
      2585cf9d
    • Linus Torvalds's avatar
      Merge tag 'usb-5.16-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb · 90d9fbc1
      Linus Torvalds authored
      Pull USB fixes from Greg KH:
       "Here are some small USB fixes for 5.16-rc5.  They include:
      
         - gadget driver fixes for reported issues
      
         - xhci fixes for reported problems.
      
         - config endpoint parsing fixes for where we got bitfields wrong
      
        Most of these have been in linux-next, the remaining few were not, but
        got lots of local testing in my systems and in some cloud testing
        infrastructures"
      
      * tag 'usb-5.16-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
        usb: core: config: using bit mask instead of individual bits
        usb: core: config: fix validation of wMaxPacketValue entries
        USB: gadget: zero allocate endpoint 0 buffers
        USB: gadget: detect too-big endpoint 0 requests
        xhci: avoid race between disable slot command and host runtime suspend
        xhci: Remove CONFIG_USB_DEFAULT_PERSIST to prevent xHCI from runtime suspending
        Revert "usb: dwc3: dwc3-qcom: Enable tx-fifo-resize property by default"
      90d9fbc1
    • Linus Torvalds's avatar
      Merge tag 'char-misc-5.16-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc · 8d7ed104
      Linus Torvalds authored
      Pull char/misc driver fixes from Greg KH:
       "Here are a bunch of small char/misc and other driver subsystem fixes.
      
        Included in here are:
      
         - iio driver fixes for reported problems
      
         - phy driver fixes for a number of reported problems
      
         - mhi resume bugfix for broken hardware
      
         - nvmem driver fix
      
         - rtsx driver fix for irq issues
      
         - fastrpc packet parsing fix
      
        All of these have been in linux-next for a while with no reported
        issues"
      
      * tag 'char-misc-5.16-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc: (33 commits)
        bus: mhi: core: Add support for forced PM resume
        iio: trigger: stm32-timer: fix MODULE_ALIAS
        misc: rtsx: Avoid mangling IRQ during runtime PM
        nvmem: eeprom: at25: fix FRAM byte_len
        misc: fastrpc: fix improper packet size calculation
        MAINTAINERS: add maintainer for Qualcomm FastRPC driver
        bus: mhi: pci_generic: Fix device recovery failed issue
        iio: adc: stm32: fix null pointer on defer_probe error
        phy: HiSilicon: Fix copy and paste bug in error handling
        dt-bindings: phy: zynqmp-psgtr: fix USB phy name
        phy: ti: omap-usb2: Fix the kernel-doc style
        phy: qualcomm: ipq806x-usb: Fix kernel-doc style
        iio: at91-sama5d2: Fix incorrect sign extension
        iio: adc: axp20x_adc: fix charging current reporting on AXP22x
        iio: gyro: adxrs290: fix data signedness
        phy: ti: tusb1210: Fix the kernel-doc warn
        phy: qualcomm: usb-hsic: Fix the kernel-doc warn
        phy: qualcomm: qmp: Add missing struct documentation
        phy: mvebu-cp110-utmi: Fix kernel-doc warns
        iio: ad7768-1: Call iio_trigger_notify_done() on error
        ...
      8d7ed104