Hi,
On Wed, Feb 06, 2013 at 11:34:32PM +, Paul Walmsley wrote:
Boot tests:
* am335xbone: hangs after Starting kernel
- Cause unknown
- http://www.mail-archive.com/linux-omap@vger.kernel.org/msg82297.html
- http://marc.info/?l=linux-omapm=135903184512238w=2
-
On Wed, Feb 06, 2013 at 03:03:14PM -0600, Jon Hunter wrote:
Adds device-tree bindings from SDMA on OMAP2+ devices. DMA client
bindings are also added for devices that have SPI and MMC bindings
populated. Client binding data is based upon existing HWMOD data for
OMAP and has been checked
Hi Tomi, Florian,
On Tue, Jan 15, 2013 at 19:00:50, Mohammed, Afzal wrote:
This series makes da8xx-fb driver (device found on DaVinci and AM335x)
capable of handling runtime timing configuration by adding fb_set_par.
The last change adds actual fb_set_par support. Other preceeding
changes
Hi,
On 2013-02-07 11:05, Mohammed, Afzal wrote:
Hi Tomi, Florian,
On Tue, Jan 15, 2013 at 19:00:50, Mohammed, Afzal wrote:
This series makes da8xx-fb driver (device found on DaVinci and AM335x)
capable of handling runtime timing configuration by adding fb_set_par.
The last change adds
On 02/06/2013 05:43 PM, Alan Stern wrote:
On Wed, 6 Feb 2013, Felipe Balbi wrote:
I can't reproduce the problem on Panda, but I can on Beagle with a slightly
different behaviour.
1) connecting/disconnecting device directly to the beagleboard's USB port
works fine.
2) If I connect a USB
Hi Paul,
Paul Walmsley a écrit :
Hi Matthieu,
On Tue, 22 Jan 2013, Paul Walmsley wrote:
Any progress on updating and resending your omap3 nand : use
NAND_BUSWIDTH_AUTO patch? We're in danger of missing the 3.9 merge
window if it takes too much longer.
Could you let us know if
Okay ... I have made some progress, but it's not ideal.
Currently I've hacked the GPMC DT driver (gpmc_probe_dt(), etc) so it now
handles setting up the
chip selects and timings for NOR devices, e.g.
gpmc: gpmc@5000 {
status = okay;
On 07/02/13 09:51, Mark Jackson wrote:
Okay ... I have made some progress, but it's not ideal.
snip
But the physmap driver (of_flash_probe()) is unable to use this information.
It seems that although
I can call of_flash_probe() from my NOR setup code, the platform_device being
reference
This patch series adds low power transition support for OMAP NAND driver.
With recent driver conversion of GPMC to platform_driver, pm_runtime calls
can be used to handle module enable disable of GPMC. This is taken care
patch #1.
patch #2 is for GPMC suspend/resume support.
This includes low
Support for pm_runtime add to GPMC driver.
Signed-off-by: Philip Avinash avinashphi...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index 2c57f81..b1cd6c1 100644
---
With GPMC converted to platform driver recently, adds low power
transition support in driver itself.
Signed-off-by: Philip Avinash avinashphi...@ti.com
---
Changes since v1:
Module disable enable added using pm_runtime support.
arch/arm/mach-omap2/gpmc.c | 20
1
In low power modes of AM335X platforms, peripherals power is cut off.
This patch supports low power sleep transition support for ELM driver.
Signed-off-by: Philip Avinash avinashphi...@ti.com
---
drivers/mtd/devices/elm.c | 40
1 file changed, 40
Add support for Low power transition support in nand driver. Also
ensures the current transaction finishes before going to low power mode
with _suspend support in mtd layer.
Signed-off-by: Philip Avinash avinashphi...@ti.com
---
drivers/mtd/nand/omap2.c | 19 +++
1 file
Hi Jon,
On 02/06/2013 10:03 PM, Jon Hunter wrote:
Adds device-tree bindings from SDMA on OMAP2+ devices. DMA client
bindings are also added for devices that have SPI and MMC bindings
populated. Client binding data is based upon existing HWMOD data for
OMAP and has been checked against OMAP
On Thursday 07 February 2013 14:18:05 Peter Ujfalusi wrote:
I looked briefly around in the mentioned code and I wonder how this is going
to work with audio (ASoC).
When we boot with DT it looks like we are _not_ creating the DMA resources for
the device as it is done for the IRQ and IO/MEM. So
On Thu, Feb 7, 2013 at 11:16 AM, Roger Quadros rog...@ti.com wrote:
snip
It seems the beagleboard problem is related to OMAP silicon errata [1].
Apparently, remote wakeup as well as host issued wakeup break omap-ehci and
have
nothing to do with the hub or it's driver.
I'll work on this
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030, MMC1,
On Wednesday 06 February 2013, Jon Hunter wrote:
+static struct of_dma_filter_info info;
Both members of this structure are constant, so you can just initialize it here,
and it would be nice to give it a more descriptive name, such as
omap_dmadev_info.
static struct platform_driver
On Wednesday 06 February 2013, Jon Hunter wrote:
Add SDMA controller binding for OMAP2+ devices and populate DMA client
information for SPI and MMC periperhal on OMAP3+ devices. Please note
that OMAP24xx devices do not have SPI and MMC bindings available yet and
so DMA client information is
Hi,
This patch adds support for TC358765 DSI-to-LVDS transmitter
from Toshiba, that is used in OMAP4 Blaze Tablet development
platform. It was originally developed a long time ago and
was used internally survived few kernel migrations.
Different people worked in this driver during last two
years
From: Tomi Valkeinen tomi.valkei...@ti.com
TC358765 is DSI-to-LVDS transmitter from Toshiba, used in
OMAP44XX Blaze Tablet and Blaze Tablet2 boards.
Signed-off-by: Dan Murphy dmur...@ti.com
Signed-off-by: Sergiy Kibrik sergiy.kib...@globallogic.com
Signed-off-by: Volodymyr Riazantsev
On Thu, Feb 07, 2013 at 03:30:56, Paul Walmsley wrote:
Hi Vaibhav,
On Thu, 24 Jan 2013, Bedia, Vaibhav wrote:
I could not track down U-Boot that you were using
It's posted now at:
http://www.pwsan.com/omap/bootloaders/beaglebone/u-boot/2011.09-9-gcf6e04d__20120803171543/
Care
On Wed, 6 Feb 2013, Alan Stern wrote:
Is this issue fixed ?
Actually we too are getting very similar issue with samsung exynos5250
hardware.
With latest 'usb-next' kernel and supporting arch patches, when i use
following test scenerio:
Connect a USB 2.0 external hub to USB 2.0
Hi,
TC358765 is DSI-to-LVDS transmitter from Toshiba, used in
OMAP44XX Blaze Tablet and Blaze Tablet2 boards.
I had a really fast look and I have few comments
+static int tc358765_read_register(struct omap_dss_device *dssdev,
+ u16 reg, u32 *val)
+{
+
On 02/07/2013 08:39 AM, Arnd Bergmann wrote:
On Wednesday 06 February 2013, Jon Hunter wrote:
+static struct of_dma_filter_info info;
Both members of this structure are constant, so you can just initialize it
here,
and it would be nice to give it a more descriptive name, such as
This is because we want to get rid of platform_data usage from probe().
The only information we need is PORT_MODE, and this can be supplied
to us by the user (i.e. omap-usb-host.c).
We also move channel clock management from runtime PM handlers into
omap_tll_enable/disable().
CC: Samuel Ortiz
Allows the OMAP HS USB host controller to be specified
via device tree.
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
---
.../devicetree/bindings/mfd/omap-usb-host.txt | 80 ++
drivers/mfd/omap-usb-host.c| 160
Provide RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin multiplexer information for USB host
pins.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 71
1 files
The module alias should be ehci-omap and not
omap-ehci to match the platform device name.
The omap-ehci module should now autoload correctly.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/host/ehci-omap.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git
Provide the RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin multiplexer information for the USB host
pins.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 55 +
1
Allows the OHCI controller found in OMAP3 and later chips to
be specified via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
.../devicetree/bindings/usb/omap3-ohci.txt | 17 +
drivers/usb/host/ohci-omap3.c
Allows the OMAP EHCI controller to be specified via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
.../devicetree/bindings/usb/omap-ehci.txt | 34 ++
drivers/usb/host/ehci-omap.c | 36
Adds device nodes for HS USB Host module, TLL module,
OHCI and EHCI controllers.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3.dtsi | 31 +++
1 files changed, 31 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi
Adds device nodes for HS USB Host module, TLL module,
OHCI and EHCI controllers.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 30 ++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi
Since there is only one resource per type we don't really need
to use resource name to obtain it. This also also makes it easier
for device tree adaptation.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
drivers/usb/host/ohci-omap3.c |5 ++---
1
Hi,
This patchset adds device tree support for OMAP's High Speed USB Host
subsystem. Board adaptation for Panda and Beagleboard is also provided.
Tested on Beagleboard.
Will not yet work on Pandaboard as PHY clock is not provided in device tree.
We will need to address the PHY clock as per the
The PHY clock, clock rate, VCC regulator and RESET regulator
can now be provided via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
---
.../devicetree/bindings/usb/usb-nop-xceiv.txt | 34 ++
drivers/usb/otg/nop-usb-xceiv.c
Add 2 flags, needs_vcc and needs_reset to platform data.
If the flag is set and the regulator couldn't be found
then we bail out with -EPROBE_DEFER.
For device tree boot we depend on presensce of vcc-supply/
reset-supply properties to decide if we should bail out
with -EPROBE_DEFER or just
Enable this driver to probe in device tree boot.
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
---
.../devicetree/bindings/mfd/omap-usb-tll.txt | 17 +
drivers/mfd/omap-usb-tll.c |9 +
2 files
Since there is only one resource per type we don't really need
to use resource name to obtain it. This also also makes it easier
for device tree adaptation.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
drivers/usb/host/ehci-omap.c |7 +++
On Thursday 07 February 2013 09:51:11 Jon Hunter wrote:
@@ -673,7 +702,7 @@ static int omap_dma_init(void)
{
int rc = platform_driver_register(omap_dma_driver);
-if (rc == 0) {
+if ((rc == 0) (!of_have_populated_dt())) {
pdev =
On Thu, 7 Feb 2013, Roger Quadros wrote:
The module alias should be ehci-omap and not
omap-ehci to match the platform device name.
The omap-ehci module should now autoload correctly.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
Hi Antonio,
On Wednesday 06 February 2013 23:33:47 Antonio Ospite wrote:
On Wed, 30 Jan 2013 01:23:48 +0100 Laurent Pinchart wrote:
On Monday 28 January 2013 13:22:10 Antonio Ospite wrote:
Hi,
looking at the MIPI Alliance Specification for Camera Serial Interface
2 (I'll call it
Hello,
I have a couple of minor comments.
On Thu, Feb 07, 2013 at 02:11:37PM +, Anil Kumar wrote:
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG
From: Rob Herring rob.herr...@calxeda.com
Now that we have OF based init with CLKSRC_OF, convert smp_twd init
function to use it and covert all callers of
twd_local_timer_of_register.
Signed-off-by: Rob Herring rob.herr...@calxeda.com
Cc: Shawn Guo shawn@linaro.org
Cc: Sascha Hauer
On 02/07/2013 01:53 PM, Rob Herring wrote:
From: Rob Herring rob.herr...@calxeda.com
Now that we have OF based init with CLKSRC_OF, convert smp_twd init
function to use it and covert all callers of
twd_local_timer_of_register.
Reviewed-by: Stephen Warren swar...@nvidia.com
Thanks for
Hi Aaro,
Introduce Retu watchdog driver.
Cc: linux-watch...@vger.kernel.org
Acked-by: Felipe Balbi ba...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Wim Van Sebroeck w...@iguana.be
Added tolinux-watchdog-next.
Kind regards,
Wim.
Not tainted (3.8.0-rc6-next-20130207-00016-g735c237
#35)
[2.317169] PC is at twl_i2c_read+0x3c/0xec
[2.321563] LR is at twl_i2c_read+0x1c/0xec
[2.325988] pc : [c0333950]lr : [c0333930]psr: 8153
[2.325988] sp : c702fed0 ip : fp :
[2.338043] r10
Add SDMA controller binding for OMAP2+ devices and populate DMA client
information for SPI and MMC periperhal on OMAP3+ devices. Please note
that OMAP24xx devices do not have SPI and MMC bindings available yet and
so DMA client information is not populated.
Signed-off-by: Jon Hunter
Adds device-tree bindings from SDMA on OMAP2+ devices. DMA client
bindings are also added for devices that have SPI and MMC bindings
populated. Client binding data is based upon existing HWMOD data for
OMAP and has been checked against OMAP documentation.
Please note that the underlying (legacy)
If the device-tree blob is present during boot, then register the SDMA
controller with the device-tree DMA driver so that we can use device-tree
to look-up DMA client information.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/dma.c |4
drivers/dma/omap-dma.c|
Paul Walmsley p...@pwsan.com writes:
On Mon, 4 Feb 2013, Rajendra Nayak wrote:
OMAP4 CHIP level PM works only with newer bootloaders. The
dependency on the bootloader comes from the fact that the
kernel is missing reset and initialization code for some
devices.
While the right thing to
[2.306243] Modules linked in:
[2.309448] CPU: 0Not tainted (3.8.0-rc6-next-20130207-00016-g735c237
#35)
[2.317169] PC is at twl_i2c_read+0x3c/0xec
[2.321563] LR is at twl_i2c_read+0x1c/0xec
[2.325988] pc : [c0333950]lr : [c0333930]psr: 8153
[2.325988] sp
On Thu, Feb 07, 2013 at 07:05:05PM -0600, Jon Hunter wrote:
Add SDMA controller binding for OMAP2+ devices and populate DMA client
information for SPI and MMC periperhal on OMAP3+ devices. Please note
that OMAP24xx devices do not have SPI and MMC bindings available yet and
so DMA client
Hi,
On Thu, Feb 07, 2013 at 07:05:06PM -0600, Jon Hunter wrote:
If the device-tree blob is present during boot, then register the SDMA
controller with the device-tree DMA driver so that we can use device-tree
to look-up DMA client information.
Signed-off-by: Jon Hunter jon-hun...@ti.com
55 matches
Mail list logo
