On 12/12/2013 09:35 AM, Archit Taneja wrote:
The VPE and VIP IPs in DRA7x contain common scaler and color conversion
hardware
blocks. We create libraries for these components such that the vpe driver and
the vip driver(in future) can use these library funcs to configure the blocks.
There
On 12/17/2013 08:52 AM, Hans Verkuil wrote:
On 12/03/2013 12:51 PM, Archit Taneja wrote:
This series fixes 2 issues in the VPE driver. The first fix allows us to use
UYVY color format for source and destination buffers. The second fix makes
sure
we don't set pixel format widths which the
On Tue, 26 Nov 2013, Tero Kristo wrote:
ti_dt_clk_init_provider() can now be used to initialize the contents of
a single clock IP block. This parses all the clocks under the IP block
and calls the corresponding init function for them.
This patch also introduces a helper function for the TI
On 12/17/2013 10:14 AM, Paul Walmsley wrote:
On Tue, 26 Nov 2013, Tero Kristo wrote:
ti_dt_clk_init_provider() can now be used to initialize the contents of
a single clock IP block. This parses all the clocks under the IP block
and calls the corresponding init function for them.
This patch
On Tue, 17 Dec 2013, Tero Kristo wrote:
On 12/17/2013 10:14 AM, Paul Walmsley wrote:
On Tue, 26 Nov 2013, Tero Kristo wrote:
ti_dt_clk_init_provider() can now be used to initialize the contents of
a single clock IP block. This parses all the clocks under the IP block
and calls the
On Tue, 26 Nov 2013, Tero Kristo wrote:
The OMAP clock driver now supports DPLL clock type. This patch also
adds support for DT DPLL nodes.
Signed-off-by: Tero Kristo t-kri...@ti.com
...
+/*
+ * struct clk_hw_omap.flags possibilities
+ *
+ * XXX document the rest of the clock flags
On Tue, 26 Nov 2013, Tero Kristo wrote:
The OMAP clock driver now supports DPLL clock type. This patch also
adds support for DT DPLL nodes.
Signed-off-by: Tero Kristo t-kri...@ti.com
...
diff --git a/drivers/clk/ti/dpll.c b/drivers/clk/ti/dpll.c
new file mode 100644
index
On Tue, 26 Nov 2013, Tero Kristo wrote:
clk-44xx.c now contains the clock init functionality for omap4, including
DT clock registration and adding of static clkdev entries.
...
diff --git a/drivers/clk/ti/clk-44xx.c b/drivers/clk/ti/clk-44xx.c
new file mode 100644
index 000..3e2090b
On Tue, 26 Nov 2013, Tero Kristo wrote:
This patch creates a unique node for each clock in the OMAP4 power,
reset and clock manager (PRCM). OMAP443x and OMAP446x have slightly
different clock tree which is taken into account in the data.
Signed-off-by: Tero Kristo t-kri...@ti.com
...
On Tue, 26 Nov 2013, Tero Kristo wrote:
This patch creates a unique node for each clock in the DRA7 power,
reset and clock manager (PRCM).
TODO: apll_pcie clock node is still a dummy in this version, and
proper support for the APLL should be added.
...
---
arch/arm/boot/dts/dra7.dtsi
On Tue, 26 Nov 2013, Tero Kristo wrote:
This patch creates a unique node for each clock in the AM33xx power,
reset and clock manager (PRCM).
Signed-off-by: Tero Kristo t-kri...@ti.com
...
---
arch/arm/boot/dts/am33xx-clocks.dtsi | 662
++
On Tue, 26 Nov 2013, Tero Kristo wrote:
This patch creates a unique node for each clock in the OMAP5 power,
reset and clock manager (PRCM).
Signed-off-by: Tero Kristo t-kri...@ti.com
...
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 17fe896..3920087
On Tue, 26 Nov 2013, Tero Kristo wrote:
This patch creates a unique node for each clock in the OMAP3 power,
reset and clock manager (PRCM).
Signed-off-by: Tero Kristo t-kri...@ti.com
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index f3a0c26..9e6ea02 100644
On Tue, 26 Nov 2013, Tero Kristo wrote:
This patch creates a unique node for each clock in the AM43xx power,
reset and clock manager (PRCM).
Signed-off-by: Tero Kristo t-kri...@ti.com
...
diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
index 974d103..18f2401
On 12/17/2013 11:44 AM, Paul Walmsley wrote:
On Tue, 26 Nov 2013, Tero Kristo wrote:
This patch creates a unique node for each clock in the OMAP4 power,
reset and clock manager (PRCM). OMAP443x and OMAP446x have slightly
different clock tree which is taken into account in the data.
The DMM/Tiler block can used by omapdrm to allocate frame buffers. With the
removal of address and irq data from the omap4 hwmods, the probe of DMM driver
fails and omapdrm isn't able to utilize the DMM hardware.
Add DMM bindings for OMAP4 and OMAP5 and DRA7x.
Changes in v5:
- Use of_match_ptr()
Enable use of DT for DMM/Tiler.
Originally worked on by Andy Gross andy...@gmail.com
Cc: Andy Gross andy...@gmail.com
Cc: DRI Development dri-de...@lists.freedesktop.org
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 7 +++
1 file changed, 7
Add Dynamic Memory Manager (DMM) bindings for OMAP4 and OMAP5 and DRA7x devices.
DMM only requires address and irq information.
Add documentation for the DMM bindings.
Originally worked on by Andy Gross andy...@gmail.com
Cc: Andy Gross andy...@gmail.com
Signed-off-by: Archit Taneja
On Mon, 16 Dec 2013, Felipe Balbi wrote:
Introduce an irq_chip and irq_domain for menelaus driver. Following
patches will convert uses to traditional request_threaded_irq().
While at that, some better error handling had to be added, so we could
free irq descs we allocated.
Tested-by:
Now that we have our own irq_chip, all children can use traditional
request_threaded_irq().
Is it possible to convert these to managed resources (*_devm)?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter
DISPC pipeline DMAs preload some bytes of pixel data in the vertical blanking
region before the start of each frame. The preload ensures the pipeline doesn't
underflow when the active region of the display starts.
DISPC_GFX/VIDp_PRELOAD registers allow us to program how many bytes of data
should
Hi Hans,
On Tuesday 17 December 2013 01:30 PM, Hans Verkuil wrote:
On 12/12/2013 09:35 AM, Archit Taneja wrote:
The VPE and VIP IPs in DRA7x contain common scaler and color conversion hardware
blocks. We create libraries for these components such that the vpe driver and
the vip driver(in
On 12/17/13 12:19, Archit Taneja wrote:
Hi Hans,
On Tuesday 17 December 2013 01:30 PM, Hans Verkuil wrote:
On 12/12/2013 09:35 AM, Archit Taneja wrote:
The VPE and VIP IPs in DRA7x contain common scaler and color
conversion hardware blocks. We create libraries for these
components such
Hi,
On Tuesday 17 December 2013 05:19 PM, Hans Verkuil wrote:
On 12/17/13 12:19, Archit Taneja wrote:
Hi Hans,
On Tuesday 17 December 2013 01:30 PM, Hans Verkuil wrote:
On 12/12/2013 09:35 AM, Archit Taneja wrote:
The VPE and VIP IPs in DRA7x contain common scaler and color
conversion
On Tue, 26 Nov 2013, Tero Kristo wrote:
Current clock wrappers assume simple and direct mapped hardware register
access. Improve this support by adding functionality for registering
platform specific clock I/O wrappers, which can be used to support
various features needed like endianess
When booting with a devietree, no platform data is provided. Do not prematurely
exit iommu_enable() and iommu_disable() in such a case.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
drivers/iommu/omap-iommu.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff
Currently, bus_set_iommu() is done in omap_iommu_init(). However,
omap_iommu_probe() can fail in a number of ways, leaving the platform
bus with a dangling reference to a non-initialized iommu. Perform
bus_set_iommu() only if omap_iommu_probe() succeed.
Signed-off-by: Florian Vaussard
omap_iommu_attach() returns NULL or ERR_PTR in case of error, but
omap_iommu_attach_dev() only checks for IS_ERR. Thus a NULL return value (in
case driver_find_device fails) will cause the kernel to panic when
omap_iommu_attach_dev() dereferences the pointer.
In such case, omap_iommu_attach()
Add missing information required to probe the iommu for the camera
subsystem.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3.dtsi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi
The data are now passed using the devicetree.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 8
1 file changed, 8 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
With full DT boot, the platform specific part of the OMAP iommu
is not useful anymore.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/mach-omap2/Makefile | 3 --
arch/arm/mach-omap2/omap-iommu.c | 79
2 files changed, 82
OMAP2+ is heading towards a full device tree boot for 3.14. Currently,
the iommu used by the OMAP3 camera subsystem is not yet converted. It
cannot be probed as necessary data are only passed through device tree.
Patches 1 and 2 are small fixes for problems encountered while developing
this
As OMAP2+ is moving to a full DT boot for 3.14, commit 7ce93f3
ARM: OMAP2+: Fix more missing data for omap3.dtsi file adds
basic DT bits. But the driver is not yet converted, so this will
not work and driver will not be probed. Convert it!
Apart from standard bindings, this patch uses
Hi!
I've noticed on a custom OMAP3530 board, that the SDcard (mmc1) is only
detected, when its previously used in U-Boot (e.g. by mmc rescan). So
I tested on beagleboard and it behaved identical.
Here the boot log with U-Boot scanning mmc before Linux booting:
root@generic-armv7a:~# dmesg |
On Tuesday 17 December 2013 07:11 PM, Stefan Roese wrote:
Hi!
I've noticed on a custom OMAP3530 board, that the SDcard (mmc1) is only
detected, when its previously used in U-Boot (e.g. by mmc rescan). So
I tested on beagleboard and it behaved identical.
Here the boot log with U-Boot scanning
On 17.12.2013 14:48, Balaji T K wrote:
On Tuesday 17 December 2013 07:11 PM, Stefan Roese wrote:
Hi!
I've noticed on a custom OMAP3530 board, that the SDcard (mmc1) is only
detected, when its previously used in U-Boot (e.g. by mmc rescan). So
I tested on beagleboard and it behaved identical.
Hi Tomi,
On Tuesday 17 December 2013 09:15:58 Tomi Valkeinen wrote:
On 2013-12-17 09:05, Sascha Hauer wrote:
On Mon, Dec 16, 2013 at 04:56:30PM +0200, Tomi Valkeinen wrote:
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/displays-new/connector-dvi.c | 43
* Paul Walmsley p...@pwsan.com [131216 23:16]:
On Fri, 13 Dec 2013, Tony Lindgren wrote:
OK posted a patch for the SBC-T3730 with minimal support also for
SBC-3530 and SBC-3517 that should boot far enough to start adding
more devices. Paul, care to try it on the CM-T3517, the patch is:
* Tomi Valkeinen tomi.valkei...@ti.com [131216 22:47]:
On 2013-12-16 20:41, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [131216 06:59]:
As a temporary solution to enable DSS for selected boards when booting
with DT, a hack was added to board-generic.c in
From: Andreas Naumann anaum...@ultratronik.de
This is a hard to reproduce problem which leads to non-functional
USB-OTG port in 0.1%-1% of all boots. Tracked it down to commit
e25bec160158abe86c276d7d206264afc3646281, which introduces save/restore
of OTG_INTERFSEL over suspend.
Since the resume
Hello
On 12/16/2013 03:56 PM, Tomi Valkeinen wrote:
This is a test for Overo with Palo43 expansion, _not_ Tobi. Palo43
doesn't have a dts, but seems to work ok with omap3-tobi.dts, so I used
it as a test.
Not to be merged.
FYI, I got the DVI (HDMI connector) on the Overo/Tobi to work
On Tue, Dec 17, 2013 at 09:37:35AM +0200, Tomi Valkeinen wrote:
Hi,
On 2013-12-13 20:17, Sebastian Reichel wrote:
Hi,
This patchset adds DT support for the N900 panel. The patchset is based on
Tomi's work/dss-dt-2 branch [0]. I suggest to send the DT changes through
Benoits queue,
On 2013-12-17 19:14, Sebastian Reichel wrote:
On Tue, Dec 17, 2013 at 09:37:35AM +0200, Tomi Valkeinen wrote:
Hi,
On 2013-12-13 20:17, Sebastian Reichel wrote:
Hi,
This patchset adds DT support for the N900 panel. The patchset is based on
Tomi's work/dss-dt-2 branch [0]. I suggest to send
On Tue, Dec 17, 2013 at 05:48:33PM +0100, anaum...@ultratronik.de wrote:
From: Andreas Naumann anaum...@ultratronik.de
This is a hard to reproduce problem which leads to non-functional
USB-OTG port in 0.1%-1% of all boots. Tracked it down to commit
e25bec160158abe86c276d7d206264afc3646281,
On 16.12.2013 20:34, Sebastian Reichel wrote:
Hi,
On Mon, Dec 16, 2013 at 02:31:53PM +0100, Linus Walleij wrote:
I am very reluctant in letting device trees specify exports of GPIOs
to userspace, not so much because it's Linux-specific but for
the fact that people are doing things in
From: Mugunthan V N mugunthan...@ti.com
Date: Fri, 13 Dec 2013 14:35:27 +0530
During checking the interrupts with cat /proc/interrupts, it is showing
device name as (null), this change was done with commit id aa1a15e2d where
request_irq is changed to devm_request_irq also changing the irq name
* Igor Grinberg grinb...@compulab.co.il [131216 23:16]:
On 12/16/13 21:17, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [131216 05:57]:
On 12/13/13 21:22, Tony Lindgren wrote:
Ok. So what do you think, is it fine to have something like:
omap3-cm-t3x.dtsi -
On 12/09/2013 03:55 PM, Nishanth Menon wrote:
Craneboard is a hardware development platform based on the Sitara
AM3517 ARM Cortex - A8 microprocessor device - see [1] for more
details. Add basic devices for craneboard as replacement for the board
file scheduled for removal as part of device
Tony Lindgren t...@atomide.com writes:
* Tony Lindgren t...@atomide.com [131210 12:27]:
The following changes since commit f2e2c9d9b4087b74eb9e00d8dfac148354cb0b71:
ARM: dts: Fix booting for secure omaps (2013-12-06 15:30:43 -0800)
are available in the git repository at:
On Tue, Dec 17, 2013 at 07:58:56PM +0200, Ivajlo Dimitrov wrote:
On Mon, Dec 16, 2013 at 02:31:53PM +0100, Linus Walleij wrote:
I am very reluctant in letting device trees specify exports of GPIOs
to userspace, not so much because it's Linux-specific but for
the fact that people are doing
On Thu, Dec 12, 2013 at 03:38:38PM -0600, Felipe Balbi wrote:
hi all,
these patches add pm_runtime support for all glue layers.
I plan to add pm_runtime support for dwc3 after these
patches are merged upstream.
Please test.
At first time I failed to notice you were removing #ifdef's
On Tue, Dec 17, 2013 at 03:31:40PM -0800, David Cohen wrote:
On Thu, Dec 12, 2013 at 03:38:38PM -0600, Felipe Balbi wrote:
hi all,
these patches add pm_runtime support for all glue layers.
I plan to add pm_runtime support for dwc3 after these
patches are merged upstream.
Please
* Tomi Valkeinen tomi.valkei...@ti.com [131215 23:26]:
On 2013-12-14 16:09, Tony Lindgren wrote:
Why was e30b06f4d5f000c31a7747a7e7ada78a5fd419a1 merged into -rc2? It's
not a fix, just a cleanup.
Hmm OK sorry looks like I removed some non-legacy mux framework code
by accident. The
Quoting Tero Kristo (2013-12-16 00:13:08)
On 12/15/2013 06:23 AM, Mike Turquette wrote:
Quoting Tero Kristo (2013-11-26 00:05:51)
Some OMAP clocks require knowledge about their parent clockdomain for
book keeping purposes. This patch creates a new DT binding for TI
clockdomains, which act
On Tue, 17 Dec 2013, Paul Walmsley wrote:
On Tue, 26 Nov 2013, Tero Kristo wrote:
Current clock wrappers assume simple and direct mapped hardware register
access. Improve this support by adding functionality for registering
platform specific clock I/O wrappers, which can be used to
On 2013-12-17 17:30, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [131216 22:47]:
On 2013-12-16 20:41, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [131216 06:59]:
As a temporary solution to enable DSS for selected boards when booting
with DT, a hack was added to
Am 17.12.2013 18:22, schrieb David Cohen:
On Tue, Dec 17, 2013 at 05:48:33PM +0100, anaum...@ultratronik.de wrote:
From: Andreas Naumann anaum...@ultratronik.de
This is a hard to reproduce problem which leads to non-functional
USB-OTG port in 0.1%-1% of all boots. Tracked it down to commit
57 matches
Mail list logo
