15 Apr, 2016

2 commits


05 May, 2014

1 commit

  • To prepare pin-controller consolidation, first rename all pinctrl nodes
    to a more appropriate name regarding ePAPR recommended names.

    Signed-off-by: Sebastian Hesselbarth
    Acked-by: Andrew Lunn
    Link: https://lkml.kernel.org/r/1398862602-29595-6-git-send-email-sebastian.hesselbarth@gmail.com
    Signed-off-by: Jason Cooper

    Sebastian Hesselbarth
     

08 Dec, 2013

2 commits


02 Oct, 2013

1 commit

  • kirkwood_setup_wins is the last manual caller of mbus in kirkwood, don't
    call it for DT boards and rely on the DT having a mbus node with
    a proper ranges property to setup these windows.

    Move all the mbus ranges properties for all boards into kirkwood.dtsi,
    since they are currently all the same.

    This makes the DT self consistent, since the physical address of the
    NAND and CRYPTO are both referenced internally. The arbitary Linux
    constants KIRKWOOD_NAND_MEM_PHYS_BASE and KIRKWOOD_SRAM_PHYS_BASE
    no longer have to match the DT values.

    Signed-off-by: Jason Gunthorpe
    Acked-by: Ezequiel Garcia
    Tested-by: Ezequiel Garcia
    Signed-off-by: Jason Cooper

    Jason Gunthorpe
     

07 Sep, 2013

1 commit

  • Pull ARM SoC board updates from Olof Johansson:
    "Board updates for 3.12. Again, a bit of domain overlap with SoC and
    DT branches, but most of this is around legacy code and board support.
    We've found that platform maintainers have a hard time separating all
    of these out and might move towards fewer branches for next release.

    - Removal of a number of Marvell Kirkwood board files, since contents
    is now common and mostly configured via DT.
    - Device-tree updates for Marvell Dove, including irqchip and
    clocksource setup.
    - Defconfig updates. Gotta go somewhere. One new one for Renesas
    Lager.
    - New backlight drivers for backlights used on Renesas shmobile
    platforms.
    - Removal of Renesas leds driver.
    - Shuffling of some of the new Broadcom platforms to give room for
    others in the same mach directory. More in 3.13"

    * tag 'boards-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (67 commits)
    mmc: sdhci-bcm-kona: Staticize sdhci_bcm_kona_card_event
    mmc: sdhci-bcm-kona: Remove unneeded version.h inclusion
    ARM: bcm: Make secure API call optional
    ARM: DT: binding fixup to align with vendor-prefixes.txt (drivers)
    ARM: mmc: fix NONREMOVABLE test in sdhci-bcm-kona
    ARM: bcm: Rename board_bcm
    mmc: sdhci-bcm-kona: make linker-section warning go away
    ARM: tegra: defconfig updates
    ARM: dove: add initial DT file for Globalscale D2Plug
    ARM: dove: add GPIO IR receiver node to SolidRun CuBox
    ARM: dove: add common pinmux functions to DT
    ARM: dove: add cpu device tree node
    ARM: dove: update dove_defconfig with SI5351, PCI, and xHCI
    arch/arm/mach-kirkwood: Avoid using ARRAY_AND_SIZE(e) as a function argument
    ARM: kirkwood: fix DT building and update defconfig
    ARM: kirkwood: Remove all remaining trace of DNS-320/325 platform code
    ARM: configs: disable DEBUG_LL in bcm_defconfig
    ARM: bcm281xx: Board specific reboot code
    ARM bcm281xx: Turn on socket & network support.
    ARM: bcm281xx: Turn on L2 cache.
    ...

    Linus Torvalds
     

06 Aug, 2013

2 commits

  • Now that mbus has been added to the device tree, it's possible to
    move the PCIe nodes out of the ocp node, placing it directly
    below the mbus. This is a more accurate representation of the hardware.

    Moving the PCIe nodes, we now need to introduce an extra cell to
    encode the window target ID and attribute. Since this depends on
    the PCIe port, we split the ranges translation entries, to
    correspond to each MBus window.

    In addition, we encode the PCIe memory and I/O apertures in the MBus
    node, according to the MBus DT binding specification. The choice made
    is 0xe0000000-0xf0000000 for memory space, and 0xf200000-0xf2100000 for
    I/O space. These apertures can be changed in each per-board DT file.

    Signed-off-by: Ezequiel Garcia
    Tested-by: Andrew Lunn
    Tested-by: Sebastian Hesselbarth
    Signed-off-by: Jason Cooper

    Ezequiel Garcia
     
  • Signed-off-by: Ezequiel Garcia
    Tested-by: Andrew Lunn
    Tested-by: Sebastian Hesselbarth
    Signed-off-by: Jason Cooper

    Ezequiel Garcia
     

26 Jul, 2013

1 commit


03 Jul, 2013

1 commit

  • Pull ARM SoC device tree changes from Arnd Bergmann:
    "These changes from 30 individual branches for the most part update
    device tree files, but there are also a few source code changes that
    have crept in this time, usually in order to atomically move over a
    driver from using hardcoded data to DT probing.

    A number of platforms change their DT files to use the C preprocessor,
    which is causing a bit of churn, but that is hopefully only this once"

    * tag 'dt-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (372 commits)
    ARM: at91: dt: rm9200ek: add spi support
    ARM: at91: dt: rm9200: add spi support
    ARM: at91/DT: at91sam9n12: add SPI DMA client infos
    ARM: at91/DT: sama5d3: add SPI DMA client infos
    ARM: at91/DT: fix SPI compatibility string
    ARM: Kirkwood: Fix the internal register ranges translation
    ARM: dts: bcm281xx: change comment to C89 style
    ARM: mmc: bcm281xx SDHCI driver (dt mods)
    ARM: nomadik: add the new clocks to the device tree
    clk: nomadik: implement the Nomadik clocks properly
    ARM: dts: omap5-uevm: Provide USB Host PHY clock frequency
    ARM: dts: omap4-panda: Fix DVI EDID reads
    ARM: dts: omap4-panda: Add USB Host support
    arm: mvebu: enable mini-PCIe connectors on Armada 370 RD
    ARM: shmobile: irqpin: add a DT property to enable masking on parent
    ARM: dts: AM43x EPOS EVM support
    ARM: dts: OMAP5: Add bandgap DT entry
    ARM: dts: AM33XX: Add pinmux configuration for CPSW to am335x EVM
    ARM: dts: AM33XX: Add pinmux configuration for CPSW to EVMsk
    ARM: dts: AM33XX: Add pinmux configuration for CPSW to beaglebone
    ...

    Linus Torvalds
     

12 Jun, 2013

1 commit


28 May, 2013

1 commit


27 May, 2013

1 commit

  • When the pinmux mechanism was added in Kirkwood, the device driver
    core was not yet providing the possibility of attaching pinmux
    configurations to all devices, drivers had to do it explicitly, and
    not all drivers were doing this.

    Now that the driver core does that in a generic way, it makes sense to
    attach the pinmux configuration to their corresponding devices.

    This allows the pinctrl subsystem to show in debugfs to which device
    is related which pins, for example:

    pin 41 (PIN41): gpio-leds.1 mvebu-gpio:41 function gpio group mpp41
    pin 42 (PIN42): gpio-leds.1 mvebu-gpio:42 function gpio group mpp42
    pin 43 (PIN43): gpio-leds.1 mvebu-gpio:43 function gpio group mpp43

    Signed-off-by: Thomas Petazzoni
    Acked-by: Andrew Lunn
    Tested-By: Andrew Lunn
    Signed-off-by: Jason Cooper

    Thomas Petazzoni
     

24 Nov, 2012

1 commit


27 Jul, 2012

1 commit