05 Dec, 2015
11 commits
-
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 frameworkSigned-off-by: Dan Murphy
Conflicts:
arch/arm/boot/dts/k2g-evm.dts
arch/arm/boot/dts/k2g.dtsi -
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
-
Add a reserved memory node to carveout a portion of the external
DDR memory, and add this address region to the dspmem node on the
K2 Galileo EVM board. This is done to enable the Keystone
Multi Proc Manager (MPM) to load images that use this memory
region. The memory is chosen to be adjacent to the DSP CMA memory
pool so that the DSP Memory Protection and Address Extension
(MPAX) module can be configured efficiently. The memory will
not be mapped into the kernel space.Signed-off-by: Suman Anna
-
A common CMA memory pool reserved memory node is added, and
is attached to all the DSP nodes through the 'memory-region'
property on the K2 Galileo EVM board. This area will be used
for allocating virtio rings and buffers. The common node allows
the DSP Memory Protection and Address Extension (MPAX) module
to be configured properly for the DSP processor.Signed-off-by: Andrew F. Davis
[s-anna@ti.com: correct CMA pool addresses]
Signed-off-by: Suman Anna -
Add a dspmem node on the K2 Galileo EVM board. The node
allows the entire MSM RAM (1 MB) to be mapped to userspace
to enable the Keystone Multi Proc Manager (MPM) based
usecases.Signed-off-by: Suman Anna
-
The Keystone 2 Galileo SoC has a single TMS320C66x DSP
Core Subsystem (C66x CorePac), containing a C66x Fixed /
Floating-Point DSP Core, and 32KB of L1P & L1D SRAMs and a
1MB L2 SRAM. Add the DT node and the rproc alias for this DSP
processor sub-system.The DT node has a new property 'power-domains', and uses
slightly different property values for 'clocks' and 'resets'
compared to other Keystone 2 SoCs. The processor does not have
a MMU, and uses various IPC Generation registers and shared
memory for inter-processor communication.NOTE:
The node name uses a DSP number suffix and does not include the
address for now. This is required to match the DT name used by
the userland MPM stack for working properly.Signed-off-by: Andrew F. Davis
Signed-off-by: Suman Anna -
Replace the custom 'ti,syscon-psc' property used for representing
device resets with a DT standard 'resets' property in the DSP node
present within the Keystone 2 Edison SoC. The 'ti,syscon-psc'
property is deprecated, and will not be supported anymore.Signed-off-by: Andrew F. Davis
[s-anna@ti.com: update commit description]
Signed-off-by: Suman Anna -
Replace the custom 'ti,syscon-psc' property used for representing
device resets with a DT standard 'resets' property in the DSP nodes
present within the Keystone 2 Lamarr SoC. The 'ti,syscon-psc'
property is deprecated, and will not be supported anymore.Signed-off-by: Andrew F. Davis
[s-anna@ti.com: update commit description]
Signed-off-by: Suman Anna -
Replace the custom 'ti,syscon-psc' property used for representing
device resets with a DT standard 'resets' property in the DSP nodes
present within the Keystone 2 Hawking/Kepler SoCs. The 'ti,syscon-psc'
property is deprecated, and will not be supported anymore.Signed-off-by: Andrew F. Davis
[s-anna@ti.com: update commit description]
Signed-off-by: Suman Anna -
…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 SoCOther 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>
-
…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 bindingSigned-off-by: Dan Murphy <DMurphy@ti.com>
Conflicts:
arch/arm/boot/dts/k2g.dtsi
04 Dec, 2015
6 commits
-
Add the DSP GPIO controller node on Keystone 2 Galileo SoC.
This is used to send interrupts to the only DSP processor
subsystem present on the SoC. The IP is identical to that
of the equivalent nodes on existing K2 SoCs.Signed-off-by: Andrew F. Davis
[s-anna@ti.com: revise commit description slightly]
Signed-off-by: Suman Anna -
Add the Keystone IRQ controller IP node on Keystone 2 Galileo
SoC. This allows the ARM CorePac core to receive interrupts
from remote processor devices (eg: DSP) on the SoC.The IP is identical in functionality to that of the equivalent
nodes on existing K2 SoCs. The only difference is the ARM INTC
interrupt id/event number.Signed-off-by: Andrew F. Davis
[s-anna@ti.com: revise commit description slightly]
Signed-off-by: Suman Anna -
Add the device state controller node as a syscon node to the
Keystone 2 Galileo SoC. This module provides similar device
control functionality as that on the existing K2 SoCs.One example usage would be the boot address programming of the
DSP processor sub-system.Signed-off-by: Andrew F. Davis
[s-anna@ti.com: relocate node and revise commit description]
Signed-off-by: Suman Anna -
Add a reset-controller node for managing resets of various
remote processor devices on the SoC over the Texas Instrument's
System Control Interface (TI SCI) protocol.Signed-off-by: Andrew F. Davis
[s-anna@ti.com: revise commit description slightly]
Signed-off-by: Suman Anna
Acked-by: Nishanth Menon -
The Keystone 2 family of SoCs will use various Reset Controller
drivers for managing the resets of remote processor devices like
DSPs on the SoC, so select the ARCH_HAS_RESET_CONTROLLER option
by default to enable the Reset framework.Signed-off-by: Suman Anna
-
Add a Power Sleep Controller (PSC) reset controller node
managing the resets required by the DSPs on Keystone 2
family of SoCs (K2HK/K2L/K2E).Signed-off-by: Andrew F. Davis
Signed-off-by: Suman Anna
03 Dec, 2015
2 commits
-
…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: OMAP2+: omap_hwmod: Always restore saved hardreset contextSigned-off-by: Dan Murphy <DMurphy@ti.com>
-
Previously when restoring hardreset context during
omap_hwmod_restore_context we would only deassert the hardreset lines if
the module was previously active, however, if a hwmod has all hardresets
asserted then _enable will return without actually enabling the module.This is a problem for the gfx hwmod on am437x as it gets disabled in
suspend path so it appears as disabled to the restore context code but
then during the attempted enable call during the regular kernel resume
path, the hwmod cannot actually be enabled.Signed-off-by: Dave Gerlach
Acked-by: Tero Kristo
01 Dec, 2015
3 commits
-
…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:
ARM: dts: dra72-evm: fix touchscreen on OSD LCD
usb: dwc3: gadget: don't prestart interrupt endpointsSigned-off-by: Dan Murphy <DMurphy@ti.com>
-
dra7x-evm-lcd-osd.dtsi has touchscreen interrupt set
to line #2 of GPIO1. However, this is incorrect for
DRA72 EVM. Since the irq line differs between different
boards, move it from the generic OSD LCD device-tree
include file to board specific .dts file.This fixes touchscreen working on DRA72x EVM.
Signed-off-by: Sekhar Nori
-
…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:
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 controllerSigned-off-by: Dan Murphy <DMurphy@ti.com>
27 Nov, 2015
2 commits
-
Uart1 rxd is wakeup capable on DRA72 EVM. Hence, mark rxd line as
wakeup capable. This is similar to commit 66b0436977e2c ("ARM: dts:
dra7-evm: Mark uart1 rxd as wakeup capable") for DRA74 EVM.Acked-by: Nishanth Menon
Signed-off-by: Vignesh R
Signed-off-by: Sekhar Nori -
For the existing IOdelay configuration via u-boot we don't
support NAND on dra72-evm. Disable it.Signed-off-by: Sekhar Nori
26 Nov, 2015
5 commits
-
Update evm dts to enable mdio and phy for K2G EVM.
Tested-by: Dave Gerlach
Signed-off-by: Murali Karicheri
[nsekhar@ti.com: fix subject prefix, move gbe0
phy-handle here]
Signed-off-by: Sekhar Nori -
This patch adds bindings to support netcp driver for nss lite found on
k2g SoC. This also add bindings for qmss lite, knav pktdma and cpsw 2u
version of ethss.Signed-off-by: Murali Karicheri
[nsekhar@ti.com: move network clocks to k2g-netcp.dtsi]
Signed-off-by: Sekhar Nori -
…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:
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 IPCSigned-off-by: Dan Murphy <DMurphy@ti.com>
-
Add DT node entry for FocalTech's FT5506 touchscreen controller for both
the AM571x IDK and AM572x variants that include the OSD display.Signed-off-by: Franklin S Cooper Jr
Acked-by: Sekhar Nori
[Removed extra blank line at end of arch/arm/boot/dts/am572x-idk-lcd-osd.dts]
Signed-off-by: Jyri Sarha -
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:
rpmsg: use proper format-specifier for printing dma_addr_t
rpmsg: rpc: fix the definition of virt_addr_t
rpmsg: rpc: define and use a device address type
rpmsg: rpc: use %pa for printing phys_addr_t
remoteproc/pruss: use %pa for printing phys_addr_t
remoteproc: use proper format-specifier for printing dma_addr_t
ARM: OMAP2+: iommu: fix sleeping lock usage in atomic context bugSigned-off-by: Dan Murphy
25 Nov, 2015
10 commits
-
It seems that the message manager proxy interrupt is held high for as
long as there is data in the queue. Since we handle a single message
in the TI message manager driver, If there are multiple messages already
pending in the queue prior to the driver's handler getting invoked,
Then, only the first message is handled (triggered by the rising edge).Other pending messages in the queue are never handled and system
deadlocks and eventually queue overflows.Signed-off-by: Nishanth Menon
-
AM572x SoC has 3 VIP module/6 VIN ports. OV2659 sensor board connects
to VIN4 B port of VIP2. Connect OV2659 and VIN4 B port node remote end
point to each other.Acked-by: Benoit Parrot
Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha -
AM571x SoC has only 1 VIP module. OV2659 sensor board connects to VIN1
b port of VIP module. Connect OV2659 and VIN1 b port remote end point
to each other.Acked-by: Benoit Parrot
Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha -
OV2659 sensor board is common for AM572x and AM571x IDK platforms,
therefor we define the OV2659 sensor node in a idk common dtsi file.Output of camera sensor board is connected to different VIP module
and VIN port number in AM572x and AM571x idk platforms. Remote end
point for sensor node connection to VIN port number will be defined in
platform specific dts file in follow on patches.The camera reference clock comes off the X1 20MHz fixed oscillator
clock source off the AM571x/AM572x IDK and is shared with display
bridge chip.Acked-by: Benoit Parrot
Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha -
OSD101T2045-53TS LCD is an add on kit (purchased separately) to AM571x
IDK platform, therefore create a separate OSD LCD dts.LCD support will not work on AM572x 1.1A and prior revisions without
board modification. Refer to revision specific rework instruction for
further information.Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha -
OSD101T2045-53TS LCD is an add on kit (purchased separately) to AM572x
IDK platform, therefore create a separate OSD LCD dts.LCD support will not work on AM572x 1.2A and prior revisions without
board modification. Refer to revision specific rework instruction for
further information.Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha -
OSD LCD display panel OSD101T2045-53TS is an add on kit (purchased
separately) that is common for AM572x and AM571x IDK platforms,
therefore we define the panel in a common LCD dtsi file. This also
allows for a future kit to contain a different LCD panel.Backlight control is via eCAP module of AM57xx PWM subsystem.
This MIPI DSI panel uses the Toshiba TC358778XBG parallel RGB to MIPI
DSI bridge device available on AM571x and AM572x IDKs.The LCD panel contains touch screen controller that will be available
as a follow on patch.Reference: OSD101T2045-53TS datasheet (registration required) -
http://www.osddisplays.com/product/osdTC358778XBG datasheet -
www.toshiba.com/taec/components/Datasheet/TC358778XBG.pdfSigned-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha -
AM572x and AM571x IDK platforms contain Toshiba TC358778XBG
(compatible to TC358768) parallel RGB to MIPI DSI bridge chip.
This bridge chip is used by LCD panels kits such as the OSD LCD
panel available for AM572x and AM571x IDK platforms to be purchased
separately.TC358778XBG datasheet -
www.toshiba.com/taec/components/Datasheet/TC358778XBG.pdfWe also have a single fixed 20MHz external crystal supplying refclk
for both camera and the bridge chip as well.Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha -
Enhanced Capture Module (eCAP) is an submodule of DRA7xx/AM57xx PWM
module instances which is capable of Capture and also operate in
Asymmetric PWM (APWM) mode. APWM is used in many platforms such as
AM57xx-IDKs to provide backlight function.Even though, DRA7xx/AM57xx has up to 3 instances of eCAP (one per
PWM instance), eCAP0 is most commonly used and hence we restrict to
defining just that.Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha -
AM571x and AM572x IDKs both have HDMI capability and they are
basically the same configuration (including GPIOs and LDOs).
Further, TPD12S016 IC is also used as an integrated HDMI ESD
solution on both these platforms. Reference: TPD12S016 datasheet:
www.ti.com/lit/ds/symlink/tpd12s016.pdfWe add common support for HDMI audio and video, though just the video
support has been currently verified (pending final production boards).NOTE: AM571x-IDK and AM572x-IDK with revisions 1.2a or prior require
board modifications for HDMI EDID to function.HACK ALERT: We describe LDO3 to describe HDMI VDDA supply. While this
is correct for AM572x-IDK rev 1.2a, LDO4 is used on AM571x-IDK rev
1.2a and on AM572x-IDK rev 1.3a. On AM572x-IDK rev 1.2a PMIC does
not have LDO4 enable capability (even though register map exists),
hence will never work if we depend on LDO4. However, LDO4 will be
always-on on AM571x-IDK rev 1.2a and AM572x-IDK rev 1.3a, and we will
temporarily get away with out crashing. This however MUST BE FIXED
once the AM572x-IDK rev 1.2a is deprecated.Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha
24 Nov, 2015
1 commit
-
Pull in the updated remoteproc feature branch that includes a
minor mutex locking fix in OMAP IOMMU driver.* 'rproc-linux-4.1.y' of git://git.ti.com/rpmsg/remoteproc:
ARM: OMAP2+: iommu: fix sleeping lock usage in atomic context bugSigned-off-by: Suman Anna