Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Mar 1, 2012
  1. ARM: OMAP3+: am33xx_hwmod: Remove gpmc_hwmod entry

    Vaibhav Hiremath authored
    Presense of gpmc_hwmod leads to kernel crash,
      - Base address and irq no is hardcoded in code
      - GPMC driver is not migrated to platform_device driver
  2. ARM: OMAP2+: hwmod: Fix wrong SYSC_TYPE1_XXX_MASK bit definations

    Vaibhav Hiremath authored
    In the SYSC_TYPE1_XXX_MASK configuration, SYSC_XXX_SHIFT macro
    is used which is not defined anywhere in the kernel.
    The build was going through since it is not being used anywhere
    till now.
    
    This bug got introduced by the commit
    358f0e6 ("OMAP3: hwmod: support
    to specify the offset position of various SYSCONFIG register bits.")
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  3. ARM: OMAP2+: hwmod: Add new sysc_type3 into omap_hwmod required for a…

    Vaibhav Hiremath authored
    …m33xx
    
    In case of AM33xx family of devices (like cpsw) have different sysc
    bit field offsets defined,
    
    sysc_type3:
    |  3     2  |  1    0  |
    | STDBYMODE | IDLEMODE |
    
    So introduce new sysc_type3 in omap_hwmod common data.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Signed-off-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
  4. ARM: OMAP: am33xx: Skip parts where cpu_is_omap34xx() is true but NA …

    Afzal Mohammed authored Vaibhav Hiremath committed
    …for AM33XX
    
    Add an explicit check for cpu_is_am33xx() to prevent the block inside
    cpu_is_omap34xx() from executing which would otherwise fail/cause
    aborts on AM33XX.
    
    Signed-off-by: Afzal Mohammed <afzal@ti.com>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  5. ARM: OMAP: am33xx-hwmod: Add HWMOD data

    Vaibhav Hiremath authored
    This patch adds HWMOD data for all the peripherals of AM335X and
    also hooks up to the existing OMAP framework.
    
    Signed-off-by: Afzal Mohammed <afzal@ti.com>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Signed-off-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Paul Walmsley <paul@pwsan.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
  6. ARM: OMAP: am33xx: Add Clock & clockdomain data

    Vaibhav Hiremath authored
    This patch adds support for AM33XX clock & clock domain data,
    corresponding API's to access CM module and
    CM register offsets & bit fields.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Signed-off-by: Afzal Mohammed <afzal@ti.com>
    Signed-off-by: Rachna Patil <rachna@ti.com>
    Signed-off-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
    CC: Tony Lindgren <tony@atomide.com>
    Cc: Paul Walmsley <paul@pwsan.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
  7. @VaibhavBedia-xx

    ARM: OMAP3+: dpll: Configure autoidle mode only if its supported

    VaibhavBedia-xx authored Vaibhav Hiremath committed
    The current DPLL code enables and disables autoidle features
    without checking whether the autoidle register is available.
    Fix this by putting a check for the existence of the autoidle
    register in the DPLL data.
    
    With such a check in place, for DPLLs which do not support this
    feature, simply skipping the autoidle_reg entry in the DPLL data
    is sufficient.
    
    Signed-off-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
  8. ARM: OMAP: id: Add missing break statement in omap3xxx_check_revision

    Vaibhav Hiremath authored
    Add missing break statement, which somehow got removed from
    omap3xxx_check_revision function inside AM335x switch case,
    resulting into wrong omap/cpu_rev configuration.
  9. ARM: OMAP2+: hwmod data: Add 32k-sync timer data to hwmod database

    Vaibhav Hiremath authored
    Add 32k-sync timer hwmod data to omap2 & 3 hwmod table
    and also enable existing hwmod data for omap4 (was disabled before).
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Signed-off-by: Felipe Balbi <balbi@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Paul Walmsley <paul@pwsan.com>
  10. ARM: OMAP2/3: Add idle_st bits for ST_32KSYNC timer to prcm-common he…

    Vaibhav Hiremath authored
    …ader
    
    Add missing idle_st bit for 32k-sync timer into the prcm-common
    header file, required for hwmod data.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Felipe Balbi <balbi@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Paul Walmsley <paul@pwsan.com>
  11. ARM: OMAP2+: 32k-counter: Use hwmod lookup to check presence of 32k t…

    Vaibhav Hiremath authored
    …imer
    
    OMAP device has 32k-sync timer which is currently used as a
    clocksource in the kernel (omap2plus_defconfig).
    The current implementation uses compile time selection between
    gp-timer and 32k-sync timer, which breaks multi-omap build for
    the devices like AM33xx, where 32k-sync timer is not available.
    
    So use hwmod database lookup mechanism, through which at run-time
    we can identify availability of 32k-sync timer on the device,
    else fall back to gp-timer.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Signed-off-by: Felipe Balbi <balbi@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Paul Walmsley <paul@pwsan.com>
    Cc: Tarun Kanti DebBarma <tarun.kanti@ti.com>
  12. ARM: OMAP: am33xx: Hook-up am33xx support to existing cm code

    Vaibhav Hiremath authored
    Reuse existing omap4 cminst code for am33xx device,
    add separate cm base table for am33xx device and initialize
    it during __init for future use.
    
    Also, since cpu_is_omap34xx() check is true for am33xx family of
    devices, we must change the order of cpu_is_xxxx check, so first
    check for cpu_is_am33xx() to follow right execution path.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
    CC: Tony Lindgren <tony@atomide.com>
    Cc: Paul Walmsley <paul@pwsan.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
  13. ARM: OMAP4: cminst: Add boot time __init function for cminst

    Vaibhav Hiremath authored
    AM33xx CM module is closer to OMAP4 CM module, and
    in order to reuse cminst api's we have to address
    some of the differences like, base addresses and partitions.
    Unlike OMAP4 CM, AM33xx doesn't have any partitions and
    maintains only single partition.
    
    So, in order to reuse the existing OMAP4 cminst code
    for AM33xx this patch adds,
    
      - Boot time __init function, to initialize _cm_bases
        based on cpu_is_xxx
      - Instead of maintaining phy addr for CM partition
        in _cm_bases[] table and then changing it to virt addr,
        directly maintain respective virt addr.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
    CC: Tony Lindgren <tony@atomide.com>
    Cc: Paul Walmsley <paul@pwsan.com>
  14. ARM: OMAP: am33xx: Hook-up am33xx support to existing prm code

    Vaibhav Hiremath authored
    Reuse existing omap4 prminst code for am33xx device,
    add separate prm base table for am33xx device and initialize
    it during __init for future use.
    
    Also, since cpu_is_omap34xx() check is true for am33xx family of
    devices, we must change the order of cpu_is_xxxx check, so first
    check for cpu_is_am33xx() to follow right execution path.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
    CC: Tony Lindgren <tony@atomide.com>
    Cc: Paul Walmsley <paul@pwsan.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
  15. ARM: OMAP4: prminst: Add boot time __init function for prminst

    Vaibhav Hiremath authored
    AM33xx PRM module is closer to OMAP4 PRM module, and
    in order to reuse prminst api's we have to address
    some of the differences like, base addresses and partitions.
    Unlike OMAP4 PRM, AM33xx doesn't have any partitions and
    maintains single partition.
    
    So, in order to reuse the existing OMAP4 prminst code
    for AM33xx this patch adds,
    
      - Boot time __init function, to initialize _prm_bases
        based on cpu_is_xxx
      - Instead of maintaining phy addr for PRM partition
        in _prm_bases[] table and then changing it to virt addr,
        directly maintain respective virt addr.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
    CC: Tony Lindgren <tony@atomide.com>
  16. ARM: OMAP4: Remove hardcoded reg-offs for PWRSTCTRL & PWRSTST

    Vaibhav Hiremath authored
    This patch removes the existing hard-coded way of providing
    offset to omap4_prminst_xxx API's and instead use offsets
    provided in powerdomainsxxxx_data.
    
    Very much required for the new device AM33XX, where,
    
    PRM module in AM33XX is closer to OMAP4 PRM module, so it makes
    complete sense to reuse all the code from existing OMAP4 implementation.
    Having said that, there is a catch here with respect to AM33XX device,
    
    The register offset in PRM module is not consistent
    across (crazy IP integration), for example,
    
    PRM_XXX         PWRSTCTRL PWRSTST RSTCTRL RSTST
    ===============================================
    PRM_PER_MOD:    0x0C,     0x08,   0x00,   0x04
    PRM_WKUP_MOD:   0x04,     0x08,   0x00,   0x0C
    PRM_MPU_MOD:    0x00,     0x04,   0x08,   NA
    PRM_DEVICE_MOD: NA,       NA,     0x00,   0x08
    
    So in order to reuse the existing OMAP4 code, we have to add
    seperate entry for register offsets, especially
    PWRSTCTRL & PWRSTST.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Paul Walmsley <paul@pwsan.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    
    Merge to "Remove-hardcoded-reg-offs-for-PWRSTCT"
  17. ARM: OMAP: am33xx: Add control reg macro in control.h

    Vaibhav Hiremath authored
  18. ARM: OMAP: am33xx: Add power domain data

    Vaibhav Hiremath authored
    This patch adds AM33XX power domain data (powerdomains33xx_data.c),
    header files consisting PRM register offsets & bit fields and
    reusing all OMAP4 API's to access PRM module.
    
    Also, hook up AM33XX power domain to OMAP framework.
    
    This patch is based on OMAP4 cleanup patch of hardcoded reg-offs for
    PWRSTCTRL & PWRSTST.
    Patch -
    http://www.mail-archive.com/linux-omap@vger.kernel.org/msg60468.html
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Signed-off-by: Afzal Mohammed <afzal@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Paul Walmsley <paul@pwsan.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
  19. ARM: OMAP: am33xx: Add voltage domain data

    Vaibhav Hiremath authored
    Currently dummy voltage domain data is being created
    in order to succeed boot process.
    Nothing has been done w.r.t actual hardware (voltage control).
    
    Also, hook up AM33XX voltage domain to OMAP framework.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Signed-off-by: Afzal Mohammed <afzal@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Paul Walmsley <paul@pwsan.com>
    Cc: Rajendra Nayak <rnayak@ti.com>
  20. arm/dts: OMAP3: Add omap3evm and am335xevm support

    Vaibhav Hiremath authored
    TI's OMAP3EVM and AM335xEVM are software development boards
    available for OMAP35x(AM/DM37x) and AM335x devices respectively;
    and these devices are considered under omap3 family.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  21. arm/dts: Add support for TI AM335x EVM board

    Vaibhav Hiremath authored
    Add AM335x EVM DTS file to use the omap3.dtsi SoC file,
    along with memory node and i2c information.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Grant Likely <grant.likely@secretlab.ca>
  22. arm:omap2:board-generic: Add DT support for AM33xx devices

    Vaibhav Hiremath authored
    Although we consider am33xx device under omap34xx family of devices,
    there is indeed difference between them, for example,
    
          - Initial required mapping (->map_io)
          - Early init (->init_early)
    	Here, the whole sequence/data is different than omap3,
    	For example, clock/hwmod/power/voltage data.
          - clock event/source timer (name and instances)
    
    So, this patch adds seperate machine descriptor for AM33XX family
    of devices.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    CC: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
  23. arm/dts: Add support for TI AM3517/05 EVM board

    Vaibhav Hiremath authored
    Add AM3517 EVM (AM3517/05) DTS file to use the omap3.dtsi SoC file,
    along with memory node and i2c information.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Grant Likely <grant.likely@secretlab.ca>
  24. arm/dts: omap3-evm: Add i2c and twl4030 support

    Vaibhav Hiremath authored
    Add support for TWL4030, which is interfaced on i2c1 bus.
    Also add clock frequencies for other i2c instances(2 & 3)
    required for client-device exist on OMAP3EVM board.
    
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
    Cc: Benoit Cousson <b-cousson@ti.com>
    Cc: Grant Likely <grant.likely@secretlab.ca>
    Cc: Tony Lindgren <tony@atomide.com>
  25. @bcousson

    ARM: OMAP2+: board-generic: Remove i2c static init

    bcousson authored Vaibhav Hiremath committed
    This mainly reverts the commit that was adding the i2c static init.
    
    Since the i2c and twl nodes are now present, there is no need
    for the static initialization anymore.
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  26. @bcousson

    arm/dts: omap3-beagle: Add twl4030 and i2c EEPROM

    bcousson authored Vaibhav Hiremath committed
    Add required clock frequencies for the i2c client devices existing
    on beagle board.
    
    Add the twl4030 basic description with only the twl_rtc module.
    
    Add the EEPROM node.
    
    Based on original patch from Manju:
    http://www.spinics.net/lists/linux-omap/msg55831.html
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  27. @bcousson

    arm/dts: omap4-sdp: Add twl6030, i2c3 and i2c4 devices

    bcousson authored Vaibhav Hiremath committed
    Update DTS file with required clock frequencies
    for the i2c client devices existing on sdp4430.
    
    Add the twl6030 node inside the i2c1 controller node.
    This is the minimal support needed to boot OMAP4 boards
    without any crash.
    The support for all the features included in this MFD will be
    added later.
    
    Add the RTC submodule inside the twl node.
    
    Add tmp105 temperature sensor in i2c3
    Add bh1780 Ambient Light Sensor in i2c3
    Add hmc5843 3-Axis Digital Compass in i2c4
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  28. @bcousson

    arm/dts: omap4-panda: Add twl6030 and i2c EEPROM

    bcousson authored Vaibhav Hiremath committed
    Update pandaboard dts file with required clock frequencies
    for the i2c client devices existing on pandaboard.
    
    Add the twl6030 node in i2c1 controller.
    
    This is the minimal support needed to boot OMAP4 boards
    without any crash.
    The support for all the features included in this MFD will be
    added later.
    
    Add a generic i2c EEPROM entry.
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  29. @bcousson

    arm/dts: twl4030: Add DTS file for twl4030 PM + Audio IC

    bcousson authored Vaibhav Hiremath committed
    Add a dedicated DTS file for the twl4030/5030 Power + Audio IC.
    This chip is a big SoC that will be reused in a lot of various
    OMAP3 boards.
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  30. @bcousson

    arm/dts: twl6030: Add DTS file for twl6030 PMIC

    bcousson authored Vaibhav Hiremath committed
    Add a dedicated DTS file for the twl6030 Power IC.
    This chip is a big SoC that will be reused in a lot of various
    OMAP4+ boards.
    
    Note: This file is supposed to be included in a board DTS that will
    create the twl node in order to allow the &twl reference to work.
    
    Exmaple:
    ...
    &i2c1 {
        twl: twl@48 {
            reg = <0x48>;
            interrupts = <0 7 4>;
            interrupt-controller;
            interrupt-parent = <&gic>;
        };
    };
    
    /include/ "twl6030.dtsi"
    ...
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  31. @bcousson

    arm/dts: OMAP3: Add i2c controller nodes

    bcousson authored Vaibhav Hiremath committed
    Add i2c controllers nodes into the main ocp bus.
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  32. @bcousson

    ARM: OMAP2+: board-generic: Use of_irq_init API

    bcousson authored Vaibhav Hiremath committed
    Use the of_irq_init API introduced in 3.2 to handle
    interrupt-controller with DT.
    Update the irq_match table to map the proper XXX_of_init
    functions for INTC and GIC drivers.
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  33. @bcousson

    arm/dts: OMAP3: Add interrupt-controller bindings for INTC

    bcousson authored Vaibhav Hiremath committed
    Update the DTS with the proper information required by the
    INTC bindings.
    
    - Add the number of interrupt lines
    - Add the reg and the compatible entries.
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  34. @bcousson

    ARM: OMAP2/3: intc: Add DT support for TI interrupt controller

    bcousson authored Vaibhav Hiremath committed
    Add a function to initialize the OMAP2/3 interrupt controller (INTC)
    using a device tree node.
    
    Replace some printk() with the proper pr_ macro.
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
  35. @bcousson

    ARM: OMAP2/3: intc: Add irqdomain support

    bcousson authored Vaibhav Hiremath committed
    Introduce the usage of the irqdomain to prepare the DT support.
    The irq_base is still hard coded to 0 to allow non-DT drivers
    to work with the previous assumption that was hwirq = irq.
    
    Signed-off-by: Benoit Cousson <b-cousson@ti.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Acked-by: Rob Herring <rob.herring@calxeda.com>
    Acked-by: Grant Likely <grant.likely@secretlab.ca>
    Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Something went wrong with that request. Please try again.