On Fri, Apr 26, 2013 at 5:45 PM, William Mills wmi...@ti.com wrote:
On 04/26/2013 03:06 AM, Mats Liljegren wrote:
I would like to perform a customer demo running a benchmark
application in full nohz mode on TCI6638k2k target, which as far as I
understand it is a KeyStone II architecture.
From: avinash philip avinashphi...@ti.com
From: Philip, Avinash avinashphi...@ti.com
Add ELM data node to AM33XX device tree file.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Acked-by: Peter Korsgaard jac...@sunsite.dk
Tested-by: Pekon Gupta pe...@ti.com
---
Changes since v2:
-
From: avinash philip avinashphi...@ti.com
From: Philip, Avinash avinashphi...@ti.com
Add GPMC data node to AM33XX device tree file.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Acked-by: Peter Korsgaard jac...@sunsite.dk
Tested-by: Pekon Gupta pe...@ti.com
---
Changes since v2:
-
From: avinash philip avinashphi...@ti.com
NAND flash connected in am335x-evm on GPMC controller. This patch adds
device tree node in am3355-evm with GPMC contoller timing for NAND flash
interface, NAND partition table, ECC scheme, elm handle id.
Signed-off-by: Philip Avinash avinashphi...@ti.com
I've been experiencing several crashes all pointing exactly the same place in
the same tick routine (see below).
The exception stack trace at the end changes depending on when the oops
occurs.
I've had the oops occur maybe 6 times in the last 50 reboots.
Any ideas ?
Mark J.
---
[
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed.
However using the old usb phy library cannot
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
Changed the inticall from subsys_initcall to module_init for
twl4030-usb.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/phy/phy-twl4030-usb.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/drivers/usb/phy/phy-twl4030-usb.c
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new framework
will break
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle.
This framework will be of use only to devices that uses external PHY (PHY
functionality is not embedded
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on/get_sync and
power_off/put_sync to align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/phy/phy-twl4030-usb.c | 55 -
1 file changed, 12
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/phy/phy-omap-usb2.c | 24
1 file changed, 24 deletions(-)
diff --git
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy device name) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/mach-omap2/usb-musb.c |6 +-
include/linux/usb/musb.h |
On Wed, 2013-02-06 at 11:17 +, Patil, Rachna wrote:
Can you share the branch which you have tested?
https://github.com/patilrachna/linux/tree/v3.8_rc3_MFD_TSCADC_DT-v2
Did you get a chance to test this branch?
And can you also share your branch, on which you observed the issue.
On Thu, Apr 11, 2013 at 11:32:01AM -0700, Tony Lindgren wrote:
Hi Roger,
Looks like there's a section mismatch issue in linux next:
WARNING: vmlinux.o(.text+0x2a7b4): Section mismatch in reference from the
function usbhs_init_phys() to the function .init.text:usb_bind_phy()
The function
Hi,
omapdss, omapfb and the panel drivers do not currently support deferred probe,
which is causing the display drivers fail when booting with DT.
This series adds very basic support for deferred probing, which hopefully fixes
the issues for omap4 panda and sdp boards with the current kernel.
omapfb requires the panels to have been probed before omapfb's probe. We
currently manage that by having omapfb in late initcall level. However,
a much simpler way is to just change the makefile so that omapfb is
after the panel drivers.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
Instead of using platform_driver_probe(), use module_platform_driver()
so that we can support deferred probing.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/omapfb/omapfb-main.c | 28 +++-
1 file changed, 3 insertions(+), 25 deletions(-)
omapfb requires the panel drivers to have been probed when omapfb is
initialized. omapfb does not support insertion of new panels after its
probe. This causes a problem in case omapdss or the panel probes have
been deferred due to EPROBE_DEFER error, as omapfb won't find any
displays.
As a quick
Use platform_driver_register() instead of platform_driver_probe() so
that we can support EPROBE_DEFER.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dsi.c | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git
Add proper error handling for dsi_probe_pdata(). This will cause
EPROBE_DEFER to be properly passed upwards, causing the DSI driver to be
probed again later if a resource was missing.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dsi.c | 20
Use platform_driver_register() instead of platform_driver_probe() so
that we can support EPROBE_DEFER.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dpi.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git
Use platform_driver_register() instead of platform_driver_probe() so
that we can support EPROBE_DEFER.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/hdmi.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git
Add proper error handling for hdmi_probe_pdata(). This will cause
EPROBE_DEFER to be properly passed upwards, causing the HDMI driver to be
probed again later if a resource was missing.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/hdmi.c | 22
Add proper error handling for dpi_probe_pdata(). This will cause
EPROBE_DEFER to be properly passed upwards, causing the DPI driver to be
probed again later if a resource was missing.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dpi.c | 22
If the I2C adapter needed by the TFP410 device is not available yet,
return EPROBE_DEFER so that the device will get probed again.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/displays/panel-tfp410.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On 04/19/2013 12:57 PM, Roger Quadros wrote:
Hi Benoit/Tony
I've consolidated all the USB host device tree patches for Panda and Beagles
to one place and addressed Tony's comments.
NOTE: patch 1 depends on OMAP clock binding introduced in
https://lkml.org/lkml/2013/4/12/407
Tony, Benoit,
* Mark Jackson mpfj-l...@newflow.co.uk [130429 01:38]:
I've been experiencing several crashes all pointing exactly the same place in
the same tick routine (see below).
The exception stack trace at the end changes depending on when the oops
occurs.
I've had the oops occur maybe 6 times
On 29/04/13 16:41, Tony Lindgren wrote:
* Mark Jackson mpfj-l...@newflow.co.uk [130429 01:38]:
I've been experiencing several crashes all pointing exactly the same place
in the same tick routine (see below).
The exception stack trace at the end changes depending on when the oops
occurs.
From: Sebastian Andrzej Siewior bige...@linutronix.de
Date: Fri, 26 Apr 2013 14:03:24 +0200
David, how did this happen? The patch I've sent
http://www.spinics.net/lists/netdev/msg234240.html
adds this to the probe function, according to the net-next tree it was
added to
On 4/29/2013 1:23 PM, Gupta, Pekon wrote:
From: avinash philip avinashphi...@ti.com
From: Philip, Avinash avinashphi...@ti.com
From: line is repeated twice.
Add ELM data node to AM33XX device tree file.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Acked-by: Peter Korsgaard
On 4/29/2013 1:25 PM, Gupta, Pekon wrote:
From: avinash philip avinashphi...@ti.com
NAND flash connected in am335x-evm on GPMC controller. This patch adds
device tree node in am3355-evm with GPMC contoller timing for NAND flash
interface, NAND partition table, ECC scheme, elm handle id.
34 matches
Mail list logo
