10 Dec, 2015
6 commits
-
This patch enables the gbe serdes support on boards that
use it.As such gbe does not depend on the SerDes configurations
from u-boot.Signed-off-by: WingMan Kwok
[nsekhar@ti.com: massage commit message]
Signed-off-by: Sekhar Nori -
The IP is owned by a 3rd party and this patch renames some of the
functions per vendor recommendation.Signed-off-by: Murali Karicheri
Signed-off-by: Sekhar Nori -
The IP is owned by 3rd party and this patch makes updates to the code
to change constants and data structures per vendor recommendation.Signed-off-by: Murali Karicheri
Signed-off-by: WingMan Kwok
Signed-off-by: Sekhar Nori -
kserdes_att_boost_phyb_patch() is unnecessary as it just call another
function kserdes_att_boost_phyb_lane_patch() from within it. So instead
call kserdes_att_boost_phyb_lane_patch() directly since we have no reuse
of the same in the code anymore.Signed-off-by: Murali Karicheri
Signed-off-by: WingMan Kwok
[nm@ti.com: massage commit text]
Signed-off-by: Sekhar Nori -
Hyperlink is not supported by the driver. So remove all code related
to hyperlink.Signed-off-by: Murali Karicheri
Signed-off-by: WingMan Kwok
[nsekhar@ti.com: adjust subject line]
Signed-off-by: Sekhar Nori -
The SerDes IP is owned by a 3rd party and this patch makes
update to the comments in the code as recommended by the
vendor.Signed-off-by: Murali Karicheri
Signed-off-by: WingMan Kwok
Signed-off-by: Sekhar Nori
01 Dec, 2015
2 commits
-
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
-
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
30 Nov, 2015
3 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 -
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 -
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
27 Nov, 2015
4 commits
-
Use dev_err() for reporting errors rather than
dev_dbg().Signed-off-by: Sekhar Nori
-
davinci_spi_bufs() uses wait_for_completion_interruptible()
without bothering to handle -ERESTARTSYS. Due to this,
sometime, it returns prematurely when a signal is received.
Since the return value is never checked, userspace eventually
receives a spurious -EIO.To fix this, use un-interruptible wait_for_completion_timeout().
Signed-off-by: Sekhar Nori
-
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
9 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 -
Signed-off-by: Murali Karicheri
[nsekhar@ti.com: move addition to networking section]
Signed-off-by: Sekhar Nori -
As the probe sequence is not guaranteed contrary to the assumption
of this patch, following commit has to be reverted.commit 2d8e276a9030 ("net: netcp: remove dead code from the driver")
Tested-by: Dave Gerlach
Signed-off-by: Murali Karicheri
Signed-off-by: Sekhar Nori -
The netcp driver shouldn't proceed until the knav qmss and dma
devices are ready. So return -EPROBE_DEFER if these devices are not
ready.Tested-by: Dave Gerlach
Signed-off-by: Murali Karicheri
Signed-off-by: Sekhar Nori -
The driver needs to take care of probe deferral. So if drivers such as
netcp that depends on knav qmss/dma driver needs to know when these
devices are ready. So add a API to query the device ready status from
these drivers.Tested-by: Dave Gerlach
Signed-off-by: Murali Karicheri
Signed-off-by: Sekhar Nori -
…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:
Revert "usb: dwc3: host: pass STOP_EP flag for known broken revisions"
Revert "usb: host: xhci-plat: enable STOP_EP workaround if platform requested"
Revert "usb: host: xhci: add quirk flag for broken Stop EP cmd"Signed-off-by: Dan Murphy <DMurphy@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:
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>
-
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
16 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:
ARM: dts: am572x-idk: Add OV2659 camera sensor support for AM572x IDK
ARM: dts: am571x-idk: Add OV2659 camera sensor support for AM571x IDK
ARM: dts: am57xx-idk-common: Add OV2659 camera sensor support
ARM: dts: am571x-idk-lcd-osd: Add OSD101T2045-53TS LCD kit support for AM571x IDK
ARM: dts: am572x-idk-lcd-osd: Add OSD101T2045-53TS LCD kit support for AM572x IDK
ARM: dts: am57xx-idk-lcd-osd: Add OSD101T2045-53TS LCD display support
ARM: dts: am57xx-idk-common: Add TC358778XBG RGB DPI to MIPI DSI bridge support
ARM: dts: dra7: Add ecap support
Documentation: dt: pwm-tiecap: Add DRA746 SoC support
ARM: dts: am57xx-idk-common: Add HDMI support
Documentation: dt: ti,tpd12s015: Add TPD12S016 support
TI-Integration: Move all Media/V4L2 related config to audio-display fragmentSigned-off-by: Dan Murphy <DMurphy@ti.com>
-
Add set_device_resets to the device ops of ti_sci to handle new
TI_SCI_MSG_SET_DEVICE_RESETS message introduced with ABI 2.3 that
will control the resets of a device without touching any of the
other state associated with that device.Previously resets control was handled by the TI_SCI_MSG_SET_DEVICE
message which also controls device state. This would lead to the
reset framework being responsible for controlling resets but also
requiring knowledge about the state of the device or making assumptions
and causing undefined behavior. With this new split ti_sci_pm_domains
can control the state exclusively while also setting the reset value
when turning the device on and the reset framework will be able to
control resets independently of device state.Also add get_device_resets to return the state of the resets of a
device.Acked-by: Nishanth Menon
Signed-off-by: Dave Gerlach -
TI_SCI_MSG_SET_DEVICE_STATE no longer will control resets as this has
been moved to a new separate ABI as of ABI 2.3 so drop the resets field
from the message request and update ti_sci_set_device_state and all
functions using it to no longer set the resets field.Also update ti_sci_pm_domains to avoid build breakage as it uses the
get_device op which used to take resets as a parameter.Acked-by: Nishanth Menon
Signed-off-by: Dave Gerlach -
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
-
…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:
ti_config_fragments/connectivity.cfg: Enable IP ESP TransformationSigned-off-by: Dan Murphy <DMurphy@ti.com>
-
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 -
Add eCAP binding for DRA746 SoC which is same as AM335x SoC.
Acked-by: Sekhar Nori
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 -
Add binding for TPD12S016 HDMI companion chip. This is compatible with
TPD12S015.Signed-off-by: Manisha Agrawal
Signed-off-by: Jyri Sarha
