1. 08 Jul, 2024 5 commits
  2. 05 Jul, 2024 4 commits
  3. 01 Jul, 2024 3 commits
  4. 27 Jun, 2024 1 commit
  5. 25 Jun, 2024 5 commits
  6. 24 Jun, 2024 1 commit
  7. 23 Jun, 2024 1 commit
    • Mark Brown's avatar
      spi: add devm_spi_optimize_message() helper · 17436001
      Mark Brown authored
      Merge series from David Lechner <dlechner@baylibre.com>:
      
      In the IIO subsystem, we are finding that it is common to call
      spi_optimize_message() during driver probe since the SPI message
      doesn't change for the lifetime of the driver. This patch adds a
      devm_spi_optimize_message() helper to simplify this common pattern.
      17436001
  8. 22 Jun, 2024 2 commits
  9. 21 Jun, 2024 1 commit
  10. 20 Jun, 2024 3 commits
  11. 19 Jun, 2024 2 commits
    • Marc Kleine-Budde's avatar
      spi: spi-imx: imx51: revert burst length calculation back to bits_per_word · df75470b
      Marc Kleine-Budde authored
      The patch 15a6af94 ("spi: Increase imx51 ecspi burst length based
      on transfer length") increased the burst length calculation in
      mx51_ecspi_prepare_transfer() to be based on the transfer length.
      
      This breaks HW CS + SPI_CS_WORD support which was added in
      6e95b23a ("spi: imx: Implement support for CS_WORD") and transfers
      with bits-per-word != 8, 16, 32.
      
      SPI_CS_WORD means the CS should be toggled after each word. The
      implementation in the imx-spi driver relies on the fact that the HW CS
      is toggled automatically by the controller after each burst length
      number of bits. Setting the burst length to the number of bits of the
      _whole_ message breaks this use case.
      
      Further the patch 15a6af94 ("spi: Increase imx51 ecspi burst
      length based on transfer length") claims to optimize the transfers.
      But even without this patch, on modern spi-imx controllers with
      "dynamic_burst = true" (imx51, imx6 and newer), the transfers are
      already optimized, i.e. the burst length is dynamically adjusted in
      spi_imx_push() to avoid the pause between the SPI bursts. This has
      been confirmed by a scope measurement on an imx6d.
      
      Subsequent Patches tried to fix these and other problems:
      
      - 5f66db08 ("spi: imx: Take in account bits per word instead of assuming 8-bits")
      - e9b220ae ("spi: spi-imx: correctly configure burst length when using dma")
      - c712c05e ("spi: imx: fix the burst length at DMA mode and CPU mode")
      - cf6d79a0 ("spi: spi-imx: fix off-by-one in mx51 CPU mode burst length")
      
      but the HW CS + SPI_CS_WORD use case is still broken.
      
      To fix the problems revert the burst size calculation in
      mx51_ecspi_prepare_transfer() back to the original form, before
      15a6af94 ("spi: Increase imx51 ecspi burst length based on
      transfer length") was applied.
      
      Cc: Stefan Moring <stefan.moring@technolution.nl>
      Cc: Stefan Bigler <linux@bigler.io>
      Cc: Clark Wang <xiaoning.wang@nxp.com>
      Cc: Carlos Song <carlos.song@nxp.com>
      Cc: Sebastian Reichel <sre@kernel.org>
      Cc: Thorsten Scherer <T.Scherer@eckelmann.de>
      Fixes: 15a6af94 ("spi: Increase imx51 ecspi burst length based on transfer length")
      Fixes: 5f66db08 ("spi: imx: Take in account bits per word instead of assuming 8-bits")
      Fixes: e9b220ae ("spi: spi-imx: correctly configure burst length when using dma")
      Fixes: c712c05e ("spi: imx: fix the burst length at DMA mode and CPU mode")
      Fixes: cf6d79a0 ("spi: spi-imx: fix off-by-one in mx51 CPU mode burst length")
      Link: https://lore.kernel.org/all/20240618-oxpecker-of-ideal-mastery-db59f8-mkl@pengutronix.deSigned-off-by: default avatarMarc Kleine-Budde <mkl@pengutronix.de>
      Tested-by: default avatarThorsten Scherer <t.scherer@eckelmann.de>
      Link: https://msgid.link/r/20240618-spi-imx-fix-bustlength-v1-1-2053dd5fdf87@pengutronix.deSigned-off-by: default avatarMark Brown <broonie@kernel.org>
      df75470b
    • Amit Kumar Mahapatra's avatar
      spi: spi-cadence: Enable spi refclk in slave mode · 78b05172
      Amit Kumar Mahapatra authored
      When spi-cadence is configured as a slave, it requires the SPI refclk to
      detect the synchronization start condition while communicating with the
      master. However, the spi-cadence driver never enables the SPI refclk in
      slave mode, causing the refclk to remain disabled if the
      "clk_ignore_unused" kernel parameter is not passed through bootargs.
      As a result, the slave cannot detect data sent by the master, leading to
      communication failure. Update driver to enable the SPI refclk in both
      master and slave configurations.
      
      Fixes: b1b90514 ("spi: spi-cadence: Add support for Slave mode")
      Signed-off-by: default avatarAmit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>
      Link: https://msgid.link/r/20240617153837.29861-1-amit.kumar-mahapatra@amd.comSigned-off-by: default avatarMark Brown <broonie@kernel.org>
      78b05172
  12. 18 Jun, 2024 5 commits
  13. 16 Jun, 2024 7 commits
    • Linus Torvalds's avatar
      Linux 6.10-rc4 · 6ba59ff4
      Linus Torvalds authored
      6ba59ff4
    • Linus Torvalds's avatar
      Merge tag 'parisc-for-6.10-rc4' of... · 6456c425
      Linus Torvalds authored
      Merge tag 'parisc-for-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux
      
      Pull parisc fix from Helge Deller:
       "On parisc we have suffered since years from random segfaults which
        seem to have been triggered due to cache inconsistencies. Those
        segfaults happened more often on machines with PA8800 and PA8900 CPUs,
        which have much bigger caches than the earlier machines.
      
        Dave Anglin has worked over the last few weeks to fix this bug. His
        patch has been successfully tested by various people on various
        machines and with various kernels (6.6, 6.8 and 6.9), and the debian
        buildd servers haven't shown a single random segfault with this patch.
      
        Since the cache handling has been reworked, the patch is slightly
        bigger than I would like in this stage, but the greatly improved
        stability IMHO justifies the inclusion now"
      
      * tag 'parisc-for-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux:
        parisc: Try to fix random segmentation faults in package builds
      6456c425
    • Linus Torvalds's avatar
      Merge tag 'i2c-for-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux · 4301487e
      Linus Torvalds authored
      Pull i2c fixes from Wolfram Sang:
       "Two fixes to correctly report i2c functionality, ensuring that
        I2C_FUNC_SLAVE is reported when a device operates solely as a slave
        interface"
      
      * tag 'i2c-for-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:
        i2c: designware: Fix the functionality flags of the slave-only interface
        i2c: at91: Fix the functionality flags of the slave-only interface
      4301487e
    • Linus Torvalds's avatar
      Merge tag 'usb-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb · b5beaa44
      Linus Torvalds authored
      Pull USB / Thunderbolt fixes from Greg KH:
       "Here are some small USB and Thunderbolt driver fixes for 6.10-rc4.
        Included in here are:
      
         - thunderbolt debugfs bugfix
      
         - USB typec bugfixes
      
         - kcov usb bugfix
      
         - xhci bugfixes
      
         - usb-storage bugfix
      
         - dt-bindings bugfix
      
         - cdc-wdm log message spam bugfix
      
        All of these, except for the last cdc-wdm log level change, have been
        in linux-next for a while with no reported problems. The cdc-wdm
        bugfix has been tested by syzbot and proved to fix the reported cpu
        lockup issues when the log is constantly spammed by a broken device"
      
      * tag 'usb-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
        USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages
        xhci: Handle TD clearing for multiple streams case
        xhci: Apply broken streams quirk to Etron EJ188 xHCI host
        xhci: Apply reset resume quirk to Etron EJ188 xHCI host
        xhci: Set correct transferred length for cancelled bulk transfers
        usb-storage: alauda: Check whether the media is initialized
        usb: typec: ucsi: Ack also failed Get Error commands
        kcov, usb: disable interrupts in kcov_remote_start_usb_softirq
        dt-bindings: usb: realtek,rts5411: Add missing "additionalProperties" on child nodes
        usb: typec: tcpm: Ignore received Hard Reset in TOGGLING state
        usb: typec: tcpm: fix use-after-free case in tcpm_register_source_caps
        USB: xen-hcd: Traverse host/ when CONFIG_USB_XEN_HCD is selected
        usb: typec: ucsi: glink: increase max ports for x1e80100
        Revert "usb: chipidea: move ci_ulpi_init after the phy initialization"
        thunderbolt: debugfs: Fix margin debugfs node creation condition
      b5beaa44
    • Linus Torvalds's avatar
      Merge tag 'tty-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty · 6efc63a8
      Linus Torvalds authored
      Pull tty/serial driver fixes from Greg KH:
       "Here are some small tty and serial driver fixes that resolve som
        reported problems. Included in here are:
      
         - n_tty lookahead buffer bugfix
      
         - WARN_ON() removal where it was not needed
      
         - 8250_dw driver bugfixes
      
         - 8250_pxa bugfix
      
         - sc16is7xx Kconfig fixes for reported build issues
      
        All of these have been in linux-next for over a week with no reported
        problems"
      
      * tag 'tty-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
        serial: drop debugging WARN_ON_ONCE() from uart_write()
        serial: sc16is7xx: re-add Kconfig SPI or I2C dependency
        serial: sc16is7xx: rename Kconfig CONFIG_SERIAL_SC16IS7XX_CORE
        serial: port: Don't block system suspend even if bytes are left to xmit
        serial: 8250_pxa: Configure tx_loadsz to match FIFO IRQ level
        serial: 8250_dw: Revert "Move definitions to the shared header"
        serial: 8250_dw: Don't use struct dw8250_data outside of 8250_dw
        tty: n_tty: Fix buffer offsets when lookahead is used
      6efc63a8
    • Linus Torvalds's avatar
      Merge tag 'staging-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging · d3e6dc4f
      Linus Torvalds authored
      Pull staging driver fix from Greg KH:
       "Here is a single staging driver fix, for the vc04 driver. It resolves
        a reported problem that showed up in the merge window set of changes.
      
        It's been in linux-next for over a week with no reported problems"
      
      * tag 'staging-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging:
        staging: vchiq_debugfs: Fix NPD in vchiq_dump_state
      d3e6dc4f
    • Linus Torvalds's avatar
      Merge tag 'driver-core-6.10-rc4' of... · e12fa4dd
      Linus Torvalds authored
      Merge tag 'driver-core-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
      
      Pull driver core and sysfs fixes from Greg KH:
       "Here are three small changes for 6.10-rc4 that resolve reported
        problems, and finally drop an unused api call. These are:
      
         - removal of devm_device_add_groups(), all the callers of this are
           finally gone after the 6.10-rc1 merge (changes came in through
           different trees), so it's safe to remove.
      
         - much reported sysfs build error fixed up for systems that did not
           have sysfs enabled
      
         - driver core sync issue fix for a many reported issue over the years
           that no one really paid much attention to, until Dirk finally
           tracked down the real issue and made the "obviously correct and
           simple" fix for it.
      
        All of these have been in linux-next for over a week with no reported
        problems"
      
      * tag 'driver-core-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
        drivers: core: synchronize really_probe() and dev_uevent()
        sysfs: Unbreak the build around sysfs_bin_attr_simple_read()
        driver core: remove devm_device_add_groups()
      e12fa4dd