On Wed, Sep 28, 2011 at 8:19 PM, Archit Taneja arc...@ti.com wrote:
Currently, there is a lot of redundant code is between DPI and VENC panels,
this
can be made common by moving out field/interlace specific code to a separate
function called omapvid_handle_interlace_display(). There is no
Fix,
arch/arm/mach-omap2/timer.c: In function 'omap_timer_init':
arch/arm/mach-omap2/timer.c:482: warning: assignment from incompatible pointer
type
Signed-off-by: Afzal Mohammed af...@ti.com
---
Fix on tony/master
arch/arm/mach-omap2/timer.c |6 +++---
1 files changed, 3 insertions(+),
On Tue, Sep 20, 2011 at 04:50:29PM +0800, Axel Lin wrote:
Current code calls omap4430_phy_init() twice in usb_musb_init().
Calling omap4430_phy_init() once is enough.
This patch removes the first omap4430_phy_init() call, which using an
uninitialized pointer as parameter.
This patch
On Thu, Sep 29, 2011 at 10:00:58AM +0800, Bryan Wu wrote:
Hiya,
Any comments and need I do anything to improve this patch?
No idea, I don't remember the original errors which this stuff spat out
and how they were caused.
The only thing I care about is that the conversion of the existing ARM
On Wed, Sep 21, 2011 at 5:41 PM, Govindraj.R govindraj.r...@ti.com wrote:
Converting uart driver to adapt to pm runtime API's.
Code re-org + cleanup.
Moving some functionality from serial.c to omap-serial.c
Changes involves:
1.) Cleaning up certain uart calls from sram_idle
We have a board similar to the beagleboard C3, but we have forced musb
to host-mode and added an smsc95xx and an RJ45 connector instead. In
2.6.39 I configured the musb driver to operate in host-mode, and that
was all that was needed to make it work.
In 3.1.0rc4 that option has been removed
-Original Message-
From: Taneja, Archit
Sent: Wednesday, September 28, 2011 8:19 PM
To: Hiremath, Vaibhav
Cc: Valkeinen, Tomi; linux-omap@vger.kernel.org; Semwal, Sumit; linux-
me...@vger.kernel.org; Taneja, Archit
Subject: [PATCH v4 2/5] OMAP_VOUT: CLEANUP: Remove redundant code
-Original Message-
From: Taneja, Archit
Sent: Wednesday, September 28, 2011 8:19 PM
To: Hiremath, Vaibhav
Cc: Valkeinen, Tomi; linux-omap@vger.kernel.org; Semwal, Sumit; linux-
me...@vger.kernel.org; Taneja, Archit
Subject: [PATCH v4 3/5] OMAP_VOUT: Fix VSYNC IRQ handling in
-Original Message-
From: Taneja, Archit
Sent: Wednesday, September 28, 2011 8:19 PM
To: Hiremath, Vaibhav
Cc: Valkeinen, Tomi; linux-omap@vger.kernel.org; Semwal, Sumit; linux-
me...@vger.kernel.org; Taneja, Archit
Subject: [PATCH v4 4/5] OMAP_VOUT: Add support for DSI panels
Add
-Original Message-
From: Taneja, Archit
Sent: Wednesday, September 28, 2011 8:19 PM
To: Hiremath, Vaibhav
Cc: Valkeinen, Tomi; linux-omap@vger.kernel.org; Semwal, Sumit; linux-
me...@vger.kernel.org; Taneja, Archit
Subject: [PATCH v4 5/5] OMAP_VOUT: Increase MAX_DISPLAYS to a larger
On Fri, May 6, 2011 at 2:44 PM, Adrian Hunter adrian.hun...@nokia.com wrote:
Go through the driver's set_power() functions rather than
calling regulator_enable/disable() directly because otherwise
pbias configuration for MMC1 is not done.
Hi Chris,
Are you OK to queue this patch as bug fix.
The hwmod structure of usb_host_hs and usb_tll are
retrieved and registered with omap device
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
Reviewed-by: Partha Basak part...@india.ti.com
---
arch/arm/mach-omap2/usb-host.c | 100 ++--
1 files changed,
Following 2 hwmod structures are added
1. usb_host_hs
The hwmod of usbhs with uhh, ehci and ohci base addresses
functional clock and ehci, ohci irqs
2. usb_tll_hs
hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Keshava Munegowda
From: Benoit Cousson b-cous...@ti.com
Following 2 hwmod structures are added
1. usb_host_hs
The hwmod of usbhs with uhh, ehci and ohci base addresses
functional clock and ehci, ohci irqs
2. usb_tll_hs
hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Benoit
From: Keshava Munegowda keshava_mgo...@ti.com
device name usbhs clocks are changed from
usbhs-omap.0 to usbhs_omap; this is because
in the hwmod registration the device name is set
as usbhs_omap; The redudant clock nodes are removed.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
From: Keshava Munegowda keshava_mgo...@ti.com
The Hwmod structures and Runtime PM features are implemented
For EHCI and OHCI drivers of OMAP3 and OMAP4.
The global suspend/resume of EHCI and OHCI
is validated on OMAP3430 sdp board with these patches.
TODO:
- Adding mux-information to Hwmods.
From: Keshava Munegowda keshava_mgo...@ti.com
The usbhs core driver does not enable/disable the interface and
functional clocks directly, These clocks are handled by runtime pm,
hence instead of the clock enable/disable, the runtime pm APIS are
used. however,the optional clocks and port clocks
From: Keshava Munegowda keshava_mgo...@ti.com
device name usbhs clocks are changed from
usbhs-omap.0 to usbhs_omap; this is because
in the hwmod registration the device name is set
as usbhs_omap; The redudant clock nodes are removed.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
The hwmod structure of usb_host_hs and usb_tll are
retrieved and registered with omap device
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
Reviewed-by: Partha Basak part...@india.ti.com
---
arch/arm/mach-omap2/usb-host.c | 100 ++--
1 files changed,
From: Benoit Cousson b-cous...@ti.com
Following 2 hwmod structures are added
1. usb_host_hs
The hwmod of usbhs with uhh, ehci and ohci base addresses
functional clock and ehci, ohci irqs
2. usb_tll_hs
hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Benoit
From: Keshava Munegowda keshava_mgo...@ti.com
The Hwmod structures and Runtime PM features are implemented
For EHCI and OHCI drivers of OMAP3 and OMAP4.
The global suspend/resume of EHCI and OHCI
is validated on OMAP3430 sdp board with these patches.
TODO:
- Adding mux-information to Hwmods.
Following 2 hwmod structures are added
1. usb_host_hs
The hwmod of usbhs with uhh, ehci and ohci base addresses
functional clock and ehci, ohci irqs
2. usb_tll_hs
hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Keshava Munegowda
From: Keshava Munegowda keshava_mgo...@ti.com
The usbhs core driver does not enable/disable the interface and
functional clocks directly, These clocks are handled by runtime pm,
hence instead of the clock enable/disable, the runtime pm APIS are
used. however,the optional clocks and port clocks
From: Benoit Cousson b-cous...@ti.com
Following 2 hwmod structures are added
1. usb_host_hs
The hwmod of usbhs with uhh, ehci and ohci base addresses
functional clock and ehci, ohci irqs
2. usb_tll_hs
hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Benoit
Fix the typo, instead it should be SDMMC1
USBC1 is not related to MMC1 I/Os
Signed-off-by: Balaji T K balaj...@ti.com
---
arch/arm/mach-omap2/hsmmc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/hsmmc.c b/arch/arm/mach-omap2/hsmmc.c
index
MMC1 pbias and speed control fix for SDMMC1 extended I/O cell
Balaji T K (2):
arm: omap4: hsmmc: Fix Pbias configuration on regulator OFF
arm: omap4: hsmmc: configure SDMMC1_DR0 properly
arch/arm/mach-omap2/hsmmc.c | 16 +++-
1 files changed, 3 insertions(+), 13 deletions(-)
MMC1 data line IO's are powered down in before set regulator function.
IO's should not be powered ON when regulator is OFF.
Keep the IO's in power pown mode after regulator OFF.
Delete incorrect comments which are not applicable for OMAP4.
Signed-off-by: Balaji T K balaj...@ti.com
Signed-off-by:
From: Balaji T K balaj...@ti.com
Will resend this series as my email id is garbled.
MMC1 pbias and speed control fix for SDMMC1 extended I/O cell
Balaji T K (2):
arm: omap4: hsmmc: Fix Pbias configuration on regulator OFF
arm: omap4: hsmmc: configure SDMMC1_DR0 properly
* Balaji T K balaj...@ti.com [110929 07:11]:
MMC1 data line IO's are powered down in before set regulator function.
IO's should not be powered ON when regulator is OFF.
Keep the IO's in power pown mode after regulator OFF.
Delete incorrect comments which are not applicable for OMAP4.
Care to
Hi,
Few comments below.
* Deepthy Ravi deepthy.r...@ti.com [110927 06:07]:
+
+#include linux/io.h
+#include linux/i2c.h
+#include linux/delay.h
+#include linux/gpio.h
+#include linux/err.h
+#include linux/platform_device.h
+#include mach/gpio.h
You can leave out mach/gpio.h as you
* Tomi Valkeinen tomi.valkei...@ti.com [110925 23:04]:
On Tue, 2011-09-20 at 11:18 +0300, Tomi Valkeinen wrote:
Hi Tony,
Here is a bunch of board file patches related to DSS. They have all been
sent
for review earlier, and are currently in my tree. Some of them depend on DSS
driver
Hi Santosh,
On Thu, 8 Sep 2011, Santosh Shilimkar wrote:
Local timer clock is sourced from the CPU clock and hence changes
along with CPU clock. These per CPU local timers are used as
clock-events, so they need to be reconfigured on CPU frequency
change as part of CPUfreq governor.
Newly
On Mon, Sep 26, 2011 at 06:50:20PM +0200, Benoit Cousson wrote:
Add required clock frequencies for the i2c client devices existing
on beagle board.
Add the twl4030 basic description with only the twl_rtc module.
Add the EEPROM node.
Based on original patch from Manju:
On Wed, Sep 28, 2011 at 10:47:32AM -0700, Kevin Hilman wrote:
Cousson, Benoit b-cous...@ti.com writes:
Hi Grant, Kevin,
Should I go ahead with this version and repost the series with that
third patch?
Fine with me.
Grant let me know if you prefer if I merge it (with your ack) with
Grant Likely grant.lik...@secretlab.ca writes:
On Wed, Sep 28, 2011 at 10:47:32AM -0700, Kevin Hilman wrote:
Cousson, Benoit b-cous...@ti.com writes:
Hi Grant, Kevin,
Should I go ahead with this version and repost the series with that
third patch?
Fine with me.
Grant let me know
Hello Hemant,
a few comments:
On Thu, 29 Sep 2011, Hemant Pedanekar wrote:
This patch adds cpu type, macros for identification of TI814X device.
Note that following update to common OMAP data structures is made:
cpu_mask and RATE_IN_XXX flags have crossed 8 bit hence struct
2011/9/8 Santosh Shilimkar santosh.shilim...@ti.com:
Local timer clock is sourced from the CPU clock and hence changes
along with CPU clock. These per CPU local timers are used as
clock-events, so they need to be reconfigured on CPU frequency
change as part of CPUfreq governor.
This requires
Not all DPLLs are identical; some require special consideration such as
OMAP4's ABE DPLL, which can have an additional 4x multiplier added to
it's clock rate based on programming the REGM4XEN bit in it's CLKMODE
register.
Unfortunately the clock framework makes a few assumptions that all DPLLs
Hi
On Thu, 22 Sep 2011, Keerthy wrote:
From: Vishwanath BS vishwanath...@ti.com
OMAP4460 specific clocks are not getting added as the
cpu_is_omap44xx is choosing only OMAP4430 specific clock nodes.
Changing it to add to OMAP4460 specific clocks also.
This is clocks are required of
Hi
On Thu, 29 Sep 2011, Mike Turquette wrote:
Not all DPLLs are identical; some require special consideration such as
OMAP4's ABE DPLL, which can have an additional 4x multiplier added to
it's clock rate based on programming the REGM4XEN bit in it's CLKMODE
register.
Unfortunately the
On Thu, Sep 29, 2011 at 6:26 PM, Paul Walmsley p...@pwsan.com wrote:
Hi
On Thu, 29 Sep 2011, Mike Turquette wrote:
Not all DPLLs are identical; some require special consideration such as
OMAP4's ABE DPLL, which can have an additional 4x multiplier added to
it's clock rate based on
[]...
+ init_data-supply_regulator = (char *)of_get_property(dev-of_node,
+ regulator-supplies, NULL);
I'd expect that in the device tree world the supply regulator would
reference the node for that regulator.
You mean using phandles?
On Tue, Sep 27, 2011 at 03:42:49PM +0530, Rajendra Nayak wrote:
Modify the fixed regulator driver to extract fixed_voltage_config from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
Signed-off-by: Rajendra Nayak rna...@ti.com
---
On Tue, Sep 27, 2011 at 03:42:43PM +0530, Rajendra Nayak wrote:
Hi Mark, Grant,
This is a respin of my RFC series I posted sometime back
and is now based on top of the latest omap i2c-twl support
series posted by Benoit
git://gitorious.org/omap-pm/linux.git for_3.2/4_omap_dt_i2c_twl
some
On Tue, Sep 27, 2011 at 03:42:48PM +0530, Rajendra Nayak wrote:
The helper routine of_get_fixed_voltage_config() extracts
fixed_voltage_config structure contents from device tree.
Also add documenation for additional bindings for fixed
regulators that can be passed through dt.
On Tue, Sep 27, 2011 at 03:42:51PM +0530, Rajendra Nayak wrote:
Device nodes in DT can associate themselves with one or more
regulators by providing a list of phandles (to regulator nodes)
and corresponding supply names.
For Example:
devicenode: node@0x0 {
...
On Tue, Sep 27, 2011 at 01:10:04PM +0100, Mark Brown wrote:
On Tue, Sep 27, 2011 at 03:42:45PM +0530, Rajendra Nayak wrote:
+ init_data = devm_kzalloc(dev, sizeof(struct regulator_init_data),
+GFP_KERNEL);
+ if (!init_data)
+
On Tue, Sep 27, 2011 at 03:42:52PM +0530, Rajendra Nayak wrote:
Look up the regulator for a given consumer from device tree, during
a regulator_get(). If not found fallback and lookup through
the regulator_map_list instead.
Devices can associate with one or more regulators by providing a
On Thu, 2011-09-29 at 10:52 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [110925 23:04]:
On Tue, 2011-09-20 at 11:18 +0300, Tomi Valkeinen wrote:
Hi Tony,
Here is a bunch of board file patches related to DSS. They have all been
sent
for review earlier, and
Following 2 hwmod structures are added
1. usb_host_hs
The hwmod of usbhs with uhh, ehci and ohci base addresses
functional clock and ehci, ohci irqs
2. usb_tll_hs
hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Keshava Munegowda
From: Benoit Cousson b-cous...@ti.com
Following 2 hwmod structures are added
1. usb_host_hs
The hwmod of usbhs with uhh, ehci and ohci base addresses
functional clock and ehci, ohci irqs
2. usb_tll_hs
hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Benoit
The hwmod structure of usb_host_hs and usb_tll are
retrieved and registered with omap device
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
Reviewed-by: Partha Basak part...@india.ti.com
---
arch/arm/mach-omap2/usb-host.c | 100 ++--
1 files changed,
From: Keshava Munegowda keshava_mgo...@ti.com
device name usbhs clocks are changed from
usbhs-omap.0 to usbhs_omap; this is because
in the hwmod registration the device name is set
as usbhs_omap; The redudant clock nodes are removed.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
From: Keshava Munegowda keshava_mgo...@ti.com
The usbhs core driver does not enable/disable the interface and
functional clocks directly, These clocks are handled by runtime pm,
hence instead of the clock enable/disable, the runtime pm APIS are
used. however,the optional clocks and port clocks
On Thu, Sep 29, 2011 at 7:54 PM, Keshava Munegowda
keshava_mgo...@ti.com wrote:
From: Keshava Munegowda keshava_mgo...@ti.com
The Hwmod structures and Runtime PM features are implemented
For EHCI and OHCI drivers of OMAP3 and OMAP4.
The global suspend/resume of EHCI and OHCI
is validated on
55 matches
Mail list logo
