On Tuesday 25 September 2012 08:03 PM, Tomi Valkeinen wrote:
On Tue, 2012-09-25 at 11:49 +0530, Archit Taneja wrote:
Writeback uses the WB_PICTURE_SIZE register to define the size of the content
written to memory, this is the output of the scaler. It uses the WB_SIZE
register to define the size
On Wed, 2012-09-26 at 11:52 +0530, Archit Taneja wrote:
On Tuesday 25 September 2012 08:03 PM, Tomi Valkeinen wrote:
On Tue, 2012-09-25 at 11:49 +0530, Archit Taneja wrote:
Writeback uses the WB_PICTURE_SIZE register to define the size of the
content
written to memory, this is the output
On Tue, 2012-09-25 at 12:07 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [120925 10:06]:
On Tue, 2012-09-25 at 08:38 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [120925 03:22]:
Hi Tony,
Each pin of OMAP requires a particular power to
On Fri, Sep 21, 2012 at 23:52:11, Porter, Matt wrote:
On Fri, Sep 21, 2012 at 08:27:07AM +, Hebbar, Gururaja wrote:
On Thu, Sep 20, 2012 at 20:13:33, Porter, Matt wrote:
This series adds DMA Engine support for AM33xx, which uses
an EDMA DMAC. The EDMA DMAC has been previously
Hi,
On Mon, Sep 17, 2012 at 3:03 PM, Marc Kleine-Budde m...@pengutronix.de wrote:
On 09/14/2012 03:06 PM, ABRAHAM, KISHON VIJAY wrote:
[...]
diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
new file mode 100644
index 000..c55446a
--- /dev/null
+++ b/drivers/phy/phy-core.c
On 09/26/2012 11:20 AM, ABRAHAM, KISHON VIJAY wrote:
Hi,
On Mon, Sep 17, 2012 at 3:03 PM, Marc Kleine-Budde m...@pengutronix.de
wrote:
On 09/14/2012 03:06 PM, ABRAHAM, KISHON VIJAY wrote:
[...]
diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
new file mode 100644
index
On Mon, 2012-09-17 at 13:52 +0300, Grazvydas Ignotas wrote:
On Thu, Sep 13, 2012 at 6:06 PM, Raphael Assenat r...@8d.com wrote:
When the omap2 nand flash driver is used, the nand-disk led trigger does not
work due to nand_wait_ready not being called.
I think better solution is just to
Hi Benoit,
On Tue, Sep 18, 2012 at 11:00:28, Philip, Avinash wrote:
Add McSPI data node to AM33XX device tree file. The McSPI module (and so
as the driver) is reused from OMAP4.
Signed-off-by: Philip, Avinash avinashphi...@ti.com
Tested-by: Matt Porter mpor...@ti.com
I haven't
On Wed, Sep 12, 2012 at 17:32:38, Hebbar, Gururaja wrote:
On Wed, Sep 12, 2012 at 14:19:51, S, Venkatraman wrote:
On Tue, Sep 4, 2012 at 6:39 PM, Hebbar, Gururaja gururaja.heb...@ti.com
wrote:
HSMMC IP on AM33xx need a special setting to handle High-speed cards.
Other platforms like
Hi Tero,
On 09/25/2012 07:33 PM, Tero Kristo wrote:
With the new parameters, I2C can now be put to high speed mode for
better performance.
We have twl6040 on the same bus. have you tried this with audio enabled?
twl6040 is in standard mode (up to 100 kbps) after power up...
Signed-off-by:
Hi,
With a patched 3.6rc7 on my beaglebone I can set the pinmux for pins using
pinctrl and that seems to work. On the 3.2 vendor tree there was the omap_mux
driver with an awesome debugfs interface:
# cat /sys/kernel/debug/omap_mux/lcd_data0
name: lcd_data0.ehrpwm2A (0x44e108a0/0x8a0 =
On Tue, Sep 25, 2012 at 7:05 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
So when I call pm_runtime_get in the omapdss driver, I imagine that the
runtime PM and pinctrl would together handle muxing the pins for
omapdss's use, and also enable the relevant regulators to make the pins
usable.
On Wed, 2012-09-26 at 14:39 +0300, Peter Ujfalusi wrote:
Hi Tero,
On 09/25/2012 07:33 PM, Tero Kristo wrote:
With the new parameters, I2C can now be put to high speed mode for
better performance.
We have twl6040 on the same bus. have you tried this with audio enabled?
twl6040 is in
On 09/26/2012 03:06 PM, Tero Kristo wrote:
On Wed, 2012-09-26 at 14:39 +0300, Peter Ujfalusi wrote:
Hi Tero,
On 09/25/2012 07:33 PM, Tero Kristo wrote:
With the new parameters, I2C can now be put to high speed mode for
better performance.
We have twl6040 on the same bus. have you tried
On Wed, 2012-09-26 at 13:46 +0200, Linus Walleij wrote:
On Tue, Sep 25, 2012 at 7:05 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
So when I call pm_runtime_get in the omapdss driver, I imagine that the
runtime PM and pinctrl would together handle muxing the pins for
omapdss's use, and
Adding Linus W. and lkml.
On Wed, Sep 26, 2012 at 01:46:45PM +0200, Koen Kooi wrote:
Hi,
With a patched 3.6rc7 on my beaglebone I can set the pinmux for pins using
pinctrl and that seems to work. On the 3.2 vendor tree there was the omap_mux
driver with an awesome debugfs interface:
#
Hi Aaro
On Thu, 30 Aug 2012 13:40:30 -0700
Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120829 08:30]:
On Wed, Aug 29, 2012 at 8:24 AM, Aaro Koskinen aaro.koski...@iki.fi wrote:
In some OMAP3 HS devices (at least Nokia N9 and N950), the public SRAM
On Wed, Sep 26, 2012 at 08:26:19AM +, Hebbar, Gururaja wrote:
On Fri, Sep 21, 2012 at 23:52:11, Porter, Matt wrote:
On Fri, Sep 21, 2012 at 08:27:07AM +, Hebbar, Gururaja wrote:
On Thu, Sep 20, 2012 at 20:13:33, Porter, Matt wrote:
This series adds DMA Engine support for AM33xx,
On Wed, Sep 26, 2012 at 2:56 PM, Matt Porter mpor...@ti.com wrote:
Adding Linus W. and lkml.
On Wed, Sep 26, 2012 at 01:46:45PM +0200, Koen Kooi wrote:
Hi,
With a patched 3.6rc7 on my beaglebone I can set the pinmux for pins using
pinctrl and that seems to work. On the 3.2 vendor tree there
On Wed, Sep 26, 2012 at 2:56 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
[Me]
You can very well do clocks and regulators in these functions as well.
That's not really what I mean. The regulators in question are OMAP
version specific, so the driver shouldn't know which regulators are
On Wed, Sep 26, 2012 at 03:09:03PM +0530, Thirumalesha N wrote:
Dear Sir/Madam,
I'm testing PMC type SM502 based Graphics card which has usb,
audio and display interfaces.
I'm using kernel version linux-2.6.21 with redhat enterprise 5.5
OS.
As you are testing
This series enables uio_pruss on AM33xx and it mostly intended to look
for the proper solution to handling this particular OMAP hwmod which
contains hardware reset lines.
The comment in arch/arm/mach-omap2/omap_hwmod.c:
/*
* If an IP block contains HW reset lines and any of them
This optional binding extension allows specification of a hwmod
and associate hardware reset line which should be deasserted for
the device to be functional.
The implementation works for reference as to the problem that
exists for utilizing uio_pruss on AM33xx but is suboptimal. The
problem is
Adds a pruss node and an example of use on Beaglebone.
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/boot/dts/am335x-bone.dts |4
arch/arm/boot/dts/am33xx.dtsi | 11 +++
2 files changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-bone.dts
Add ifdefery hacks to only use SRAM on Davinci. This
needs to be cleaned up with a sane generic SRAM allocator
(like the DT based driver available that can't be used on
Davinci which is just starting DT conversion) before it
can go upstream.
Adds DT, pinctrl, and runtime PM support for use on
Hi,
On Tue, Sep 25, 2012 at 2:39 PM, Philippe De Swert
Then maybe it's best to just remove the ifdefs and always provide
generic_interrupt() ?
Anyone against it ?
Providing generic_interrupt seems fine.
Well it seems there are only two drivers that
Hi,
On Wed, 2012-09-26 at 10:45 +0530, Chandrabhanu Mahapatra wrote:
Hi everyone,
this patch series aims at cleaning up of DSS of printk()'s enabled with
dss_debug and replace them with generic dynamic debug printing.
The 1st patch
* replaces printk() in DSSDBG definition with pr_debug()
The PHY framework provides a set of API's for the PHY drivers to
create/destroy a PHY and API's for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
using phandle, the platform specfic intialization code (say from board file)
Hi All,
I appear to be having problems receiving emails being sent to me by the
mailing lists. I did not receive any of the responses to this patch set,
but I know see online that there have been a few responses. So sorry for
not responding.
I have been complaining to our IT department but all
Hi Rob,
On 09/13/2012 06:31 PM, Jon Hunter wrote:
In order to add device-tree support to the timer driver the following changes
were made ...
1. Allocate system timers (used for clock-events and clock-source) based upon
timer properties rather than using an hard-coded timer instance ID.
On 09/26/2012 10:51 AM, Jon Hunter wrote:
Hi Rob,
#define OMAP3_32K_SOURCEomap_32k_fck
#define OMAP4_32K_SOURCEsys_32k_ck
+#define TIMER_PROP_ALWONti,timer-alwon
+
I see you made the following comment [1] here ...
It would be easier to follow the code if you use the
On Wed, Sep 26, 2012 at 03:03:27PM +0200, Linus Walleij wrote:
On Wed, Sep 26, 2012 at 2:56 PM, Matt Porter mpor...@ti.com wrote:
Adding Linus W. and lkml.
On Wed, Sep 26, 2012 at 01:46:45PM +0200, Koen Kooi wrote:
Hi,
With a patched 3.6rc7 on my beaglebone I can set the pinmux for pins
Use the enum for board_ref_clock from linux/wl12xx.h
Signed-off-by: Vikram Narayanan vikram...@gmail.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
---
I'm not subscribed to the list. So please keep me in Cc for the replies.
arch/arm/mach-omap2/board-omap4panda.c |
On 09/20/2012 06:53 PM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [120919 19:24]:
Hi Tony,
I was about to take the DTS patch, but was wondering if you will pull
the driver changes for 3.7.
I suggest that you do a separate branch on top of Paul's hwmod series
when he posts
On Wed, 2012-09-26 at 20:31 +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/destroy a PHY and API's
Just some trivial notes.
diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
[]
@@ -0,0 +1,445 @@
[]
+static void
On Wed, Sep 26, 2012 at 08:31:15PM +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/destroy a PHY and API's for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
Op 26 sep. 2012, om 18:15 heeft Matt Porter mpor...@ti.com het volgende
geschreven:
On Wed, Sep 26, 2012 at 03:03:27PM +0200, Linus Walleij wrote:
On Wed, Sep 26, 2012 at 2:56 PM, Matt Porter mpor...@ti.com wrote:
Adding Linus W. and lkml.
On Wed, Sep 26, 2012 at 01:46:45PM +0200, Koen Kooi
On Wednesday, September 26, 2012 09:57:57 AM Joe Perches wrote:
On Wed, 2012-09-26 at 20:31 +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/destroy a PHY and API's
Just some trivial notes.
diff --git a/drivers/phy/phy-core.c
On 09/26/2012 07:41 PM, Dmitry Torokhov wrote:
On Wednesday, September 26, 2012 09:57:57 AM Joe Perches wrote:
On Wed, 2012-09-26 at 20:31 +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/destroy a PHY and API's
Just some trivial
Hi,
On Wed, Sep 26, 2012 at 11:10:48AM +0530, ABRAHAM, KISHON VIJAY wrote:
Hi,
On Wed, Sep 19, 2012 at 5:26 PM, Felipe Balbi ba...@ti.com wrote:
On Wed, Sep 19, 2012 at 05:00:29PM +0530, Kishon Vijay Abraham I wrote:
usb_otg_ss_refclk960m is needed by usb2 phy present in omap5. For
McSPI driver previously assumed that D0 was input (MISO) and D1 was output
(MOSI).
This forces the hardware designer to wire all SPI peripherals in this way when
it should be a software configuration option.
Signed-off-by: Stan Hu sta...@gmail.com
---
arch/arm/plat-omap/include/plat/mcspi.h |
* Koen Kooi k...@dominion.thruhere.net [120926 10:23]:
Op 26 sep. 2012, om 18:15 heeft Matt Porter mpor...@ti.com het volgende
geschreven:
On Wed, Sep 26, 2012 at 03:03:27PM +0200, Linus Walleij wrote:
On Wed, Sep 26, 2012 at 2:56 PM, Matt Porter mpor...@ti.com wrote:
Adding Linus W.
Op 26 sep. 2012, om 20:52 heeft Tony Lindgren t...@atomide.com het volgende
geschreven:
* Koen Kooi k...@dominion.thruhere.net [120926 10:23]:
Op 26 sep. 2012, om 18:15 heeft Matt Porter mpor...@ti.com het volgende
geschreven:
On Wed, Sep 26, 2012 at 03:03:27PM +0200, Linus Walleij
* Tomi Valkeinen tomi.valkei...@ti.com [120926 00:06]:
On Tue, 2012-09-25 at 12:07 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [120925 10:06]:
On Tue, 2012-09-25 at 08:38 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [120925 03:22]:
Hi
* Linus Walleij linus.wall...@linaro.org [120926 06:28]:
On Wed, Sep 26, 2012 at 2:56 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
[Me]
You can very well do clocks and regulators in these functions as well.
That's not really what I mean. The regulators in question are OMAP
version
* Koen Kooi k...@dominion.thruhere.net [120926 11:54]:
It's for am335x :)
Ah OK we don't have that data in the kernel then. But
if you have some format in mind suitable I can still
generate the other omap+package+mode data for you.
Regards,
Tony
--
To unsubscribe from this list: send the
On 09/26/2012 05:01 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/destroy a PHY and API's for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
using phandle, the
On Mon, Sep 17, 2012 at 12:53:18PM +0530, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current implementation some pdata is missing in lis3lv02d_i2c driver.
Also adds platform data for
On Tue, Sep 25, 2012 at 01:52:03PM +0530, Poddar, Sourav wrote:
Hi Greg,
Ping on this?
It was a RFT patch, with a huge thread. What's the resolution here?
Did people figure out the real problem here or not? If so, care to
resend the proper patch so I know what to apply?
thanks,
greg k-h
On Wed, 26 Sep 2012 13:24:00 -0700
Greg KH gre...@linuxfoundation.org wrote:
On Mon, Sep 17, 2012 at 12:53:18PM +0530, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current
On Wed, Sep 26, 2012 at 01:34:50PM -0700, Andrew Morton wrote:
On Wed, 26 Sep 2012 13:24:00 -0700
Greg KH gre...@linuxfoundation.org wrote:
On Mon, Sep 17, 2012 at 12:53:18PM +0530, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved
On Wed, 26 Sep 2012 13:44:03 -0700
Greg KH gre...@linuxfoundation.org wrote:
On Wed, Sep 26, 2012 at 01:34:50PM -0700, Andrew Morton wrote:
On Wed, 26 Sep 2012 13:24:00 -0700
Greg KH gre...@linuxfoundation.org wrote:
On Mon, Sep 17, 2012 at 12:53:18PM +0530, AnilKumar Ch wrote:
On Wed, Sep 26, 2012 at 01:54:12PM -0700, Andrew Morton wrote:
On Wed, 26 Sep 2012 13:44:03 -0700
Greg KH gre...@linuxfoundation.org wrote:
On Wed, Sep 26, 2012 at 01:34:50PM -0700, Andrew Morton wrote:
On Wed, 26 Sep 2012 13:24:00 -0700
Greg KH gre...@linuxfoundation.org wrote:
On Wed, Sep 26, 2012 at 09:44:29AM -0400, Matt Porter wrote:
Add ifdefery hacks to only use SRAM on Davinci. This
needs to be cleaned up with a sane generic SRAM allocator
(like the DT based driver available that can't be used on
Davinci which is just starting DT conversion) before it
can go
Hi Jean,
On Wed, 12 Sep 2012, Jean Pihet wrote:
Here is a re-spin after some comments and suggestions after review and
discussions.
Thanks Jean, I'll take it from here, probably with some changes which I
will respond to the individual patches, probably for 3.8.
- Paul
--
To unsubscribe
Hi Paul and Laurent,
This is an update to an old patchset for CSI-2 configuration for OMAP 3430
and 3630, and the corresponding patch to the ISP driver. Both have been
tested on the 3630 only so far.
Additional patches for the N9(50) camera support that mostly aren't yet
upstreamable, are
The OMAP 3630 has configuration how the ISP CSI-2 PHY pins are connected to
the actual CSI-2 receivers outside the ISP itself. Allow changing this
configuration from the ISP driver.
Signed-off-by: Sakari Ailus sakari.ai...@iki.fi
---
arch/arm/mach-omap2/control.c | 86
Configure CSI-2 phy based on platform data in the ISP driver. For that, the
new V4L2_CID_IMAGE_SOURCE_PIXEL_RATE control is used. Previously the same
was configured from the board code.
This patch is dependent on omap3: Provide means for changing CSI2 PHY
configuration.
Signed-off-by: Sakari
Moi Sakari
* Sakari Ailus sakari.ai...@iki.fi [120926 14:51]:
Configure CSI-2 phy based on platform data in the ISP driver. For that, the
new V4L2_CID_IMAGE_SOURCE_PIXEL_RATE control is used. Previously the same
was configured from the board code.
This patch is dependent on omap3: Provide
Hi Benoit,
On 12 September 2012 19:08, Omar Ramirez Luna omar.l...@linaro.org wrote:
To allow mailbox driver to function with device tree.
Tested in OMAP4 and OMAP3. OMAP2 untested.
Patch: arm/dts: OMAP2+: Add mailbox nodes, was Acked by Benoit
however it seems it wasn't picked up, so
Hi Omar,
On 9/26/2012 3:21 PM, Omar Ramirez Luna wrote:
Hi Benoit,
On 12 September 2012 19:08, Omar Ramirez Luna omar.l...@linaro.org wrote:
To allow mailbox driver to function with device tree.
Tested in OMAP4 and OMAP3. OMAP2 untested.
Patch: arm/dts: OMAP2+: Add mailbox nodes, was Acked
On Wed, Sep 26, 2012 at 09:44:29AM -0400, Matt Porter wrote:
Add ifdefery hacks to only use SRAM on Davinci. This
needs to be cleaned up with a sane generic SRAM allocator
(like the DT based driver available that can't be used on
Davinci which is just starting DT conversion) before it
can go
Hi Afzal,
On 09/19/2012 08:23 AM, Afzal Mohammed wrote:
Presently there are three peripherals that gets it timing
by runtime calculation. Those peripherals can work with
frequency scaling that affects gpmc clock. But timing
calculation for them are in different ways.
Here a generic runtime
Hi,
On Wed, Sep 26, 2012 at 11:57 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Sep 26, 2012 at 11:10:48AM +0530, ABRAHAM, KISHON VIJAY wrote:
Hi,
On Wed, Sep 19, 2012 at 5:26 PM, Felipe Balbi ba...@ti.com wrote:
On Wed, Sep 19, 2012 at 05:00:29PM +0530, Kishon Vijay Abraham I wrote:
On Thu, Sep 27, 2012 at 10:43:06AM +0530, ABRAHAM, KISHON VIJAY wrote:
Hi,
On Wed, Sep 26, 2012 at 11:57 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Sep 26, 2012 at 11:10:48AM +0530, ABRAHAM, KISHON VIJAY wrote:
Hi,
On Wed, Sep 19, 2012 at 5:26 PM, Felipe Balbi ba...@ti.com
usb: musb: dsps: remove explicit NOP device creation
removed nop register, but not unregistering, remove nop
unregister in error and exit path.
Signed-off-by: Afzal Mohammed af...@ti.com
---
drivers/usb/musb/musb_dsps.c | 2 --
1 file changed, 2 deletions(-)
diff --git
DT bindings have '-' (hyphens) instead of '_' (underscore),
update the documentation to reflect it.
Signed-off-by: Afzal Mohammed af...@ti.com
---
Documentation/devicetree/bindings/usb/am33xx-usb.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
From: B, Ravi ravib...@ti.com
Added device tree support for nop transceiver driver and updated the
Documentation with device tree binding information for am33xx platform.
Signed-off-by: Ravi Babu ravib...@ti.com
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Afzal Mohammed
From: Wei Yongjun yongjun_...@trendmicro.com.cn
In case of error, the function voltdm_lookup() returns NULL
not ERR_PTR(). The IS_ERR() test in the return value check
should be replaced with NULL test.
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
From: Wei Yongjun yongjun_...@trendmicro.com.cn
In case of error, the function voltdm_lookup() returns NULL
not ERR_PTR(). The IS_ERR() test in the return value check
should be replaced with NULL test.
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
70 matches
Mail list logo
