09 Jan, 2016

5 commits


24 Dec, 2015

2 commits

  • TI-Feature: ti_linux_base_lsk
    TI-Tree: git@git.ti.com:ti-linux-kernel/ti-linux-kernel.git
    TI-Branch: ti-linux-4.1.y

    * 'ti-linux-4.1.y' of git.ti.com:ti-linux-kernel/ti-linux-kernel:
    net: netcp: remove obsolete driver code
    phy: keystone: update header of the file
    phy: keystone: remove comments per vendor recommendation
    ARM: dts: keystone: enable gbe serdes support
    phy: keystone: change function names per vendor recommendation
    phy: keystone: rename data structures based on vendor recommendation
    phy: keystone: reduce one level of nesting in the function call
    phy: keystone: remove hyperlink support
    phy: keystone: update comments per IP vendor recommendation

    Signed-off-by: LCPD Auto Merger

    LCPD Auto Merger
     
  • …gration-tree/connectivity-ti-linux-kernel into ti-linux-4.1.y

    TI-Feature: connectivity
    TI-Tree: git://git.ti.com/connectivity-integration-tree/connectivity-ti-linux-kernel.git
    TI-Branch: connectivity-ti-linux-4.1.y

    * 'connectivity-ti-linux-4.1.y' of git://git.ti.com/connectivity-integration-tree/connectivity-ti-linux-kernel:
    net: netcp: remove obsolete driver code
    phy: keystone: update header of the file
    phy: keystone: remove comments per vendor recommendation
    ARM: dts: keystone: enable gbe serdes support
    phy: keystone: change function names per vendor recommendation
    phy: keystone: rename data structures based on vendor recommendation
    phy: keystone: reduce one level of nesting in the function call
    phy: keystone: remove hyperlink support
    phy: keystone: update comments per IP vendor recommendation

    Signed-off-by: Dan Murphy <DMurphy@ti.com>

    Dan Murphy
     

23 Dec, 2015

3 commits


10 Dec, 2015

5 commits


05 Dec, 2015

10 commits

  • TI-Feature: ti_linux_base_lsk
    TI-Tree: git@git.ti.com:ti-linux-kernel/ti-linux-kernel.git
    TI-Branch: ti-linux-4.1.y

    * 'ti-linux-4.1.y' of git.ti.com:ti-linux-kernel/ti-linux-kernel:
    remoteproc/keystone: ensure the DSPs are in reset in probe
    TEMP: ARM: dts: k2g-evm: Reserve some DDR for MPM usecases
    ARM: dts: k2g-evm: Add a common DSP shared memory CMA pool
    TEMP: ARM: dts: k2g-evm: Add dspmem node
    ARM: dts: k2g: Add DSP node
    remoteproc/keystone: add support for Keystone 2 Galileo SOCs
    remoteproc/keystone: drop ti,syscon-psc fallback support
    ARM: dts: k2e: Replace 'ti,syscon-psc' property in DSP node
    ARM: dts: k2l: Replace 'ti,syscon-psc' property in DSP nodes
    ARM: dts: k2hk: Replace 'ti,syscon-psc' property in DSP nodes
    remoteproc/keystone: add support for using reset framework

    Signed-off-by: LCPD Auto Merger

    LCPD Auto Merger
     
  • TI-Feature: rpmsg
    TI-Tree: git://git.ti.com/rpmsg/rpmsg.git
    TI-Branch: rpmsg-ti-linux-4.1.y

    * 'rpmsg-ti-linux-4.1.y' of git://git.ti.com/rpmsg/rpmsg:
    remoteproc/keystone: ensure the DSPs are in reset in probe
    TEMP: ARM: dts: k2g-evm: Reserve some DDR for MPM usecases
    ARM: dts: k2g-evm: Add a common DSP shared memory CMA pool
    TEMP: ARM: dts: k2g-evm: Add dspmem node
    ARM: dts: k2g: Add DSP node
    remoteproc/keystone: add support for Keystone 2 Galileo SOCs
    remoteproc/keystone: drop ti,syscon-psc fallback support
    ARM: dts: k2e: Replace 'ti,syscon-psc' property in DSP node
    ARM: dts: k2l: Replace 'ti,syscon-psc' property in DSP nodes
    ARM: dts: k2hk: Replace 'ti,syscon-psc' property in DSP nodes
    remoteproc/keystone: add support for using reset framework

    Signed-off-by: Dan Murphy

    Conflicts:
    arch/arm/boot/dts/k2g-evm.dts
    arch/arm/boot/dts/k2g.dtsi

    Dan Murphy
     
  • Pull in the updated remoteproc feature branch that adds the support
    to load the DSP core on Keystone 2 Galileo SoC to the keystone
    remoteproc driver. The driver already had support for the Keystone 2
    Hawking/Kepler, Lamarr and Edison SoCs, and it has now been updated
    to use the reset framework for reset control and management. The
    K2G support is on par with the other SoCs in terms of functionality.

    The merge also syncs up the RPMsg integration branch with the latest
    platform base code.

    * 'rproc-linux-4.1.y' of git://git.ti.com/rpmsg/remoteproc: (64 commits)
    remoteproc/keystone: ensure the DSPs are in reset in probe
    TEMP: ARM: dts: k2g-evm: Reserve some DDR for MPM usecases
    ARM: dts: k2g-evm: Add a common DSP shared memory CMA pool
    TEMP: ARM: dts: k2g-evm: Add dspmem node
    ARM: dts: k2g: Add DSP node
    remoteproc/keystone: add support for Keystone 2 Galileo SOCs
    remoteproc/keystone: drop ti,syscon-psc fallback support
    ARM: dts: k2e: Replace 'ti,syscon-psc' property in DSP node
    ARM: dts: k2l: Replace 'ti,syscon-psc' property in DSP nodes
    ARM: dts: k2hk: Replace 'ti,syscon-psc' property in DSP nodes
    remoteproc/keystone: add support for using reset framework
    ARM: dts: k2g: Add DSP GPIO controller node
    ARM: dts: k2g: Add keystone IRQ controller node
    ARM: dts: k2g: Add device state controller node
    ti_config_fragments/baseport: Enable TI SCI reset driver
    ARM: dts: k2g: Add TI SCI reset-controller node
    reset: Add the TI SCI reset driver
    Documentation: dt: reset: Add TI SCI reset binding
    dt-bindings: reset: Add k2g reset definitions
    ti_config_fragments/baseport: enable reset-syscon driver
    ...

    Signed-off-by: Suman Anna

    Suman Anna
     
  • The DSPs are expected to be in reset when the driver probes a device.
    If the DSPs are out of reset in probe, the system may crash when the
    firmware is being loaded. So, add a check to make sure the DSP resets
    are asserted, and if not, throw a eye-catchy warning and assert the
    resets specifically.

    Signed-off-by: Andrew F. Davis
    [s-anna@ti.com: replace warning with a WARN]
    Signed-off-by: Suman Anna

    Andrew F. Davis
     
  • Add support to the keystone remoteproc driver for managing the
    DSP present in the Keystone 2 Galileo (K2G) SoC. The K2G SoC has
    a Power Management Micro Controller (PMMC) that manages the
    individual device's power, clock and reset functionalities.

    The keystone remoteproc driver already uses standard frameworks
    for reset and clock control, so it doesn't require any significant
    modifications other than a new compatible suitable for K2G DSP.

    The binding document is also updated to reflect the modified
    property values used by the K2G DSP node as compared to the
    values used by existing Keystone 2 DSPs.

    NOTE:
    The enhancement to use common pm_runtime framework for all Keystone
    2 SoCs is left for a future time. The redundata clock API usage for
    K2G does not impact any functionality, but is still required for
    other K2 SoCs.

    Signed-off-by: Suman Anna
    Signed-off-by: Andrew F. Davis

    Suman Anna
     
  • The Keystone remoteproc driver has already been enhanced to
    support using the reset framework API for managing the DSP
    device resets. All the existing DSP DT nodes have also been
    switched to use the 'resets' property instead of the deprecated
    'ti,syscon-psc' property.

    All the Keystone 2 family of SoCs are expected to be using reset
    drivers going forward, so drop the support for the direct syscon
    PSC based reset handling from the driver completely. The DT
    binding has also been updated accordingly.

    While at this, also add a build dependency for the driver
    against the RESET_CONTROLLER Kconfig, and switch to using the
    devm_reset_control_get() API instead of the optional variant.

    Signed-off-by: Andrew F. Davis
    [s-anna@ti.com: mandatory reset dependencies, binding updates]
    Signed-off-by: Suman Anna

    Andrew F. Davis
     
  • The Keystone family of SoCs has the reset registers as part of the
    Power and Sleep Controller (PSC) module. The keystone remoteproc
    driver currently manages these DSP resets by itself through the
    regmap/syscon API.

    Enhance the keystone remoteproc driver to start using the reset
    framework API for managing resets. This is being done to streamline
    the driver usage for supporting the DSP on Keystone 2 Galileo (K2G)
    SoC. This also switches the driver to use a more standard framework
    for resets.

    The support is added as an incremental change, so the regmap/syscon
    framework is used as a fallback to support the transition of the
    Keystone 2 DSP DTS nodes from using 'ti,psc-syscon' to the 'resets'
    property.

    Signed-off-by: Andrew F. Davis
    [s-anna@ti.com: add error checking, checkpatch fixes, binding updates]
    Signed-off-by: Suman Anna

    Andrew F. Davis
     
  • TI-Feature: ti_linux_base_lsk
    TI-Tree: git@git.ti.com:ti-linux-kernel/ti-linux-kernel.git
    TI-Branch: ti-linux-4.1.y

    * 'ti-linux-4.1.y' of git.ti.com:ti-linux-kernel/ti-linux-kernel:
    ti_config_fragments: introduce wlan.cfg
    ARM: dts: k2g: Add DSP GPIO controller node
    ARM: dts: k2g: Add keystone IRQ controller node
    ARM: dts: k2g: Add device state controller node
    ti_config_fragments/baseport: Enable TI SCI reset driver
    ARM: dts: k2g: Add TI SCI reset-controller node
    reset: Add the TI SCI reset driver
    Documentation: dt: reset: Add TI SCI reset binding
    dt-bindings: reset: Add k2g reset definitions
    ti_config_fragments/baseport: enable reset-syscon driver
    ARM: Keystone: Enable ARCH_HAS_RESET_CONTROLLER
    ARM: dts: keystone: Add PSC reset node
    reset: add a SYSCON based reset driver
    Documentation: dt: reset: Add syscon reset binding
    Revert "drm/i2c: tda998x: Fix bad checksum of the HDMI AVI infoframe"

    Signed-off-by: LCPD Auto Merger

    LCPD Auto Merger
     
  • …nel/platform-linux-feature-tree into rproc-linux-4.1.y

    Resync with the latest platform base code. The merge pulls in various
    required patches, fixes and new features including the following:
    - A new SYSCON reset driver that will be used by Keystone 2
    remoteproc driver for K2HK/L/E SoCs
    - Device nodes for Device State Controller, IRQ Controller for
    receiving interrupts from remoteprocs, and a DSP GPIO Controller
    for sending interrupts to DSPs on Keystone 2 Galileo SoC
    - Fixes in the TI SCI protocol to work with latest updates on the
    PMMC firmware for isolating reset control from clock control ops
    for K2G reset driver functionality
    - A new TI SCI reset driver that will be used by Keystone 2
    remoteproc driver for K2G SoC

    Other updates include
    - Clock updates to various Keystone 2 Galileo DTS nodes
    - LDO/SMPS fixes on AM57xx IDK boards
    - Various config fragments improvements to enable reset
    framework and drivers

    * 'platform-ti-linux-4.1.y' of git://git.ti.com/~rrnayak/ti-linux-kernel/platform-linux-feature-tree: (53 commits)
    ARM: dts: k2g: Add DSP GPIO controller node
    ARM: dts: k2g: Add keystone IRQ controller node
    ARM: dts: k2g: Add device state controller node
    ti_config_fragments/baseport: Enable TI SCI reset driver
    ARM: dts: k2g: Add TI SCI reset-controller node
    reset: Add the TI SCI reset driver
    Documentation: dt: reset: Add TI SCI reset binding
    dt-bindings: reset: Add k2g reset definitions
    ti_config_fragments/baseport: enable reset-syscon driver
    ARM: Keystone: Enable ARCH_HAS_RESET_CONTROLLER
    ARM: dts: keystone: Add PSC reset node
    reset: add a SYSCON based reset driver
    Documentation: dt: reset: Add syscon reset binding
    ARM: OMAP2+: omap_hwmod: Always restore saved hardreset context
    hwmon: (tmp102) Force wait for conversion time for the first valid data
    ti_config_fragments/baseport: Build thermal into kernel
    firmware: ti_sci: Add device_resets calls to the device ops
    firmware: ti_sci: Drop resets field from ti_sci_set_device_state calls
    ARM: dts: k2g: Fix Message Manager interrupt polarity
    baseport.cfg: Enable SYSTEM V IPC
    ...

    Signed-off-by: Suman Anna <s-anna@ti.com>

    Suman Anna
     
  • …nel/platform-linux-feature-tree into ti-linux-4.1.y

    TI-Feature: platform_base
    TI-Tree: git://git.ti.com/~rrnayak/ti-linux-kernel/platform-linux-feature-tree.git
    TI-Branch: platform-ti-linux-4.1.y

    * 'platform-ti-linux-4.1.y' of git://git.ti.com/~rrnayak/ti-linux-kernel/platform-linux-feature-tree:
    ARM: dts: k2g: Add DSP GPIO controller node
    ARM: dts: k2g: Add keystone IRQ controller node
    ARM: dts: k2g: Add device state controller node
    ti_config_fragments/baseport: Enable TI SCI reset driver
    ARM: dts: k2g: Add TI SCI reset-controller node
    reset: Add the TI SCI reset driver
    Documentation: dt: reset: Add TI SCI reset binding
    dt-bindings: reset: Add k2g reset definitions
    ti_config_fragments/baseport: enable reset-syscon driver
    ARM: Keystone: Enable ARCH_HAS_RESET_CONTROLLER
    ARM: dts: keystone: Add PSC reset node
    reset: add a SYSCON based reset driver
    Documentation: dt: reset: Add syscon reset binding

    Signed-off-by: Dan Murphy <DMurphy@ti.com>

    Conflicts:
    arch/arm/boot/dts/k2g.dtsi

    Dan Murphy
     

04 Dec, 2015

3 commits

  • …el/audio-display-linux-feature-tree into ti-linux-4.1.y

    TI-Feature: audio-display
    TI-Tree: git@git.ti.com:~darrene/ti-linux-kernel/audio-display-linux-feature-tree.git
    TI-Branch: audio-display-ti-linux-4.1.y

    * 'audio-display-ti-linux-4.1.y' of git.ti.com:~darrene/ti-linux-kernel/audio-display-linux-feature-tree:
    Revert "drm/i2c: tda998x: Fix bad checksum of the HDMI AVI infoframe"

    Signed-off-by: Dan Murphy <DMurphy@ti.com>

    Dan Murphy
     
  • Some TI Keystone family of SoCs contain a system controller (like the
    Power Management Micro Controller (PMMC) on Keystone 2 Galileo SoC)
    that manage the low-level device control (like clocks, resets etc)
    for the various hardware modules present on the SoC. These device
    control operations are provided to the host processor OS through a
    communication protocol called the TI System Control Interface (TI SCI)
    protocol.

    This patch adds a reset driver that communicates to the system
    controller over the TI SCI protocol for performing reset management
    of various devices present on the SoC. Various reset functionalities
    are achieved by the means of different TI SCI device operations
    provided by the TI SCI framework.

    Signed-off-by: Andrew F. Davis
    [s-anna@ti.com: documentation changes, revised commit message]
    Signed-off-by: Suman Anna
    Acked-by: Nishanth Menon

    Andrew F. Davis
     
  • Add a reset-controller driver for performing reset management of
    various devices present on the SoC, with the reset registers shared
    between devices in a common register memory space. This driver uses
    the syscon/regmap frameworks to actually implement the various reset
    functionalities needed by the reset consumer devices.

    Signed-off-by: Andrew F. Davis
    [s-anna@ti.com: add documentation, syscon name change]
    Signed-off-by: Suman Anna

    Andrew F. Davis
     

03 Dec, 2015

1 commit


02 Dec, 2015

2 commits

  • TI-Feature: ti_linux_base_lsk
    TI-Tree: git@git.ti.com:ti-linux-kernel/ti-linux-kernel.git
    TI-Branch: ti-linux-4.1.y

    * 'ti-linux-4.1.y' of git.ti.com:ti-linux-kernel/ti-linux-kernel:
    Revert "crypto: ahash - ensure statesize is non-zero"
    hwmon: (tmp102) Force wait for conversion time for the first valid data
    ARM: dts: dra72-evm: fix touchscreen on OSD LCD
    usb: dwc3: gadget: don't prestart interrupt endpoints
    ti_config_fragments/baseport: Build thermal into kernel

    Signed-off-by: LCPD Auto Merger

    LCPD Auto Merger
     
  • …nel/platform-linux-feature-tree into ti-linux-4.1.y

    TI-Feature: platform_base
    TI-Tree: git://git.ti.com/~rrnayak/ti-linux-kernel/platform-linux-feature-tree.git
    TI-Branch: platform-ti-linux-4.1.y

    * 'platform-ti-linux-4.1.y' of git://git.ti.com/~rrnayak/ti-linux-kernel/platform-linux-feature-tree:
    hwmon: (tmp102) Force wait for conversion time for the first valid data
    ti_config_fragments/baseport: Build thermal into kernel

    Signed-off-by: Dan Murphy <DMurphy@ti.com>

    Dan Murphy
     

01 Dec, 2015

3 commits

  • TMP102 works based on conversions done periodically. However, as per
    the TMP102 data sheet[1] the first conversion is triggered immediately
    after we program the configuration register. The temperature data
    registers do not reflect proper data until the first conversion is
    complete (in our case HZ/4).

    The driver currently sets the last_update to be jiffies - HZ, just
    after the configuration is complete. When tmp102 driver registers
    with the thermal framework, it immediately tries to read the sensor
    temperature data. This takes place even before the conversion on the
    TMP102 is complete and results in an invalid temperature read.

    Depending on the value read, this may cause thermal framework to
    assume that a critical temperature event has occurred and attempts to
    shutdown the system.

    Instead of causing an invalid mid-conversion value to be read
    erroneously, we mark the last_update to be in-line with the current
    jiffies. This allows the tmp102_update_device function to skip update
    until the required conversion time is complete. Further, we ensure to
    return -EAGAIN result instead of returning spurious temperature (such
    as 0C) values to the caller to prevent any wrong decisions made with
    such values.

    A simpler alternative approach could be to sleep in the probe for the
    duration required, but that will result in latency that is undesirable
    that can delay boot sequence un-necessarily.

    [1] http://www.ti.com/lit/ds/symlink/tmp102.pdf

    Reported-by: Aparna Balasubramanian
    Reported-by: Elvita Lobo
    Reported-by: Yan Liu
    Signed-off-by: Nishanth Menon

    Nishanth Menon
     
  • Because interrupt endpoints usually transmit such
    small amounts of data, it seems pointless to prestart
    transfers and try to get speed improvements. This
    patch also sorts out a problem with CDC ECM function
    where its notification endpoint gets stuck in busy
    state and we continuously issue Update Transfer
    commands.

    Fixes: 8a1a9c9e4503 ("usb: dwc3: gadget: start transfer on XFER_COMPLETE")
    Signed-off-by: Felipe Balbi
    Signed-off-by: Sekhar Nori

    Felipe Balbi
     
  • TI-Feature: ti_linux_base_lsk
    TI-Tree: git@git.ti.com:ti-linux-kernel/ti-linux-kernel.git
    TI-Branch: ti-linux-4.1.y

    * 'ti-linux-4.1.y' of git.ti.com:ti-linux-kernel/ti-linux-kernel:
    mmc: host: omap_hsmmc: increase the timeout value given for sw timeout
    mmc: host: omap_hsmmc: Fix software timeout handling
    mmc: host: omap_hsmmc: disable irq while handling soft timeout
    ASoC: davinci-mcasp: Fix master capture only mode
    ASoC: davinci-mcasp: Fix TDM slot rx/tx mask associations
    ARM: DTS: am57xx-idk-lcd-osd: Add support for capacitive touch controller

    Signed-off-by: LCPD Auto Merger

    LCPD Auto Merger
     

30 Nov, 2015

4 commits

  • Increase the timeout value given for sw timeout to a high value
    (3 times the value requested by card). During the experiments, it
    was observed that the eMMC card on DRA72x EVM advertised 960ms as
    timeout but the (worst case) transfer complete came after 2.6 seconds.

    The additional delay is to account for the start time of the transfer,
    IO timings and card advertising incorrect timeout values. Also add a
    minimum timeout value of 20ms so that we don't timeout unnecessarily.

    Signed-off-by: Kishon Vijay Abraham I
    [nsekhar@ti.com: massage commit text]
    Signed-off-by: Sekhar Nori

    Kishon Vijay Abraham I
     
  • omap_hsmmc_xfer_done or omap_hsmmc_cmd_done should be invoked
    to inform the MMC core of the completion of request and for
    any cleanup operations. Invoke these in the software timeout
    handler. This helps to avoid blocked fs process while doing
    any MMC operation.

    Signed-off-by: Kishon Vijay Abraham I
    Signed-off-by: Sekhar Nori

    Kishon Vijay Abraham I
     
  • In order to avoid unnecessary interrupt handling while we are
    already handling the software timeout, disable the irq in
    software timeout handler.
    For example there was a CRC error interrupt while software
    timeout was being handled resulting in an abort.

    Signed-off-by: Kishon Vijay Abraham I
    Signed-off-by: Sekhar Nori

    Kishon Vijay Abraham I
     
  • TI-Feature: ti_linux_base_lsk
    TI-Tree: git@git.ti.com:ti-linux-kernel/ti-linux-kernel.git
    TI-Branch: ti-linux-4.1.y

    * 'ti-linux-4.1.y' of git.ti.com:ti-linux-kernel/ti-linux-kernel:
    spi: davinci: use dev_err() for error reporting
    spi: davinci: fix spurious i/o error
    ARM: dts: dra72-evm: Mark uart1 rxd as wakeup capable
    ARM: dts: dra72-evm: We don't support NAND on dra72-evm

    Signed-off-by: LCPD Auto Merger

    LCPD Auto Merger
     

28 Nov, 2015

1 commit

  • TI-Feature: ti_linux_base_lsk
    TI-Tree: git@git.ti.com:ti-linux-kernel/ti-linux-kernel.git
    TI-Branch: ti-linux-4.1.y

    * 'ti-linux-4.1.y' of git.ti.com:ti-linux-kernel/ti-linux-kernel:
    ARM: dts: k2g-evm: update dts to enable mdio bindings
    ARM: dts: k2g: add netcp bindings to support nss lite
    ti_config_fragments/connectivity.cfg: enable Micrel phy
    Revert "net: netcp: remove dead code from the driver"
    net: netcp: support probe deferral
    soc: ti: provide APIs to support driver probe deferral

    Signed-off-by: LCPD Auto Merger

    LCPD Auto Merger
     

27 Nov, 2015

1 commit