20 Jul, 2016

1 commit


05 May, 2016

1 commit


26 Apr, 2016

2 commits


14 Jan, 2016

2 commits


08 Jan, 2016

1 commit


07 Jan, 2016

1 commit


14 Nov, 2015

1 commit


16 Sep, 2015

2 commits


11 Sep, 2015

1 commit

  • WAKEUP2 is used as a gpio input for the touch screen controller's interrupt
    output signal. It was incorrect to set it as an output in the first place.

    This is valid for both the OSD panel that uses the EDT FT5506 touchscreen
    controller and the LG panel that uses the LDC3001 touchscreen controller.

    Signed-off-by: Franklin S Cooper Jr
    Signed-off-by: Dan Murphy

    Franklin Cooper
     

13 Aug, 2015

2 commits

  • DP83865 ethernet phy used on DRA74x-evm is quirky and the datasheet
    provided IODELAY values for standard RGMII phys do not work.

    Silicon Revision(SR) 2.0 provides an alternative bit configuration
    that allows us to do a "gross adjustment" to launch the data off a
    different internal clock edge. Manual IO Delay overrides are still
    necessary to fine tune the clock-to-data delays. This is a necessary
    workaround for the quirky ethernet Phy we have on the platform.

    NOTE: SMA registers are spare "kitchen sink" registers that does
    contain bits for other workaround as necessary as well. Hence the
    control for the same is introduced in a generic SoC specific, board
    generic location.

    Signed-off-by: Nishanth Menon

    Nishanth Menon
     
  • Silicon revision 2.0 has new signal routing hence has an updated set of
    iodelay parameters to be used. Update the configuration for the same.
    Padmux remains the same.

    Based on data from VayuES2_EVM_Base_Config-20150807.

    NOTE: With respect to the RGMII values, the Manual IODelay values
    are used for the fine adjusments needed to meet the tight RGMII
    specification.

    Signed-off-by: Nishanth Menon

    Nishanth Menon
     

12 Aug, 2015

2 commits

  • ARM supported speeds and init value of core_pll for SDP1200
    are programmed wrong as part for the device speed cleanups.
    Fixing it here.

    Signed-off-by: Lokesh Vutla

    Lokesh Vutla
     
  • On keystone2 Lamarr and Edison platforms, the PA clocksource
    mux in PLL REG1, can be changed only after enabling its clock
    domain.
    So selecting the output of PASS PLL as input to PA only after
    enabling the clockdomain.
    This is as per the debug done by "Vitaly Andrianov "
    and based on the previous work done by "Hao Zhang "

    Fixes: d634a0775bcf ("ARM: keystone2: Cleanup PLL init code")
    Reported-by: Vitaly Andrianov
    Tested-by: Vitaly Andrianov
    Signed-off-by: Lokesh Vutla

    Lokesh Vutla
     

07 Aug, 2015

6 commits


05 Aug, 2015

15 commits


04 Aug, 2015

2 commits

  • Kernel stores information to the RTC_SCRATCH0 and RTC_SCRATCH1 registers
    for wakeup from RTC-only mode. Parse these registers during SPL boot and
    jump to the kernel resume vector if the device is waking up from RTC-only
    mode.

    The RTC scratch register layout used is:

    SCRATCH0 : bits00-31 : kernel resume address
    SCRATCH1 : bits00-15 : RTC magic value used to detect valid config
    SCRATCH1 : bits16-31 : board type information populated by bootloader

    During the normal boot patch the SCRATCH1 : bits16-31 are updated with
    the eeprom read board type data. In the rtc_only boot path the rtc
    scratchpad register is read and the board type is determined and
    correspondingly ddr dpll parameters are set. This is done so as to avoid
    costly i2c read to eeprom.

    RTC-only mode support is currently only enabled for
    am43xx_evm_rtconly_config.
    This is not to be used with epos evm builds.

    Signed-off-by: Tero Kristo
    [j-keerthy@ti.com] Ported to latest branch with minor fixes
    Signed-off-by: Keerthy
    Signed-off-by: Lokesh Vutla

    From: Tero Kristo
     
  • KS2_RSTCTRL_RSTYPE is defined as KS2_PLL_CNTRL_BASE + offset.
    But ddr driver reads KS2_PLL_CNTRL_BASE + KS2_RSTCTRL_RSTYPE
    for detecting reset type, which gives a wrong reset type.
    Fixing it by just reading KS2_RSTCTRL_RSTYPE.

    Reviewed-by: Vitaly Andrianov
    Signed-off-by: Lokesh Vutla

    Lokesh Vutla
     

30 Jul, 2015

1 commit

  • Because KS2 u-boot works in 32 bit address space the existing ram_size
    global data field cannot be used. The maximum, which the get_ram_size()
    can detect is 2GB only. The ft_board_setup() needs the actual ddr3 size
    to fix up dtb.

    This commit introduces the ddr3_get_size() which uses SPD data to
    calculate the ddr3 size. This function replaces the "ddr3_size"
    environment variable, which was used to get the SODIMM size.

    For platforms, which don't have SODIMM with SPD and ddr3 is populated to
    a board a simple ddr3_get_size function that returns ddr3 size has to be
    implemented. See hardware-k2l.h

    Signed-off-by: Vitaly Andrianov

    Vitaly Andrianov