25 Jan, 2012

1 commit

  • Default timing causes issues with OOB data corruption on reading and
    causes UBIFS torture test. To resolve the above issue, NAND was tested
    with different timings and optimal timings were adapted after repeated
    tests and trials.

    Signed-off-by: Philip, Avinash

    Philip, Avinash
     

22 Dec, 2011

1 commit

  • LCDC functional clock may or may not be derived from CPU/MPU DPLL,
    For example,
    AM335x => Separate independent DPLL for LCDC
    Davinci => Same DPLL as MPU

    So, on platforms where LCDC functional clock is not derived from CPU/MPU
    PLL it is not required to reset LCDC module as its functional clock does
    not change with DVFS.

    This patch adds check to do reset only if functional clock changes
    between pre and post notifier callbacks with DVFS.

    Signed-off-by: Manjunathappa, Prakash

    Manjunathappa, Prakash
     

16 Dec, 2011

1 commit


13 Dec, 2011

3 commits


12 Dec, 2011

2 commits


06 Dec, 2011

3 commits


01 Dec, 2011

12 commits


30 Nov, 2011

17 commits

  • TPS65910 VDD1 SMPS is connected to MPU.
    Add dummy entries for other regulators.

    TODO: Replace dummy regulator entries
    with proper ones as required.

    Signed-off-by: Afzal Mohammed

    Afzal Mohammed
     
  • MPU voltage domain data added. Also added
    OPP table for MPU voltage domain.

    OPP table for CORE voltage domain has not been
    added as there were issues upon reducing CORE
    voltage, hence no dependency has been defined
    for MPU.

    Signed-off-by: Afzal Mohammed

    Afzal Mohammed
     
  • Jitter correction for AM33XX is not present.
    Handle revelant clock API's properly.

    Signed-off-by: Afzal Mohammed

    Vaibhav Bedia
     
  • Signed-off-by: Vaibhav Bedia

    Vaibhav Bedia
     
  • Initialize voltage to be as per OPP

    Signed-off-by: Vaibhav Bedia
    Signed-off-by: Afzal Mohammed

    Vaibhav Bedia
     
  • Replace clk_set_rate with omap_device_scale
    in target function. This provides the ability
    to change voltage as well as frequency as per
    OPP tables

    Signed-off-by: Afzal Mohammed

    Afzal Mohammed
     
  • TI processors in TI81x and AM33x family work with PMICs like
    TPS65910/1 which are not part of the TWL series. These processors
    also do not have a voltage controller/processor module.

    In order to invoke the normal regulator calls from the voltage
    layer the following changes are done to struct voltagedomain
    - Add a flag use_regulator for the SoC voltagedomain
    code to indicate its intention of using a PMIC which
    is not controlled by VC/VP
    - Add a regulator_init callback which the platform code
    can utilise for any custom init sequence before making
    use of the regulator. Platform code is also expected
    to set the voltdm->scale function in the init callback

    Signed-off-by: Ravikumar Kattekola
    Signed-off-by: Vaibhav Bedia

    Vaibhav Bedia
     
  • Most clock rates can vary to some extent based on the exact
    M/N values used to lock a dpll.
    Do a round_rate before updating the rates into the OPP table
    so that the 'exact' rates appear and a subsequent clk_set_rate
    works without issues.

    Signed-off-by: Rajendra Nayak
    Signed-off-by: Nishanth Menon
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia
    Signed-off-by: Afzal Mohammed

    Rajendra Nayak
     
  • Ensure that PM initializations are all ready before we proceed.

    This allows drivers such as gfx, cpufreq which are ready earlier
    than pm to not not attempt to use the scaling infrastructure before
    it is ready.

    Signed-off-by: Nishanth Menon
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia

    Nishanth Menon
     
  • Make DVFS to try the next available frequency if the higher match
    is not available. This will probably be the max available for the device.

    If we cannot match any thing at all, fail. This modifies the behavior
    of device scale to guarenteeing _atleast_ the frequency requested into
    _if possible_, the frequency requested.

    Signed-off-by: Girish S G
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia

    Girish S G
     
  • Provide mechanism to know if DVFS is scaling on a specific domain.
    This API will allow us to detect transition and take appropriate
    measures in idle path

    Acked-by: Todd Poynor
    Acked-by: Santosh Shilimkar
    Signed-off-by: Nishanth Menon
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia

    Nishanth Menon
     
  • Ability to show the dependency table helps debug some of the quirky
    issues associated with dvfs when multiple device requests are present

    [nm@ti.com: log beautification, few fixes]
    Signed-off-by: Nishanth Menon
    Signed-off-by: Todd Poynor
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia

    Todd Poynor
     
  • Let omap_init_opp_table run through all the OPP's instead of
    returning on seeing the first invalid one. Skip the invalid ones
    and give a fair chance to the rest to get registered,
    if they are found to be valid.
    For every invalid entry in the OPP table, instead of a pr_warn,
    do a WARN so it gets the attention it needs.

    Signed-off-by: Rajendra Nayak
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia

    Rajendra Nayak
     
  • Allocating dvfs_info for every device instead of doing it
    for every voltage domain causes devices registered using
    omap_dvfs_register_device() to disappear.

    Signed-off-by: Rajendra Nayak
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia

    Rajendra Nayak
     
  • dvfs.h is required by omap cpufreq driver that
    lives in drivers folder, so move it to plat/
    directory. Also move voltage.h, vc.h & vp.h
    similarly to have clean header file inclusions

    Signed-off-by: Afzal Mohammed

    Afzal Mohammed
     
  • Register DVFS entries per opp entry to capture all
    scalable domain devices.

    Signed-off-by: Nishanth Menon
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia

    Nishanth Menon
     
  • With hwmods, ideally, we should have been able to do:
    pdm = omap_hwmod_get_pwrdm(oh);
    voltdm = pwrdm_get_voltdm(pdm);
    clk = clk_get(oh->main_clk);

    Unfortunately hwmod database is'nt mature enough yet to handle
    silicon variance within the same family, e.g. 4430 Vs 4460.
    So we explicitly map the domain and clk names within the OPP
    entries. This allows us to scale by having a central location for
    the registration.

    IMPORTANT NOTE: we probably will need to fix core and iva clk
    setting.

    Signed-off-by: Nishanth Menon
    Signed-off-by: Vishwanath BS
    [vaibhav.bedia@ti.com: Pull in for AM33xx]
    Signed-off-by: Vaibhav Bedia

    Nishanth Menon