On Wed, Jul 13, 2011 at 07:24:17PM +0530, Tarun Kanti DebBarma wrote:
From: Charulatha V ch...@ti.com
Call runtime pm APIs pm_runtime_get_sync() and pm_runtime_put_sync()
for enabling/disabling clocks appropriately. Remove syscore_ops and
instead use dev_pm_ops now.
...
+ /*
+ *
On Wed, Jul 13, 2011 at 05:00:35PM +0300, Tero Kristo wrote:
OMAP SMPS regulator driver provides access to OMAP voltage processor
controlled regulators. These include VDD1 and VDD2 for OMAP3 and additionally
VDD3 for OMAP4. SMPS regulators use the OMAP voltage layer for the actual
voltage
On Wed, 2011-07-13 at 19:49 +0200, Premi, Sanjeev wrote:
Texas Instruments Oy, Tekniikantie 12, 02150 Espoo. Y-tunnus: 0115040-6.
Kotipaikka: Helsinki
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Kristo, Tero
-Original Message-
From: Todd Poynor [mailto:toddpoy...@google.com]
Sent: Thursday, July 14, 2011 11:40 AM
To: DebBarma, Tarun Kanti
Cc: linux-omap@vger.kernel.org; Hilman, Kevin; Shilimkar, Santosh;
t...@atomide.com; linux-arm-ker...@lists.infradead.org; Varadarajan,
Charulatha
On Thu, 2011-07-14 at 08:29 +0200, Todd Poynor wrote:
On Wed, Jul 13, 2011 at 05:00:35PM +0300, Tero Kristo wrote:
OMAP SMPS regulator driver provides access to OMAP voltage processor
controlled regulators. These include VDD1 and VDD2 for OMAP3 and
additionally
VDD3 for OMAP4. SMPS
On Thu, 2011-07-14 at 02:22 +0200, Hilman, Kevin wrote:
Hi Tero,
Tero Kristo t-kri...@ti.com writes:
Based on the comments for the previous version of this set, I implemented
a regulator driver for the OMAP SMPS now.
Could you rebase this on my pm-wip/voltdm branch where I've started
* Felipe Balbi ba...@ti.com [110708 04:53]:
Are you or are you not taking now board files ? We have one which was
left out due to a comment from Russell stating that no new board-files
would be accepted until the move to device tree was completed [1]
Well looking at the cumulative diffstats,
* Jan Weitzel j.weit...@phytec.de [110713 05:51]:
Am Mittwoch, den 13.07.2011, 16:13 +0400 schrieb Sergei Shtylyov:
Have you added that 'i' at the end intentionally?
Thank you. It was a tribute to vim.
:i)
I'll fold the fixed patch into your original patch. Will also
keep the new
On Tue, Jul 12, 2011 at 02:39:45PM -0300, Victhor wrote:
| drivers/usb/musb/tusb6010_omap.c: In function 'tusb_omap_use_shared_dmareq':
| drivers/usb/musb/tusb6010_omap.c:92: error: 'musb' undeclared (first use in
this function)
| drivers/usb/musb/tusb6010_omap.c:92: error: (Each undeclared
* Tony Lindgren t...@atomide.com [110714 00:22]:
* Felipe Balbi ba...@ti.com [110708 04:53]:
Are you or are you not taking now board files ? We have one which was
left out due to a comment from Russell stating that no new board-files
would be accepted until the move to device tree was
On Thu, 2011-07-14 at 00:55 +0200, Mark Brown wrote:
On Wed, Jul 13, 2011 at 06:53:45PM +0300, Tero Kristo wrote:
On Wed, 2011-07-13 at 16:40 +0200, Mark Brown wrote:
I do strongly prefer the idiom of just registering all the regulators
even if they're read only.
Number of available
Am Donnerstag, den 14.07.2011, 00:34 -0700 schrieb Tony Lindgren:
* Jan Weitzel j.weit...@phytec.de [110713 05:51]:
Am Mittwoch, den 13.07.2011, 16:13 +0400 schrieb Sergei Shtylyov:
Have you added that 'i' at the end intentionally?
Thank you. It was a tribute to vim.
:i)
-Original Message-
From: Kristo, Tero
Sent: Thursday, July 14, 2011 12:41 PM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org;
broo...@opensource.wolfsonmicro.com; Girdwood, Liam; Hilman, Kevin
Subject: RE: [PATCHv2 4/5] TEMP: OMAP3: beagle rev-c4: enable OPP6
On Wed,
As noted by Grant Likely grant.lik...@secretlab.ca, omap2+ Makefile
unnecessarily
repeats entries for common device init code instead of using Kconfig symbol.
Remove references to hsmmc.o and board-flash.o. Also omap_phy_internal.o
references can be removed once it has some Kconfig symbol to
On Thursday 14 July 2011 02:57 AM, Hilman, Kevin wrote:
On Wed, Jul 13, 2011 at 2:15 PM, Kevin Hilmankhil...@ti.com wrote:
Ben Dooksben-...@fluff.org writes:
On Tue, Jul 05, 2011 at 02:50:46PM +0530, Shubhrajyoti D wrote:
Currently the OMAP4 doesnot hit device off still the
driver may have
Hi all,
Playing with USB ethernet gadget on IGEP boards with mainline kernel
(Linux 3.0.0-rc7) I observed one strange behavior. The ethernet gadget
works with one board with OMAP3530 but it doesn't with another one
with DM3730. The log looks like this:
root@igep00x0:~# modprobe g_ether
[
Hi All,
Just wondering if anyone had any figures for how much data one can expect
the omap3's usb controller to handle?
I'm trying to get a playstation eye (ov534) camera to run as at 60fps,
but gspca is giving me payload errors at 50fps or 60fps. (50*640*480 bytes
per sec, or about 122Mbits /
Shubhrajyoti shubhrajy...@ti.com writes:
On Thursday 14 July 2011 02:57 AM, Hilman, Kevin wrote:
On Wed, Jul 13, 2011 at 2:15 PM, Kevin Hilmankhil...@ti.com wrote:
Ben Dooksben-...@fluff.org writes:
On Tue, Jul 05, 2011 at 02:50:46PM +0530, Shubhrajyoti D wrote:
Currently the OMAP4
Shubhrajyoti D shubhrajy...@ti.com writes:
Restore of context is not done for OMAP4. This patch
Subject says context *save*, here says context *restore.*
adds the OMAP_I2C_FLAG_RESET_REGS_POSTIDLE in the OMAP4
hwmod which activates the restore for OMAP4.
s/hwmod/hwmod data/
Currently the
Restore of context is not done for OMAP4. This patch
adds the OMAP_I2C_FLAG_RESET_REGS_POSTIDLE in the OMAP4
hwmod data which activates the restore for OMAP4.
Currently the OMAP4 does not hit device off still the
driver may have support for it.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
Restore of context is not done for OMAP4. This patch
adds the OMAP_I2C_FLAG_RESET_REGS_POSTIDLE in the OMAP4
hwmod data which activates the restore for OMAP4.
Currently the OMAP4 does not hit device off still the
driver may have support for it.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
Please ignore the patch sent another one with correct sub line
On Thursday 14 July 2011 10:03 PM, Shubhrajyoti D wrote:
Restore of context is not done for OMAP4. This patch
adds the OMAP_I2C_FLAG_RESET_REGS_POSTIDLE in the OMAP4
hwmod data which activates the restore for OMAP4.
Currently the
Shubhrajyoti D shubhrajy...@ti.com writes:
Restore of context is not done for OMAP4. This patch
adds the OMAP_I2C_FLAG_RESET_REGS_POSTIDLE in the OMAP4
hwmod data which activates the restore for OMAP4.
Currently the OMAP4 does not hit device off still the
driver may have support for it.
Fixes logic bug that software flow control cannot be disabled, because
serial_omap_configure_xonxoff() is not called if both IXON and IXOFF bits
are cleared.
Signed-off-by: Nick Pelly npe...@google.com
---
drivers/tty/serial/omap-serial.c |3 +--
1 files changed, 1 insertions(+), 2
Hi Hemant,
On Wed, 2011-07-13 at 05:07 +0530, Pedanekar, Hemant wrote:
Any comments on the hwmod and clock patch sets?
I just discovered that other devices in this family are coming along
which will require changing the names/macros/etc. from 816x to 81xx[1].
Merging this series, followed
From: Jon Hunter jon-hun...@ti.com
Various clock fixes for OMAP3 and OMAP4 devices.
Plus one debug patch (if anyone is interested).
Jon Hunter (4):
OMAP4: Add missing clock divider for OCP_ABE_ICLK
OMAP3+: use DPLLs recalc function instead of omap2_get_dpll_rate
OMAP3+: Update DPLL Fint
From: Jon Hunter jon-hun...@ti.com
The parent clock of the OCP_ABE_ICLK is the AESS_FCLK and the
parent clock of the AESS_FCLK is the ABE_FCLK...
ABE_FCLK -- AESS_FCLK -- OCP_ABE_ICLK
The AESS_FCLK and OCP_ABE_ICLK clocks both have dividers which
determine their operational frequency. However,
From: Mike Turquette mturque...@ti.com
OMAP4 DPLL_ABE can enable a 4X multipler on top of the normal MN multipler
and divider. This is achieved by setting CM_CLKMODE_DPLL_ABE.DPLL_REGM4XEN
bit in CKGEN module of CM1. From the OMAP4 TRM:
Fdpll = Fref x 2 x (4 x M/(N+1)) in case REGM4XEN bit field
From: Mike Turquette mturque...@ti.com
omap3_noncore_dpll_set_rate uses omap2_dpll_round_rate explicitly. Instead
use the struct clk pointer's round_rate function to allow for DPLL's with
special needs.
Also the rounded rate can differ from target rate, so to better reflect
reality set clk-rate
From: Jon Hunter jon-hun...@ti.com
This is a continuation of Mike Turquette's patch OMAP3+: use
DPLL's round_rate when setting rate.
omap3_noncore_dpll_set_rate() and omap3_noncore_dpll_enable() call
omap2_get_dpll_rate() explicitly. It may be necessary for some
DPLLs to use a different function
From: Jon Hunter jon-hun...@ti.com
The OMAP36xx and OMAP4xxx DPLLs have a different internal reference
clock frequency (fint) operating range than OMAP3430. Update the
dpll_test_fint() function to check for the correct frequency ranges
for OMAP36xx and OMAP4xxx.
For OMAP36xx and OMAP4xxx
From: Jon Hunter jon-hun...@ti.com
Add a debugfs node called summary to /sys/kernel/debug/clock/
that displays a quick summary of all clocks registered in the
clocks structure. The format of the output from this node is:
clock-name parent-name rate usecount
This debugfs node was very helpful
Hi Kevin,
Hilman, Kevin wrote on Friday, July 15, 2011 3:28 AM:
Hi Hemant,
On Wed, 2011-07-13 at 05:07 +0530, Pedanekar, Hemant wrote:
Any comments on the hwmod and clock patch sets?
I just discovered that other devices in this family are coming along
which will require changing the
On Fri, Jul 15, 2011 at 12:19 AM, Nick Pelly npe...@google.com wrote:
Fixes logic bug that software flow control cannot be disabled, because
serial_omap_configure_xonxoff() is not called if both IXON and IXOFF bits
are cleared.
Thanks, Good Point.
need to send to this patch to
34 matches
Mail list logo
