On Mon, Mar 19, 2012 at 5:16 PM, Archit Taneja a0393...@ti.com wrote:
On Monday 19 March 2012 02:15 PM, Hiremath, Vaibhav wrote:
On Fri, Mar 16, 2012 at 16:41:27, Taneja, Archit wrote:
Hi,
On Friday 16 March 2012 03:46 PM, Archit Taneja wrote:
On Monday 12 March 2012 03:34 PM, Hiremath,
On Wed, 2012-06-27 at 22:09 +0200, Peter Meerwald wrote:
Signed-off-by: Peter Meerwald pme...@pmeerw.net
---
drivers/video/omap2/dss/Kconfig |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Thanks, applied to omapdss tree.
Tomi
signature.asc
Description: This is a digitally
On Thu, 19 Apr 2012, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
The am35x family of SoCs do not have an IVA so
a parallel set of clockdomain dependencies are
required that are simililar to OMAP3 but without
any IVA dependencies.
Signed-off-by: Mark A. Greer
+ Shubro, Felipe,
On Thu, Jun 28, 2012 at 12:57 AM, Paul Walmsley p...@pwsan.com wrote:
On Wed, 27 Jun 2012, Paul Walmsley wrote:
Looks like something broke between v3.5-rc3 and v3.5-rc4 with dynamic
idle on 3530ES3 Beagle. 37xx EVM doesn't seem to be affected.
Taking a closer look now.
On Wed, Jun 27, 2012 at 7:54 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 27 Jun 2012, Keshava Munegowda wrote:
Its observed that in Beagle XM , during suspend/resume the OMAP
EHCI controller losing the register contents. this is causing the
hub disconnect after the resume, this is
Hello Konstantin,
On Thu, Jun 28, 2012 at 7:43 AM, Eduardo Valentin
eduardo.valen...@ti.com wrote:
Hello,
On Wed, Jun 27, 2012 at 10:04:32PM +0400, Konstantin Baydarov wrote:
Hello.
This is a next version of series of patches(based on Eduardo Valentin's
patch set) adding a basic support
Hi,
* Konstantin Baydarov kbaida...@dev.rtsoft.ru [120627 11:09]:
OMAP system control module can be probed early, then
omap_type is safe to use its APIs.
TODO: add support for other omap versions
Signed-off-by: Konstantin Baydarov kbaida...@dev.rtsoft.ru
---
arch/arm/mach-omap2/id.c |
Hi,
* Javier Martinez Canillas martinez.jav...@gmail.com [120627 15:32]:
On Sun, Jun 24, 2012 at 12:18 AM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
On OMAP boards that includes an SD card slot, an EXT4 partition could
be used to store the root file system. So, the kernel should
On Wed, 2012-06-27 at 20:23 +0530, Jassi Brar wrote:
On 27 June 2012 13:43, Tomi Valkeinen tomi.valkei...@ti.com wrote:
I don't like it at all that omapdss disables and enables the panels in
omapdss's suspend/resume hooks. But I'm not sure how this should work...
Should panel drivers each
Err,
There was a patch been sent in response that did exactly as you asked.
http://lkml.indiana.edu/hypermail/linux/kernel/1205.3/00433.html
Regards
-- Pantelis
On Jun 24, 2012, at 11:59 AM, Russell King - ARM Linux wrote:
See this thread:
The following changes since commit 6b16351acbd415e66ba16bf7d473ece1574cf0bc:
Linux 3.5-rc4 (2012-06-24 12:53:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-fixes-for-v3.5-rc4
for you to fetch changes up to
On 28 June 2012 12:11, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Wed, 2012-06-27 at 20:23 +0530, Jassi Brar wrote:
On 27 June 2012 13:43, Tomi Valkeinen tomi.valkei...@ti.com wrote:
I don't like it at all that omapdss disables and enables the panels in
omapdss's suspend/resume hooks.
On Wed, 2012-06-27 at 19:35 +0530, jaswinder.si...@linaro.org wrote:
From: Jassi Brar jaswinder.si...@linaro.org
We can easily keep track of latest EDID from the display and hence avoid
expensive EDID re-reads over I2C.
This could also help some cheapo displays that provide EDID reliably
On Thu, 2012-06-28 at 13:16 +0530, Jassi Brar wrote:
On 28 June 2012 12:11, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Wed, 2012-06-27 at 20:23 +0530, Jassi Brar wrote:
On 27 June 2012 13:43, Tomi Valkeinen tomi.valkei...@ti.com wrote:
I don't like it at all that omapdss disables
Got the l-o list address wrong, sigh...
- Paul
-- Forwarded message --
Date: Thu, 28 Jun 2012 02:19:47 -0600 (MDT)
From: Paul Walmsley p...@pwsan.com
To: t...@atomide.com
Cc: linux-o...@vger.kernel.com, linux-arm-ker...@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP AM35xx:
Hi,
On 4430ES2 Panda, the serial port prints garbage at the end of long
transmissions from the board when dynamic idle is enabled. Here's an
example (search for Minicom2.6.1):
http://www.pwsan.com/omap/testlogs/am35xx_devel_3.6/20120628014213/pm/4430es2panda_log.txt
My recollection is that
Hi Tero,
there are some new compiler warnings added in the v3.5-rc kernels:
arch/arm/mach-omap2/twl-common.c:51:12: warning: 'twl_set_voltage' defined but
not used
arch/arm/mach-omap2/twl-common.c:57:12: warning: 'twl_get_voltage' defined but
not used
They only seem to appear on my N800
On Thu, 2012-06-28 at 02:47 -0600, Paul Walmsley wrote:
Hi Tero,
there are some new compiler warnings added in the v3.5-rc kernels:
arch/arm/mach-omap2/twl-common.c:51:12: warning: 'twl_set_voltage' defined
but not used
arch/arm/mach-omap2/twl-common.c:57:12: warning: 'twl_get_voltage'
From a5dc6e2ebee40b4f6cf51c1ec3c67476ffb8efc3 Mon Sep 17 00:00:00 2001
From: Ramesh Gupta G grgu...@ti.com
Date: Thu, 28 Jun 2012 11:53:54 +0530
Subject: [PATCH v3 0/2] OMAP:IOMMU:flush L1 and L2 caches
This patch series is the next version to
- add a new cache maintenance api to support
Hi Tony,
On Wed, Jun 27, 2012 at 20:28:45, Tony Lindgren wrote:
The last patch in this series causes onenand not to show
up on my n900. I believe the problem has been there earlier
too, but I just did not notice it.
Sorry for the delayed response, could reach workplace a short
while ago only
From 95b900d845537ab755bfcef50e956ee03e89a2c5 Mon Sep 17 00:00:00 2001
From: Ramesh Gupta G grgu...@ti.com
Date: Wed, 27 Jun 2012 16:50:32 +0530
Subject: [PATCH v3 1/2] ARM: new cache maintenance api for iommu
Non-coherent IOMMU drivers need to make sure
that the data held in the caches is
From ad8097177ca6c43d98d0641ea881936fe328b4dc Mon Sep 17 00:00:00 2001
From: Ramesh Gupta G grgu...@ti.com
Date: Fri, 15 Jun 2012 16:46:46 +0530
Subject: [PATCH v3 2/2] OMAP:IOMMU:flush L1 and L2 caches
OMAP IOMMU need to make sure that data in the L1 and L2
caches is visible to the MMU hardware
Hi.
On 06/28/2012 08:50 AM, Eduardo Valentin wrote:
Hello,
On Wed, Jun 27, 2012 at 10:04:54PM +0400, Konstantin Baydarov wrote:
This patch introduces a MFD core device driver for OMAP system control
module.
The control module allows software control of various static modes supported
Hi everyone!
This following patch series enables LCD3 support which consists of two patches.
The 1st patch
* adds enum mgr_reg_fields to describe various register fields manipulated for
LCD support
* replaces if-else checks for LCD implementation with simpler interface with
the help of
The current implementation of LCD channels and managers consists of a number of
if-else construct which has been replaced by a simpler interface. A constant
structure mgr_desc has been created in Display Controller (DISPC) module. The
mgr_desc contains for each channel its name, irqs and is
OMAP5 Display Subsystem (DSS) architecture comes with a additional LCD3 channel
with its own dedicated overlay manager. The current patch adds LCD3 channel and
basic register support for LCD3 channel. It adds register addresses for various
Display Controller (DISPC) registers like
The support feature for LCD3 manager has been added into the DSS features
structure. LCD3 panel has registers as DISPC_CONTROL3 and DISPC_CONFIG3 just
like those in LCD and LCD2 panels. These registers control the Display
Controller (DISPC) module for LCD3 output. The three LCDs support Display
DISPC functions have been modified to provide clock and register dumps and debug
support for the LCD3 manager.
Signed-off-by: Chandrabhanu Mahapatra cmahapa...@ti.com
---
drivers/video/omap2/dss/dispc.c | 70 ++
1 files changed, 40 insertions(+), 30
The dispc_disable_outputs() function currently disables all LCD managers except
LCD3. This patch adds disabling functionality for LCD3 manager thereby
maintaining consistency of Display Subsystem for in case Display Controller is
reset when LCD3 manager is in use.
Signed-off-by: Chandrabhanu
On Thu, Jun 28, 2012 at 2:35 PM, Tero Kristo t-kri...@ti.com wrote:
On Thu, 2012-06-28 at 02:47 -0600, Paul Walmsley wrote:
Hi Tero,
there are some new compiler warnings added in the v3.5-rc kernels:
arch/arm/mach-omap2/twl-common.c:51:12: warning: 'twl_set_voltage' defined
but not used
On 28 June 2012 13:18, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Wed, 2012-06-27 at 19:35 +0530, jaswinder.si...@linaro.org wrote:
From: Jassi Brar jaswinder.si...@linaro.org
We can easily keep track of latest EDID from the display and hence avoid
expensive EDID re-reads over I2C.
This
Hello,
On Thu, Jun 28, 2012 at 12:37 PM, Konstantin Baydarov
kbaida...@dev.rtsoft.ru wrote:
Hi.
On 06/28/2012 08:50 AM, Eduardo Valentin wrote:
Hello,
On Wed, Jun 27, 2012 at 10:04:54PM +0400, Konstantin Baydarov wrote:
This patch introduces a MFD core device driver for OMAP system
Hi,
Gentle remainder to this patch series.
On Fri, Jun 22, 2012 at 15:10:46, AnilKumar, Chimata wrote:
This patch series add device tree support for AM33XX SoC family.
Initialy Hiremath Vaibhav submitted a patch for AM33XX devices
based on omap3 family. Details at
Hello.
On 06/28/2012 01:49 PM, Valentin, Eduardo wrote:
Hello,
On Thu, Jun 28, 2012 at 12:37 PM, Konstantin Baydarov
kbaida...@dev.rtsoft.ru wrote:
Hi.
On 06/28/2012 08:50 AM, Eduardo Valentin wrote:
Hello,
On Wed, Jun 27, 2012 at 10:04:54PM +0400, Konstantin Baydarov wrote:
This
On Thu, 2012-06-28 at 15:18 +0530, Jassi Brar wrote:
On 28 June 2012 13:18, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Wed, 2012-06-27 at 19:35 +0530, jaswinder.si...@linaro.org wrote:
From: Jassi Brar jaswinder.si...@linaro.org
We can easily keep track of latest EDID from the display
On 06/28/2012 02:12 PM, Konstantin Baydarov wrote:
The interface(design) of omap-control-core.c has already been discussed many
times :(
Eduardo, in his patch set, suggested following design:
- omap-control-core.c ioremaps SCM window and provide functions to read/write
SCP register for
On 28 June 2012 15:44, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2012-06-28 at 15:18 +0530, Jassi Brar wrote:
--- a/drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c
+++ b/drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c
@@ -243,10 +243,13 @@ static int hdmi_check_hpd_state(struct hdmi_ip_data
OMAP2 does not use the external voltage controller code for TWL, and
thus OMAP2 only compilation generates following warnings:
arch/arm/mach-omap2/twl-common.c:51: warning: 'twl_set_voltage' defined but not
used
arch/arm/mach-omap2/twl-common.c:57: warning: 'twl_get_voltage' defined but not
On Thu, 2012-06-28 at 15:10 +0530, Chandrabhanu Mahapatra wrote:
The current implementation of LCD channels and managers consists of a number
of
if-else construct which has been replaced by a simpler interface. A constant
structure mgr_desc has been created in Display Controller (DISPC)
Hello,
On Thu, Jun 28, 2012 at 1:26 PM, Konstantin Baydarov
kbaida...@dev.rtsoft.ru wrote:
On 06/28/2012 02:12 PM, Konstantin Baydarov wrote:
The interface(design) of omap-control-core.c has already been discussed many
times :(
Eduardo, in his patch set, suggested following design:
-
Hello again,
On Thu, Jun 28, 2012 at 1:51 PM, Valentin, Eduardo
eduardo.valen...@ti.com wrote:
Hello,
On Thu, Jun 28, 2012 at 1:26 PM, Konstantin Baydarov
kbaida...@dev.rtsoft.ru wrote:
On 06/28/2012 02:12 PM, Konstantin Baydarov wrote:
The interface(design) of omap-control-core.c has
On 28 June 2012 16:17, Jassi Brar jaswinder.si...@linaro.org wrote:
On 28 June 2012 15:44, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2012-06-28 at 15:18 +0530, Jassi Brar wrote:
--- a/drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c
+++ b/drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c
@@
On Thu, Jun 28, 2012 at 10:06:23AM +0300, Pantelis Antoniou wrote:
Err,
There was a patch been sent in response that did exactly as you asked.
http://lkml.indiana.edu/hypermail/linux/kernel/1205.3/00433.html
Regards
Obviously it was missed, and no one bothered to re-send it. Yes, it
On Thu, 2012-06-28 at 16:17 +0530, Jassi Brar wrote:
On 28 June 2012 15:44, Tomi Valkeinen tomi.valkei...@ti.com wrote:
When the display device is disabled, we're not listening to the hpd
interrupt anymore. So when it's disabled, the cable can be replugged and
the monitor changed, and the
On Thu, 2012-06-28 at 16:28 +0530, Jassi Brar wrote:
On 28 June 2012 16:17, Jassi Brar jaswinder.si...@linaro.org wrote:
On 28 June 2012 15:44, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2012-06-28 at 15:18 +0530, Jassi Brar wrote:
--- a/drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c
On Thursday 28 June 2012 04:20 PM, Tomi Valkeinen wrote:
On Thu, 2012-06-28 at 15:10 +0530, Chandrabhanu Mahapatra wrote:
The current implementation of LCD channels and managers consists of a number
of
if-else construct which has been replaced by a simpler interface. A constant
structure
On Thu, 2012-06-28 at 16:49 +0530, Chandrabhanu Mahapatra wrote:
On Thursday 28 June 2012 04:20 PM, Tomi Valkeinen wrote:
On Thu, 2012-06-28 at 15:10 +0530, Chandrabhanu Mahapatra wrote:
+ [OMAP_DSS_CHANNEL_DIGIT] = {
+ .name = DIGIT,
+ .vsync_irq =
On Thu, 2012-06-28 at 14:10 +0300, Tomi Valkeinen wrote:
On Thu, 2012-06-28 at 16:28 +0530, Jassi Brar wrote:
Sorry a correction. Reading detect() won't work. I suggest we keep HPD
IRQ enabled for the lifetime of the driver.
Ok, I see. But that's not acceptable. It would require us to
This patch series adds device tree support for MUSB and device
tree support for all the related modules to get MUSB working in
OMAP platform.
A new omap-usb2 phy driver has been added (with only dt suppport)
to perform phy configurations. Previously this configuration was
performed by twl6030,
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree support for usb2 phy driver and
the documentation with device tree binding information is
Add omap-usb2 data node in omap4 device tree file.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index bda5df3..4d2dcc1
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes
Add twl4030-usb data node in twl4030 device tree file.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/twl4030.dtsi | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/twl4030.dtsi
Add twl6030-usb data node in twl6030 device tree file
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/twl6030.dtsi |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/twl6030.dtsi b/arch/arm/boot/dts/twl6030.dtsi
index
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-board.dts file.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3-evm.dts|6 ++
All the unnessary functions in omap-phy-internal is removed.
These functionality are now handled by omap-usb2 phy driver.
Cc: Felipe Balbi ba...@ti.com
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/omap_phy_internal.c | 138
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 34 -
drivers/usb/musb/omap2430.c|
Add device tree support for twl6030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
.../devicetree/bindings/usb/twl-usb.txt| 18
drivers/usb/otg/twl6030-usb.c | 45
Add device tree support for twl6030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
.../devicetree/bindings/usb/twl-usb.txt| 19 +
drivers/usb/otg/twl4030-usb.c |
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
ID detection.
Writing to control module which is now handled in omap2430.c should be
Ping..
Thanks,
Sricharan
On Thu, Jun 14, 2012 at 5:26 PM, R, Sricharan r.sricha...@ti.com wrote:
Hi Paul,
Some prm and cm registers read/write and status functions
are built only for some custom OMAP2+ builds and are stubbed
in header files for other builds under ifdef statements.
But
On 06/28/12 19:10, the mail apparently from Tomi Valkeinen included:
On Thu, 2012-06-28 at 16:28 +0530, Jassi Brar wrote:
On 28 June 2012 16:17, Jassi Brar jaswinder.si...@linaro.org wrote:
On 28 June 2012 15:44, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2012-06-28 at 15:18 +0530,
Hi,
* Paul Walmsley p...@pwsan.com [120628 01:25]:
The following changes since commit 6b16351acbd415e66ba16bf7d473ece1574cf0bc:
Linux 3.5-rc4 (2012-06-24 12:53:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
On 06/28/12 19:38, the mail apparently from Tomi Valkeinen included:
On Thu, 2012-06-28 at 14:10 +0300, Tomi Valkeinen wrote:
On Thu, 2012-06-28 at 16:28 +0530, Jassi Brar wrote:
Sorry a correction. Reading detect() won't work. I suggest we keep HPD
IRQ enabled for the lifetime of the
On 28 June 2012 16:40, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2012-06-28 at 16:28 +0530, Jassi Brar wrote:
Sorry a correction. Reading detect() won't work. I suggest we keep HPD
IRQ enabled for the lifetime of the driver.
Ok, I see. But that's not acceptable. It would require
* Mohammed, Afzal af...@ti.com [120628 02:36]:
Hi Tony,
On Wed, Jun 27, 2012 at 20:28:45, Tony Lindgren wrote:
The last patch in this series causes onenand not to show
up on my n900. I believe the problem has been there earlier
too, but I just did not notice it.
Sorry for the
Hi Tony,
On Thu, Jun 28, 2012 at 18:02:07, Tony Lindgren wrote:
* Mohammed, Afzal af...@ti.com [120628 02:36]:
Yes that seems to do the trick, thanks! I can fold that into the
breaking patch when applying.
Relieved, thanks
Regards
Afzal
--
To unsubscribe from this list: send the line
Hi Tony,
On Thu, Jun 28, 2012 at 18:02:07, Tony Lindgren wrote:
* Mohammed, Afzal af...@ti.com [120628 02:36]:
diff --git a/arch/arm/mach-omap2/gpmc-onenand.c
b/arch/arm/mach-omap2/gpmc-onenand.c
index c8a9487..bbae674 100644
--- a/arch/arm/mach-omap2/gpmc-onenand.c
+++
On 28 June 2012 17:33, Andy Green andy.gr...@linaro.org wrote:
On 06/28/12 19:10, the mail apparently from Tomi Valkeinen included:
On Thu, 2012-06-28 at 16:28 +0530, Jassi Brar wrote:
On 28 June 2012 16:17, Jassi Brar jaswinder.si...@linaro.org wrote:
On 28 June 2012 15:44, Tomi Valkeinen
On Thu, 2012-06-28 at 18:43 +0530, Jassi Brar wrote:
On 28 June 2012 17:33, Andy Green andy.gr...@linaro.org wrote:
If Jassi's alright with it we might have a go at implementing this, but can
you define a bit more about how we logically tell DSS that we want to, eg,
disable HDMI totally?
On Thu, 2012-06-28 at 16:28 +0530, Jassi Brar wrote:
I think among the first things, while enabling HDMI, should be to see
if there is really some display connected on the port i.e, HPD
asserted. Only if ti_hdmi_4_detect() returned true, should we
proceed otherwise wait for HPQ irq.
Hello again,
On Thu, Jun 28, 2012 at 9:29 AM, Valentin, Eduardo
eduardo.valen...@ti.com wrote:
Hello Konstantin,
On Thu, Jun 28, 2012 at 7:43 AM, Eduardo Valentin
eduardo.valen...@ti.com wrote:
Hello,
On Wed, Jun 27, 2012 at 10:04:32PM +0400, Konstantin Baydarov wrote:
Hello.
This is a
Kevin Hilman khil...@ti.com writes:
Tasslehoff Kjappfot tasskj...@gmail.com writes:
The support for using a timer to wake from suspend was removed in:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=98e182a26bbbf5575457622337684ef61493e864
I found an
On Thursday 24 March 2011, Andy Green wrote:
The following series solves a problem Panda suffers from where
because there is no local MAC address storage on the board, a
new random MAC address is applied to the onboard Ethernet
interface each time, and the wl12xx module's wlan0 interface is
Hi Tony,
Looks like we have an issue with the merge from branch
omap-cleanup-for-v3.5,
Patch (ARM: OMAP2+: am33xx: Make am33xx as a separate class) changes
AM335X_CLASS to value 0x33500033 and then later merge commit (Merge tag
'omap-cleanup-for-v3.5' into tmp-merge) reverts it back to
The LCD interface drivers(DPI, DSI, RFBI, SDI) do some direct DISPC register
writes to configure LCD manager related fields. This series groups these fields
into a single struct, and let's the interface driver apply these parameters.
This allows us to:
- Check the LCD manager related parameters
dipsc_mgr_set_clock div has an int return type to report errors or success.
The function doesn't really check for errors and always returns 0. Change
the return type to void.
Checking for the correct DISPC clock divider ranges will be done when a DSS2
user does a manager apply. This support will
dipsc_mgr_set_clock div has an int return type to report errors or success.
The function doesn't really check for errors and always returns 0. Change
the return type to void.
Checking for the correct DISPC clock divider ranges will be done when a DSS2
user does a manager apply. This support will
Create a struct dss_lcd_mgr_config which holds LCD overlay manager related
parameters. These are currently partially contained in the omap_dss_device
connected to the manager, and the rest are in the interface driver.
The parameters are directly written to the DISPC registers in the interface
Create a dss_lcd_mgr_config struct instance in DPI. Fill up all the parameters
of the struct with configurations held by the panel, and the configurations
required by DPI.
Use these to write to the DISPC registers. These direct register writes would be
later replaced by a function which applies
Create a dss_lcd_mgr_config struct instance in RFBI. Fill up all the parameters
of the struct with configurations held by the panel, and the configurations
required by RFBI.
Use these to write to the DISPC registers. These direct register writes would be
later replaced by a function which applies
Create a dss_lcd_mgr_config struct instance in DSI. Fill up all the parameters
of the struct with configurations held by the panel, and the configurations
required by DSI.
Use these to write to the DISPC registers. These direct register writes would be
later replaced by a function which applies
Create a dss_lcd_mgr_config struct instance in SDI. Fill up all the parameters
of the struct with configurations held by the panel, and the configurations
required by SDI.
Use these to write to the DISPC registers. These direct register writes would be
later replaced by a function which applies
Replace the DISPC fuctions used to configure LCD channel related manager
parameters with dss_mgr_set_lcd_config() in APPLY. This function ensures that
the DISPC registers are written at the right time by using the shadow register
programming model.
The LCD manager configurations is stored as a
The LCD related manager configurations are a part of the manager's private data
in APPLY. Pass this to dss_lcd_mgr_config to dss_mgr_check and create a function
to check the validity of some of the configurations.
To check some of the configurations, we require information of interface to
which
APPLY needs to know at certain places whether an overlay manager is in manual
or auto update mode. The caps of the connected omap_dss_device were used to
check that.
A LCD manager is in manual update if stallmode is enabled for that manager. TV
managers for now always auto update.
Return the
dss_mgr_is_lcd() available in dss.h does the same thing as dispc_mgr_is_lcd()
in dispc.c. Remove the function from dispc.c and replace it with the one in
dss.h.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/dispc.c | 27 +--
1 file changed, 9
The RFBI driver uses a direct DISPC register write to enable the overlay
manager. Replace this with dss_mgr_enable() which checks if the connected
overlay and managers are correctly configured, and configure DSS for
fifomerge.
Signed-off-by: Archit Taneja arc...@ti.com
---
Replication logic for an overlay depends on the color mode in which it is
configured and the video port width of the manager it is connected to.
video port width now held in dss_lcd_mgr_config in the manager's private
data in APPLY. Use this instead of referring to the omap_dss_device connected
On Sat, Apr 28, 2012 at 07:04:38, Paul Walmsley wrote:
On Fri, 17 Feb 2012, Vaibhav Hiremath wrote:
In case of AM33xx family of devices (like cpsw) have different sysc
bit field offsets defined,
sysc_type3:
| 3 2 | 10 |
| STDBYMODE | IDLEMODE |
So introduce new
On Thu, 2012-06-28 at 14:18 +, Arnd Bergmann wrote:
It's been a while since we discussed these patches, but Steven Rostedt
just tripped over the same problem and the patches work for
him, so he says Tested-by: Steven Rostedt rost...@goodmis.org.
Can we get the patches into linux-3.6
On 6/28/2012 8:10 PM, Hiremath, Vaibhav wrote:
On Sat, Apr 28, 2012 at 07:04:38, Paul Walmsley wrote:
On Fri, 17 Feb 2012, Vaibhav Hiremath wrote:
In case of AM33xx family of devices (like cpsw) have different sysc
bit field offsets defined,
sysc_type3:
| 3 2 | 10 |
|
In current implementation, some places we are still using
ARCH_OMAPx config option, making it difficult to add new devices;
for example, while adding am33xx device support I came across multiple
instances where I had to patch the existing code to make it work for
am33xx.
This patch tries to
In order to remove unnecessary idefs, move noncore and core
dpll ops to dpll3xxx.c file (where it should have been already).
The clkops (clkops_omap3_core_dpll_ops clkops_omap3_noncore_dpll_ops)
is used in clock data files, and dependency is already handled by
Makefile rule.
Signed-off-by:
The function __omap2_set_globals() can be common across all
platforms/architectures, even in case of omap4, internally it
calls same set of functions as in __omap2_set_globals() function
(except for sdrc).
This patch adds new config flag SOC_HAS_OMAP2_SDRC to handle sdrc,
so that we can reuse same
All OMAP2PLUS based devices, builds omap-device.o target;
so just add one entry so that there is no need to patch this file
for any future OMAP2+ devices.
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Kevin Hilman khil...@ti.com
Cc: Paul Walmsley
Hi Vaibhav,
One small comment.
On 06/28/2012 04:59 PM, Vaibhav Hiremath wrote:
The function __omap2_set_globals() can be common across all
platforms/architectures, even in case of omap4, internally it
calls same set of functions as in __omap2_set_globals() function
(except for sdrc).
This
On 27.06.2012 14:13, Hiremath, Vaibhav wrote:
Just to clarify from AM335x perspective,
In case of AM335x, since the patches and complete BasePort support is still
not present in the Mainline (neither in Linus's tree not in linux-omap), you
need to use my Repo (https://github.com/hvaibhav:
From: Vikram Pandita vikram.pand...@ti.com
In case a peripheral is driving SDA bus low (ie. a start condition), provide
a constant clock output using the test mode of the OMAP I2C controller to
try and clear the bus. Soft reset I2C controller after attempting the bus clear
to ensure that
This is a minimal cleanup series.
The patch series does the following
- Bus busy recovery mechanism.
- Make the i2c use SET_RUNTIME_PM_OPS
- Use INIT_COMPLETION instead of init_completion
- the reset patch is dropped will try to rework it as per the
review comments recieved.
This applies on
1 - 100 of 163 matches
Mail list logo
