1. 19 Apr, 2017 5 commits
  2. 10 Apr, 2017 1 commit
  3. 04 Apr, 2017 2 commits
  4. 31 Mar, 2017 1 commit
    • Arnd Bergmann's avatar
      Merge tag 'arm-soc/for-4.12/soc' of http://github.com/Broadcom/stblinux into next/soc · b69bad75
      Arnd Bergmann authored
      Pull "Broadcom soc changes for 4.12" from Florian Fainelli:
      
      This pull request contains Broadcom ARM-based SoC Kconfig/platform changes for
      4.12, please pull the following:
      
      - Al enables ZONE_DMA for BRCMSTB platforms since a bunch of on-chip
        peripherals such as USB (OHCI and EHCI) and SDHCI cannot support physical
        addresses > 32-bit. This is only required when ARM_LPAE is enabled
      
      - Danesh enables ARCH_HAS_HOLES_MEMORYMODEL in order for the kernel to provide
        a pfn_valid() implementation despite BRCMSTB enabling the SPARSEMEM model by
        default.
      
      - Florian adds support for a new 28nm generation chip: 7260 by updating the
        runtime detection UART debuggin stub used for DEBUG_LL.
      
      * tag 'arm-soc/for-4.12/soc' of http://github.com/Broadcom/stblinux:
        ARM: brcmstb: Add entry for 7260
        ARM: brcmstb: Enable ARCH_HAS_HOLES_MEMORYMODEL
        ARM: brcmstb: Enable ZONE_DMA for non 64-bit capable peripherals
      b69bad75
  5. 30 Mar, 2017 4 commits
    • Arnd Bergmann's avatar
      Merge tag 'gemini-multiplat-2' of... · 88f31b1d
      Arnd Bergmann authored
      Merge tag 'gemini-multiplat-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik into next/soc
      
      Pull "Gemini multiplatform updates" from Linus Walleij:
      
      - Select the poweroff driver so the system can properly shut down.
        This driver is merged in the power tree.
      - Select the right Faraday GPIO block (we renamed it).
      - Do not select SERIAL_OF_PLATFORM that just create Kconfig
        warnings on us. We'll put that into the defconfig instead.
      
      * tag 'gemini-multiplat-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik:
        ARM: gemini: don't select SERIAL_OF_PLATFORM
        ARM: gemini: select the right GPIO block
        ARM: gemini: select gemini poweroff
      88f31b1d
    • Arnd Bergmann's avatar
      Merge tag 'omap-for-v4.12/soc-v2-signed' of... · 59bc516c
      Arnd Bergmann authored
      Merge tag 'omap-for-v4.12/soc-v2-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into next/soc
      
      Pull "SoC changes for omaps for v4.12 merge window" from Tony Lindgren:
      
      - Drop PM_SUSPEND_STANDBY
      
      - Clean up hwmod code in preparation to eventually dynamically
        allocating hwmod data based on device tree data
      
      - Implement hwmod workaround for dra7 DCAN1 and OTG module to prevent
        clockdomain from entering HW_AUTO
      
      - Configure clockdomain and hwmod for dm81xx SATA
      
      - Mark omap_init_rng as __init
      
      * tag 'omap-for-v4.12/soc-v2-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
        ARM: OMAP2+: mark omap_init_rng as __init
        ARM: OMAP2+: dm81xx: Add clkdm and hwmod for SATA
        ARM: DRA7: hwmod_data: Prevent wait_target_disable error for usb_otg_ss
        ARM: DRA7: hwmod: Fix DCAN1 stuck in transition
        ARM: OMAP2+ hwmod: Allow modules to disable HW_AUTO
        ARM: OMAP2+: omap_hwmod: provide space for more hwmod flags
        ARM: OMAP2+: Make hwmod clkdm_name const
        ARM: OMAP2+: Remove unused CLOCKACT_TEST_ICLK
        ARM: OMAP2+: Use list_for_each_entry for hwmod slave_ports
        ARM: OMAP2+: Remove mostly unused hwmod linkspace
        ARM: OMAP: PM: Drop useless checks for PM_SUSPEND_STANDBY
      59bc516c
    • Arnd Bergmann's avatar
      Merge tag 'davinci-for-v4.12/soc' of... · 2235ac90
      Arnd Bergmann authored
      Merge tag 'davinci-for-v4.12/soc' of git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci into next/soc
      
      Pull "DaVinci SoC updates for v4.12" from Sekhar Nori:
      
      v4.12 SoC updates for DaVinci include necessary pdata-quirks
      to make video capture and display work on da850.
      
      VPIF driver which supports video capture and display on
      da850 is a legacy driver.  It does not have DT equavalents
      for all things that are used on platform data.
      
      Attempts were made to pass data via DT[1], but linux-media
      does not yet have a good way of describing subdevices in
      device tree. This is work in progress. As soon as bindings
      are defined and implementation is available, we can shift
      to using that. For now we are stuck with using pdata.
      
      The pull request also has some clean-up for PM, and a fix
      for pdata quirks mechanism.
      
      [1] https://marc.info/?l=devicetree&m=147982998517384
      
      * tag 'davinci-for-v4.12/soc' of git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci:
        ARM: davinci: add pdata-quirks for da850-evm vpif display
        ARM: da850-evm: add a fixed regulator for the UI board IO expander
        ARM: davinci: da8xx: add pdata-quirks for VPIF capture
        ARM: davinci: da8xx: add OF_DEV_AUXDATA() for vpif
        ARM: davinci: board-da850-evm: add I2C ID for VPIF
        ARM: davinci: allow having multiple pdata-quirks
        ARM: davinci: PM: Drop useless check for PM_SUSPEND_STANDBY
      2235ac90
    • Sekhar Nori's avatar
      ARM: davinci: add pata_bk3710 libata driver support · 28d4d1d0
      Sekhar Nori authored
      Signed-off-by: default avatarSekhar Nori <nsekhar@ti.com>
      [b.zolnierkie: split from bigger patch + preserved old driver support]
      Signed-off-by: default avatarBartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
      28d4d1d0
  6. 28 Mar, 2017 5 commits
  7. 24 Mar, 2017 4 commits
  8. 23 Mar, 2017 3 commits
  9. 22 Mar, 2017 1 commit
  10. 20 Mar, 2017 1 commit
    • Greg Ungerer's avatar
      ARM: imx: set correct chip_select in platform setup · 901f26bc
      Greg Ungerer authored
      Some platform based configuration setup of spi-imx SPI devices does
      not set the "chip_select" to the actual hardware chip select used.
      This works because the cs_gpio mapping that is associated with this
      platform setup maps the chip_select offset used to the appropriate
      hardware chip select. The spi-imx driver uses the chip_select as an
      index into the cs_gpio array and ultimately gets the correct hardware
      chip select for its hardware setup.
      
      The motivation is to be able to eventually modify the spi-imx code to
      use the "chip_select" directly for harwdare setup instead of indirectly
      via the cs_gpio mapping array.
      
      This change only affects platforms using the hardware chip select
      addressing method for their SPI devices (sometimes called native chip
      select). The majority of devices using the spi-imx driver use the GPIO
      addressing method.
      
      The change to use the correct "chip_select" is strait forward. But the
      cs_gpio mapping arrary also needs to be modifed to match that change. In
      simple terms the cs_gpio mapping should always have the hardware chip
      select number at its same index offset.
      
      There is no functional change with these patches. The three affected
      platforms should work exactly as before. However I don't have any of
      these platforms (or access to them) and so I can't test them. So this
      patch is compile tested only.
      Signed-off-by: default avatarGreg Ungerer <gerg@linux-m68k.org>
      Signed-off-by: default avatarShawn Guo <shawnguo@kernel.org>
      901f26bc
  11. 18 Mar, 2017 1 commit
    • Linus Walleij's avatar
      ARM: gemini: select gemini poweroff · 1953d4ad
      Linus Walleij authored
      It's especially annoying if the system cannot be properly
      powered down so select the poweroff driver from the Kconfig.
      
      Cc: Janos Laube <janos.dev@gmail.com>
      Cc: Paulius Zaleckas <paulius.zaleckas@gmail.com>
      Cc: Hans Ulli Kroll <ulli.kroll@googlemail.com>
      Cc: Florian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      1953d4ad
  12. 15 Mar, 2017 3 commits
    • Florian Fainelli's avatar
      ARM: brcmstb: Add entry for 7260 · d47b51ad
      Florian Fainelli authored
      BCM7260 has the same UART base address as 7268, order the entries by
      ascending chip number and alias the 7268 definition to the 7260
      definition.
      Signed-off-by: default avatarFlorian Fainelli <f.fainelli@gmail.com>
      d47b51ad
    • Danesh Petigara's avatar
      ARM: brcmstb: Enable ARCH_HAS_HOLES_MEMORYMODEL · 59f181aa
      Danesh Petigara authored
      Due to the brcmstb SoC's memory map, we may have holes in the memory if
      we don't populate the maximum amount of memory supported by e.g: the
      first memory controller which spans either the first 1GiB or first 2GiB
      of memory.
      
      We need to select ARCH_HAS_HOLES_MEMORYMODEL in order to enable
      CONFIG_HAVE_ARCH_PFN_VALID on platforms that have CONFIG_SPARSEMEM
      enabled.
      Signed-off-by: default avatarDanesh Petigara <danesh.petigara@broadcom.com>
      [florian: Detailed commit message]
      Signed-off-by: default avatarFlorian Fainelli <f.fainelli@gmail.com>
      59f181aa
    • Al Cooper's avatar
      ARM: brcmstb: Enable ZONE_DMA for non 64-bit capable peripherals · 3c51b9c7
      Al Cooper authored
      Some Host Controller hardware blocks, like the OHCI, EHCI and SDIO
      controllers, have hardware blocks that are not capable of doing 64 bit
      DMA. These host controllers fail on boards with >3GB of memory because
      the memory above 3GB is located physically >= 0x100000000 and can only
      be accessed using 64 DMA. The way Linux is currently configured for
      BRCMSTB systems, the memory given to drivers for DMA through functions
      like dma_alloc_coherent() comes from CMA memory and CMA memory is taken
      from the top of physical memory. When these drivers get a DMA buffer
      with an address >=0x100000000, they end up dropping the upper 32 bit of
      the address causing the hardware to DMA to incorrect memory, typically
      BMEM (custom memory carveout). This issue was discovered on a
      BCM97449SSV_DDR4 system with 4GB or memory.
      
      The fix is to enable CONFIG_ZONE_DMA. On ARM systems this makes sure
      that all DMA memory is located within the first 32 bits of address
      space.
      Signed-off-by: default avatarAl Cooper <alcooperx@gmail.com>
      Signed-off-by: default avatarFlorian Fainelli <f.fainelli@gmail.com>
      3c51b9c7
  13. 14 Mar, 2017 4 commits
  14. 13 Mar, 2017 1 commit
  15. 12 Mar, 2017 4 commits