31 Jul, 2013

4 commits


21 Jul, 2013

4 commits

  • of_property_read_u32 return 0 on success. The check was using a ! to
    return error. Fix the if condition.

    Signed-off-by: Rohit Vaswani
    Acked-by: Linus Walleij
    Reviewed-by: Pankaj Jangra
    Cc: "Bird, Tim"
    Signed-off-by: David Brown
    Signed-off-by: Linus Walleij

    Rohit Vaswani
     
  • The OMAP GPIO driver check if the chip has an associated
    Device Tree node using the struct gpio_chip of_node member.

    But this is only build if CONFIG_OF_GPIO is defined which
    leads to the following error when using omap1_defconfig:

    linux/drivers/gpio/gpio-omap.c: In function 'omap_gpio_chip_init':
    linux/drivers/gpio/gpio-omap.c:1080:17: error: 'struct gpio_chip' has no member named 'of_node'
    linux/drivers/gpio/gpio-omap.c: In function 'omap_gpio_irq_map':
    linux/drivers/gpio/gpio-omap.c:1116:16: error: 'struct gpio_chip' has no member named 'of_node'

    Reported-by: Kevin Hilman
    Signed-off-by: Javier Martinez Canillas
    Signed-off-by: Linus Walleij

    Javier Martinez Canillas
     
  • When an OMAP GPIO is used as an IRQ line, a call to gpio_request()
    has to be made to initialize the OMAP GPIO bank before a driver
    request the IRQ. Otherwise the call to request_irq() fails.

    Drives should not be aware of this neither care wether an IRQ line
    is a GPIO or not. They should just request the IRQ and this has to
    be handled by the irq_chip driver.

    With the current OMAP GPIO DT binding, if we define:

    gpio6: gpio@49058000 {
    compatible = "ti,omap3-gpio";
    reg = ;
    interrupts = ;
    ti,hwmods = "gpio6";
    gpio-controller;
    #gpio-cells = ;
    interrupt-controller;
    #interrupt-cells = ;
    };

    interrupt-parent = ;
    interrupts = ;

    The GPIO is correctly mapped as an IRQ but a call to gpio_request()
    is never made. Since a call to the custom IRQ domain .map function
    handler is made for each GPIO used as an IRQ, the GPIO can be setup
    and configured as input there automatically.

    Changes since v3:
    - Use bank->chip.of_node instead of_have_populated_dt() to check
    DT or legacy boot as suggested by Jean-Christophe PLAGNIOL-VILLARD
    - Add a comment that this is just a temporary solution until and
    that it has to be removed once is handled by the IRQ core.

    Changes since v2:
    - Only make the call to gpio_request_one() conditional in the DT
    case as suggested by Grant Likely.

    Changes since v1:
    - Split the irq domain mapping function handler and the GPIO
    request in two different patches.

    Signed-off-by: Javier Martinez Canillas
    Tested-by: Enric Balletbo i Serra
    Acked-by: Grant Likely
    Acked-by: Jean-Christophe PLAGNIOL-VILLARD
    Acked-by: Santosh Shilimkar
    Signed-off-by: Linus Walleij

    Javier Martinez Canillas
     
  • When a GPIO is defined as an interrupt line using Device
    Tree, a call to irq_create_of_mapping() is made that calls
    irq_create_mapping(). So, is not necessary to do the mapping
    for all OMAP GPIO lines and explicitly call irq_create_mapping()
    on the driver probe() when booting with Device Tree.

    Add a custom IRQ domain .map function handler that will be
    called by irq_create_mapping() to map the GPIO lines used as IRQ.
    This also allows to execute needed setup code such as configuring
    a GPIO as input and enabling the GPIO bank.

    Changes since v3:
    - Use bank->chip.of_node instead of_have_populated_dt() to check
    DT or legacy boot as suggested by Jean-Christophe PLAGNIOL-VILLARD

    Changes since v2:
    - Unconditionally do the IRQ setup in the .map() function and
    only call irq_create_mapping() in the gpio chip init to avoid
    code duplication as suggested by Grant Likely.

    Changes since v1:
    - Split the addition of the .map function handler and the
    automatic gpio request in two different patches.
    - Add GPIO IRQ setup logic to the irq domain mapping function.
    - Only call irq_create_mapping for every GPIO on legacy boot.
    - Only setup a GPIO IRQ on the .map function for DeviceTree boot.

    Signed-off-by: Javier Martinez Canillas
    Tested-by: Enric Balletbo i Serra
    Acked-by: Grant Likely
    Acked-by: Jean-Christophe PLAGNIOL-VILLARD
    Acked-by: Santosh Shilimkar
    Signed-off-by: Linus Walleij

    Javier Martinez Canillas
     

04 Jul, 2013

2 commits

  • Pull power management and ACPI updates from Rafael Wysocki:
    "This time the total number of ACPI commits is slightly greater than
    the number of cpufreq commits, but Viresh Kumar (who works on cpufreq)
    remains the most active patch submitter.

    To me, the most significant change is the addition of offline/online
    device operations to the driver core (with the Greg's blessing) and
    the related modifications of the ACPI core hotplug code. Next are the
    freezer updates from Colin Cross that should make the freezing of
    tasks a bit less heavy weight.

    We also have a couple of regression fixes, a number of fixes for
    issues that have not been identified as regressions, two new drivers
    and a bunch of cleanups all over.

    Highlights:

    - Hotplug changes to support graceful hot-removal failures.

    It sometimes is necessary to fail device hot-removal operations
    gracefully if they cannot be carried out completely. For example,
    if memory from a memory module being hot-removed has been allocated
    for the kernel's own use and cannot be moved elsewhere, it's
    desirable to fail the hot-removal operation in a graceful way
    rather than to crash the kernel, but currenty a success or a kernel
    crash are the only possible outcomes of an attempted memory
    hot-removal. Needless to say, that is not a very attractive
    alternative and it had to be addressed.

    However, in order to make it work for memory, I first had to make
    it work for CPUs and for this purpose I needed to modify the ACPI
    processor driver. It's been split into two parts, a resident one
    handling the low-level initialization/cleanup and a modular one
    playing the actual driver's role (but it binds to the CPU system
    device objects rather than to the ACPI device objects representing
    processors). That's been sort of like a live brain surgery on a
    patient who's riding a bike.

    So this is a little scary, but since we found and fixed a couple of
    regressions it caused to happen during the early linux-next testing
    (a month ago), nobody has complained.

    As a bonus we remove some duplicated ACPI hotplug code, because the
    ACPI-based CPU hotplug is now going to use the common ACPI hotplug
    code.

    - Lighter weight freezing of tasks.

    These changes from Colin Cross and Mandeep Singh Baines are
    targeted at making the freezing of tasks a bit less heavy weight
    operation. They reduce the number of tasks woken up every time
    during the freezing, by using the observation that the freezer
    simply doesn't need to wake up some of them and wait for them all
    to call refrigerator(). The time needed for the freezer to decide
    to report a failure is reduced too.

    Also reintroduced is the check causing a lockdep warining to
    trigger when try_to_freeze() is called with locks held (which is
    generally unsafe and shouldn't happen).

    - cpufreq updates

    First off, a commit from Srivatsa S Bhat fixes a resume regression
    introduced during the 3.10 cycle causing some cpufreq sysfs
    attributes to return wrong values to user space after resume. The
    fix is kind of fresh, but also it's pretty obvious once Srivatsa
    has identified the root cause.

    Second, we have a new freqdomain_cpus sysfs attribute for the
    acpi-cpufreq driver to provide information previously available via
    related_cpus. From Lan Tianyu.

    Finally, we fix a number of issues, mostly related to the
    CPUFREQ_POSTCHANGE notifier and cpufreq Kconfig options and clean
    up some code. The majority of changes from Viresh Kumar with bits
    from Jacob Shin, Heiko Stübner, Xiaoguang Chen, Ezequiel Garcia,
    Arnd Bergmann, and Tang Yuantian.

    - ACPICA update

    A usual bunch of updates from the ACPICA upstream.

    During the 3.4 cycle we introduced support for ACPI 5 extended
    sleep registers, but they are only supposed to be used if the
    HW-reduced mode bit is set in the FADT flags and the code attempted
    to use them without checking that bit. That caused suspend/resume
    regressions to happen on some systems. Fix from Lv Zheng causes
    those registers to be used only if the HW-reduced mode bit is set.

    Apart from this some other ACPICA bugs are fixed and code cleanups
    are made by Bob Moore, Tomasz Nowicki, Lv Zheng, Chao Guan, and
    Zhang Rui.

    - cpuidle updates

    New driver for Xilinx Zynq processors is added by Michal Simek.

    Multidriver support simplification, addition of some missing
    kerneldoc comments and Kconfig-related fixes come from Daniel
    Lezcano.

    - ACPI power management updates

    Changes to make suspend/resume work correctly in Xen guests from
    Konrad Rzeszutek Wilk, sparse warning fix from Fengguang Wu and
    cleanups and fixes of the ACPI device power state selection
    routine.

    - ACPI documentation updates

    Some previously missing pieces of ACPI documentation are added by
    Lv Zheng and Aaron Lu (hopefully, that will help people to
    uderstand how the ACPI subsystem works) and one outdated doc is
    updated by Hanjun Guo.

    - Assorted ACPI updates

    We finally nailed down the IA-64 issue that was the reason for
    reverting commit 9f29ab11ddbf ("ACPI / scan: do not match drivers
    against objects having scan handlers"), so we can fix it and move
    the ACPI scan handler check added to the ACPI video driver back to
    the core.

    A mechanism for adding CMOS RTC address space handlers is
    introduced by Lan Tianyu to allow some EC-related breakage to be
    fixed on some systems.

    A spec-compliant implementation of acpi_os_get_timer() is added by
    Mika Westerberg.

    The evaluation of _STA is added to do_acpi_find_child() to avoid
    situations in which a pointer to a disabled device object is
    returned instead of an enabled one with the same _ADR value. From
    Jeff Wu.

    Intel BayTrail PCH (Platform Controller Hub) support is added to
    the ACPI driver for Intel Low-Power Subsystems (LPSS) and that
    driver is modified to work around a couple of known BIOS issues.
    Changes from Mika Westerberg and Heikki Krogerus.

    The EC driver is fixed by Vasiliy Kulikov to use get_user() and
    put_user() instead of dereferencing user space pointers blindly.

    Code cleanups are made by Bjorn Helgaas, Nicholas Mazzuca and Toshi
    Kani.

    - Assorted power management updates

    The "runtime idle" helper routine is changed to take the return
    values of the callbacks executed by it into account and to call
    rpm_suspend() if they return 0, which allows us to reduce the
    overall code bloat a bit (by dropping some code that's not
    necessary any more after that modification).

    The runtime PM documentation is updated by Alan Stern (to reflect
    the "runtime idle" behavior change).

    New trace points for PM QoS are added by Sahara
    ().

    PM QoS documentation is updated by Lan Tianyu.

    Code cleanups are made and minor issues are addressed by Bernie
    Thompson, Bjorn Helgaas, Julius Werner, and Shuah Khan.

    - devfreq updates

    New driver for the Exynos5-bus device from Abhilash Kesavan.

    Minor cleanups, fixes and MAINTAINERS update from MyungJoo Ham,
    Abhilash Kesavan, Paul Bolle, Rajagopal Venkat, and Wei Yongjun.

    - OMAP power management updates

    Adaptive Voltage Scaling (AVS) SmartReflex voltage control driver
    updates from Andrii Tseglytskyi and Nishanth Menon."

    * tag 'pm+acpi-3.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (162 commits)
    cpufreq: Fix cpufreq regression after suspend/resume
    ACPI / PM: Fix possible NULL pointer deref in acpi_pm_device_sleep_state()
    PM / Sleep: Warn about system time after resume with pm_trace
    cpufreq: don't leave stale policy pointer in cdbs->cur_policy
    acpi-cpufreq: Add new sysfs attribute freqdomain_cpus
    cpufreq: make sure frequency transitions are serialized
    ACPI: implement acpi_os_get_timer() according the spec
    ACPI / EC: Add HP Folio 13 to ec_dmi_table in order to skip DSDT scan
    ACPI: Add CMOS RTC Operation Region handler support
    ACPI / processor: Drop unused variable from processor_perflib.c
    cpufreq: tegra: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: s3c64xx: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: omap: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: imx6q: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: exynos: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: dbx500: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: davinci: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: arm-big-little: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: powernow-k8: call CPUFREQ_POSTCHANGE notfier in error cases
    cpufreq: pcc: call CPUFREQ_POSTCHANGE notfier in error cases
    ...

    Linus Torvalds
     
  • Pull GPIO updates from Linus Walleij:
    "Here is a batch of GPIO changes for v3.11. I have agreed with Grant
    to take care of the pull requests for this development cycle.

    No special things are happening in the GPIO tree this time (nice with
    some calm) and I have been extra careful to do regression builds and
    it's well boiled in -next.

    GPIO changes for the v3.11 development cycle:
    - Incremental development for the Langwell (Atom SoC), Xilinx, ICH
    and RCAR drivers.
    - Cleanups from Jingoo Han, Axel Lin, Wei Jongjun, Wolfram Sang,
    Tushar Behera, Sachin Kamat and Yijing Wang"

    * tag 'gpio-for-v3.11-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio: (35 commits)
    Gpio/trivial: replace numeric with standard PM state macros
    gpiolib: remove warnning of allocations with IRQs disabled
    gpio: grgpio: Staticize local symbols
    gpio-langwell: remove Withney point support
    gpio: ich: add GPO_BLINK support
    gpio-sta2x11: Convert to use devm_ioremap_resource
    gpio_msm: Convert to use devm_ioremap_resource
    gpio-rcar: Use OUTDT when reading GPIOs configured as output
    gpio-sta2x11: Fix potential NULL pointer dereference
    gpio/omap: omap_gpio_init_context stub must be inline
    gpio: msm-v1: Remove errant __devinit to fix compile
    gpio: devres: make comments proper
    GPIO: xilinx: Enable driver for Xilinx zynq
    DT: Add documentation for gpio-xilinx
    GPIO: xilinx: Use BIT macro
    GPIO: xilinx: Use __raw_readl/__raw_writel IO functions
    GPIO: xilinx: Add support for dual channel
    GPIO: xilinx: Simplify driver probe function
    gpio: sx150x: convert to use devm_* functions
    MAINTAINERS: add linux-gpio mailing list
    ...

    Linus Torvalds
     

03 Jul, 2013

5 commits

  • Pull core irq changes from Ingo Molnar:
    "The main changes:

    - generic-irqchip driver additions, cleanups and fixes

    - 3 new irqchip drivers: ARMv7-M NVIC, TB10x and Marvell Orion SoCs

    - irq_get_trigger_type() simplification and cross-arch cleanup

    - various cleanups, simplifications

    - documentation updates"

    * 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (26 commits)
    softirq: Use _RET_IP_
    genirq: Add the generic chip to the genirq docbook
    genirq: generic-chip: Export some irq_gc_ functions
    genirq: Fix can_request_irq() for IRQs without an action
    irqchip: exynos-combiner: Staticize combiner_init
    irqchip: Add support for ARMv7-M NVIC
    irqchip: Add TB10x interrupt controller driver
    irqdomain: Use irq_get_trigger_type() to get IRQ flags
    MIPS: octeon: Use irq_get_trigger_type() to get IRQ flags
    arm: orion: Use irq_get_trigger_type() to get IRQ flags
    mfd: stmpe: use irq_get_trigger_type() to get IRQ flags
    mfd: twl4030-irq: Use irq_get_trigger_type() to get IRQ flags
    gpio: mvebu: Use irq_get_trigger_type() to get IRQ flags
    genirq: Add irq_get_trigger_type() to get IRQ flags
    genirq: Irqchip: document gcflags arg of irq_alloc_domain_generic_chips
    genirq: Set irq thread to RT priority on creation
    irqchip: Add support for Marvell Orion SoCs
    genirq: Add kerneldoc for irq_disable.
    genirq: irqchip: Add mask to block out invalid irqs
    genirq: Generic chip: Add linear irq domain support
    ...

    Linus Torvalds
     
  • Pull ARM SoC driver specific changes from Arnd Bergmann:
    "These changes are all driver specific and cross over between arm-soc
    contents and some other subsystem, in these cases cpufreq, crypto,
    dma, pinctrl, mailbox and usb, and the subsystem owners agreed to have
    these changes merged through arm-soc.

    As we proceed to untangle the dependencies between platform code and
    driver code, the amount of changes in this category is fortunately
    shrinking, for 3.11 we have 16 branches here and 101 non-merge
    changesets, the majority of which are for the stedma40 dma engine
    driver used in the ux500 platform. Cleaning up that code touches
    multiple subsystems, but gets rid of the dependency in the end.

    The mailbox code moved out from mach-omap2 to drivers/mailbox is an
    intermediate step and is still omap specific at the moment. Patches
    exist to generalize the subsystem and add other drivers with the same
    API, but those did not make it for 3.11."

    * tag 'drivers-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (101 commits)
    crypto: ux500: use dmaengine_submit API
    crypto: ux500: use dmaengine_prep_slave_sg API
    crypto: ux500: use dmaengine_device_control API
    crypto: ux500/crypt: add missing __iomem qualifiers
    crypto: ux500/hash: add missing static qualifiers
    crypto: ux500/hash: use readl on iomem addresses
    dmaengine: ste_dma40: Declare memcpy config as static
    ARM: ux500: Remove mop500_snowball_ethernet_clock_enable()
    ARM: ux500: Correct the EN_3v3 regulator's on/off GPIO
    ARM: ux500: Provide a AB8500 GPIO Device Tree node
    gpio: rcar: fix gpio_rcar_of_table
    gpio-rcar: Remove #ifdef CONFIG_OF around OF-specific sections
    gpio-rcar: Reference core gpio documentation in the DT bindings
    clk: exynos5250: Add enum entries for divider clock of i2s1 and i2s2
    ARM: dts: Update Samsung I2S documentation
    ARM: dts: add clock provider information for i2s controllers in Exynos5250
    ARM: dts: add Exynos audio subsystem clock controller node
    clk: samsung: register audio subsystem clocks using common clock framework
    ARM: dts: use #include for all device trees for Samsung
    pinctrl: s3c24xx: use correct header for chained_irq functions
    ...

    Linus Torvalds
     
  • Pull ARM SoC specific changes from Arnd Bergmann:
    "These changes are all to SoC-specific code, a total of 33 branches on
    17 platforms were pulled into this. Like last time, Renesas sh-mobile
    is now the platform with the most changes, followed by OMAP and
    EXYNOS.

    Two new platforms, TI Keystone and Rockchips RK3xxx are added in this
    branch, both containing almost no platform specific code at all, since
    they are using generic subsystem interfaces for clocks, pinctrl,
    interrupts etc. The device drivers are getting merged through the
    respective subsystem maintainer trees.

    One more SoC (u300) is now multiplatform capable and several others
    (shmobile, exynos, msm, integrator, kirkwood, clps711x) are moving
    towards that goal with this series but need more work.

    Also noteworthy is the work on PCI here, which is traditionally part
    of the SoC specific code. With the changes done by Thomas Petazzoni,
    we can now more easily have PCI host controller drivers as loadable
    modules and keep them separate from the platform code in
    drivers/pci/host. This has already led to the discovery that three
    platforms (exynos, spear and imx) are actually using an identical PCIe
    host controller and will be able to share a driver once support for
    spear and imx is added."

    * tag 'soc-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (480 commits)
    ARM: integrator: let pciv3 use mem/premem from device tree
    ARM: integrator: set local side PCI addresses right
    ARM: dts: Add pcie controller node for exynos5440-ssdk5440
    ARM: dts: Add pcie controller node for Samsung EXYNOS5440 SoC
    ARM: EXYNOS: Enable PCIe support for Exynos5440
    pci: Add PCIe driver for Samsung Exynos
    ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data
    ARM: keystone: Move CPU bringup code to dedicated asm file
    ARM: multiplatform: always pick one CPU type
    ARM: imx: select syscon for IMX6SL
    ARM: keystone: select ARM_ERRATA_798181 only for SMP
    ARM: imx: Synertronixx scb9328 needs to select SOC_IMX1
    ARM: OMAP2+: AM43x: resolve SMP related build error
    dmaengine: edma: enable build for AM33XX
    ARM: edma: Add EDMA crossbar event mux support
    ARM: edma: Add DT and runtime PM support to the private EDMA API
    dmaengine: edma: Add TI EDMA device tree binding
    arm: add basic support for Rockchip RK3066a boards
    arm: add debug uarts for rockchip rk29xx and rk3xxx series
    arm: Add basic clocks for Rockchip rk3066a SoCs
    ...

    Linus Torvalds
     
  • Pull ARM SoC cleanups from Arnd Bergmann:
    "This contains cleanups as preparation for other branches adding new
    features, we pulled 16 branches for 9 platforms into this one.

    Most notable here is the removal of support for ATAGS based OMAP4
    systems. Since all OMAP4 machines are fully functional with DT based
    booting in 3.10, we can remove a lot of code here.

    Also noteworthy is Maxime Ripard's cleanup of the machine descriptors,
    which means we need no machine descriptors in a lot more cases and can
    boot additional machines by just having the respective device drivers
    enabled."

    * tag 'cleanup-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (76 commits)
    ARM: picoxcell: remove .nr_irqs reference
    ARM: s5p64x0: avoid build warning for uncompress.h
    ARM: SAMSUNG: Remove unused plat/regs-watchdog.h header
    ARM: SAMSUNG: Remove legacy watchdog reset code
    ARM: SAMSUNG: Let platforms use the new watchdog reset driver
    ARM: SAMSUNG: Add watchdog reset driver
    ARM: SAMSUNG: Use local definitions of watchdog registers
    watchdog: s3c2410_wdt: Use local register definitions
    ARM: S5P64X0: Use common uncompress.h part for plat-samsung
    ARM: SAMSUNG: Consolidate uncompress subroutine
    ARM: at91: drop rm9200dk board support
    ARM: dts: msm: Fix merge resolution
    ARM: OMAP1: Remove dma.h
    ARM: OMAP1: Remove legacy irda.h and irda setup from board files
    ARM: OMAP1: Remove duplicated DMA channel definitions
    ARM: OMAP1: Remove McBSP DMA channel definitions
    ARM: OMAP2+: Remove dma.h
    ARM: OMAP2+: hwmod: Remove remaining DMA channel definitions
    ARM: OMAP2+: Remove duplicated DMA channel definitions
    ARM: OMAP2+: Remove AES crypto device DMA channel definitions
    ...

    Linus Torvalds
     
  • …ernel/git/arm/arm-soc

    Pull ARM SoC non-cricitical bug fixes from Arnd Bergmann:
    "These are various bug fixes that were not considered important enough
    for merging into 3.10.

    The majority of the ARM fixes are for the OMAP and at91 platforms, and
    there is another set of bug fixes for device drivers that resolve
    'randconfig' build errors and that the subsystem maintainers either
    did not pick up or preferred to get merged through the arm-soc tree."

    * tag 'fixes-non-critical-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (43 commits)
    ARM: at91/PMC: use at91_usb_rate() for UTMI PLL
    ARM: at91/PMC: fix at91sam9n12 USB FS init
    ARM: at91/PMC: at91sam9n12 family has a PLLB
    ARM: at91/PMC: sama5d3 family doesn't have a PLLB
    ARM: tegra: fix section mismatch in tegra_pmc_parse_dt
    ARM: mxs: don't select HAVE_PWM
    ARM: mxs: stub out mxs_pm_init for !CONFIG_PM
    cpuidle: calxeda: select ARM_CPU_SUSPEND
    ARM: mvebu: fix length of ethernet registers in mv78260 dtsi
    ARM: at91: cpuidle: Fix target_residency
    ARM: at91: fix at91_extern_irq usage for non-dt boards
    ARM: sirf: use CONFIG_SIRF rather than CONFIG_PRIMA2 where necessary
    clocksource: kona: adapt to CLOCKSOURCE_OF_DECLARE change
    X.509: do not emit any informational output
    mtd: omap2: allow bulding as a module
    [SCSI] nsp32: use mdelay instead of large udelay constants
    hwrng: bcm2835: fix MODULE_LICENSE tag
    ARM: at91: Change the internal SRAM memory type MT_MEMORY_NONCACHED
    ARM: at91: Fix link breakage when !CONFIG_PHYLIB
    MAINTAINERS: Add exynos filename match to ARM/S5P EXYNOS ARM ARCHITECTURES
    ...

    Linus Torvalds
     

30 Jun, 2013

1 commit


26 Jun, 2013

1 commit

  • Commit ede4d7a5 ("gpio/omap: convert gpio irq domain to linear mapping")
    converted the OMAP GPIO driver to use a linear mapping for the GPIO IRQ
    domain instead of using a legacy mapping. Not using a legacy mapping has
    a number of benefits but it requires the platform to support SPARSE_IRQ
    which currently is not supported on OMAP1.

    So this change caused a regression on OMAP1 platforms [1].

    Since this issue is not present on all OMAP2+ platforms, there is no need to
    revert the driver to use legacy domain mapping for all the platforms.

    [1]: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg89005.html

    Signed-off-by: Javier Martinez Canillas
    Tested-by: Aaro Koskinen
    Signed-off-by: Tony Lindgren

    Javier Martinez Canillas
     

25 Jun, 2013

1 commit

  • Use irq_get_trigger_type() to get the IRQ trigger type flags
    instead calling irqd_get_trigger_type(irq_get_irq_data(irq))

    Signed-off-by: Javier Martinez Canillas
    Acked-by: Grant Likely
    Cc: Linus Walleij
    Cc: Samuel Ortiz
    Acked-by: Jason Cooper
    Cc: Andrew Lunn
    Cc: Russell King
    Cc: Ralf Baechle
    Cc: Benjamin Herrenschmidt
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-mips@linux-mips.org
    Link: http://lkml.kernel.org/r/1371228049-27080-3-git-send-email-javier.martinez@collabora.co.uk
    Signed-off-by: Thomas Gleixner

    Javier Martinez Canillas
     

21 Jun, 2013

2 commits

  • …ernel/git/horms/renesas into next/drivers

    From Simon Horman:

    Second Round of Renesas ARM based SoC GPIO R-Car updates for v3.11

    Documentation enhancement and code cleanup by Laurent Pinchart.

    * tag 'renesas-gpio-rcar2-for-v3.11' of git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas:
    gpio-rcar: Remove #ifdef CONFIG_OF around OF-specific sections
    gpio-rcar: Reference core gpio documentation in the DT bindings

    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

    Arnd Bergmann
     
  • …it/kgene/linux-samsung into next/soc

    From Kukjin Kim:

    cleanup and removing dead code for only support DT for exynos
    - remove board file for exynos
    - remove legacy files which are not used anymore
    - decouple ARCH_EXYNOS from PLAT_S5P

    * tag 'remove-nondt-exynos-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung: (35 commits)
    ARM: EXYNOS: Remove remaining dead code after non-DT support removal
    ARM: EXYNOS: Remove legacy L2X0 initialization
    ARM: EXYNOS: Use exynos_init_io() as map_io callback
    ARM: EXYNOS: Remove custom init_irq callbacks
    ARM: EXYNOS: Remove mach/regs-usb-phy.h header
    thermal: exynos: Support both EXYNOS4X12 SoCs
    ARM: EXYNOS: Remove unused base addresses from mach/map.h header
    ARM: EXYNOS: Remove mach/irqs.h header
    ARM: EXYNOS: Select SPARSE_IRQ for Exynos
    ARM: SAMSUNG: Make legacy MFC support code depend on SAMSUNG_ATAGS
    ARM: EXYNOS: Remove mach/regs-gpio.h header
    ARM: EXYNOS: Remove mach/gpio.h
    ARM: EXYNOS: Remove setup-i2c0.c
    ARM: EXYNOS: Do not select legacy Kconfig symbols any more
    ARM: SAMSUNG: Include most of mach/ headers conditionally
    ARM: EXYNOS: Decouple ARCH_EXYNOS from PLAT_S5P
    USB: Check for ARCH_EXYNOS separately
    platform: Check for ARCH_EXYNOS separately
    ARM: SAMSUNG: Compile legacy IRQ and GPIO PM code only with ATAGS support
    ARM: EXYNOS: Provide compatibility stubs for PM code in pm-core.h header
    ...

    Conflicts:
    arch/arm/mach-exynos/Kconfig

    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

    Arnd Bergmann
     

20 Jun, 2013

4 commits


19 Jun, 2013

3 commits


17 Jun, 2013

12 commits


15 Jun, 2013

1 commit

  • …t/davidb/linux-msm into next/cleanup

    From David Brown:
    Cleanups for MSM for 3.11

    These are a handful of cleanups to the MSM tree. The gpio cleanups
    get us closer to having proper pinmux and gpio support.

    * tag 'msm-cleanup-for-3.11' of git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm:
    mfd: ssbi: Use devm_* and simplify code
    gpio: msm: Add device tree and irqdomain support for gpio-msm-v2
    ARM: msm: Remove gpiomux-v2 and re-organize MSM_GPIOMUX configs
    msm: iomap: Remove unused bases and mappings
    msm: Remove unused file core.h
    ARM: msm: Remove init_irq declaration in machine description

    Signed-off-by: Olof Johansson <olof@lixom.net>

    Conflicts:
    arch/arm/boot/dts/msm8660-surf.dts
    arch/arm/boot/dts/msm8960-cdp.dts

    Olof Johansson