On Sun, 2011-03-27 at 04:39 +0200, Sebastian Reichel wrote:
Hi,
I've got problems getting a working tty with the mainline 2.6.38
kernel on my Nokia N900. Here is the related output from dmesg:
$ grep -E (omapdss|omapfb|acx565akm) dmesg
[0.890899] omapdss CORE: clk ick, rate 8300
This patch set enables powering down the isp1704 usb
tranceiver when not in use.
Tested on RX-51.
Kalle Jokiniemi (2):
isp1704_charger: allow board specific powering routine
RX-51: Enable isp1704 power on/off
arch/arm/mach-omap2/board-rx51-peripherals.c | 27 ++-
The ISP1704/1707 chip can be put to full power down
state by asserting the CHIP_SEL line. This patch enables
platform or board specific hooks to put the device into
power down mode in case not needed.
These patches are preparatio for enabling this powering
routine in n900 (rx-51) devices.
Thanks
Ugh, Monday morning :(
Managed to send old version of the patch, this has a boot issue. Please
disregard this patch set, I'll send V2 set soon...
- Kalle
-Original Message-
From: Jokiniemi Kalle (Nokia-MS/Tampere)
Sent: 28. maaliskuuta 2011 9:33
To: linux-...@vger.kernel.org;
The ISP1704/1707 chip can be put to full power down
state by asserting the CHIP_SEL line. This patch enables
platform or board specific hooks to put the device into
power down mode in case not needed.
These patches are preparatio for enabling this powering
routine in n900 (rx-51) devices.
Thanks
The isp1704 usb tranceiver is used for charging and can be
disabled when not in use. Provide the powering routine to
the driver via platform data.
Loosely based on earlier patches from Heikki Krogerus in
Nokia N900 maemo kernel.
Signed-off-by: Kalle Jokiniemi kalle.jokini...@nokia.com
Cc: Heikki
This patch set enables powering down the isp1704 usb
tranceiver when not in use.
Tested on RX-51 and MeeGo.
v2: fixed a boot issue in the 1/2 patch.
Kalle Jokiniemi (2):
isp1704_charger: allow board specific powering routine
RX-51: Enable isp1704 power on/off
+
static struct platform_device rx51_charger_device = {
- .name = isp1704_charger,
+ .name = isp1704_charger,
Both are same; you don’t need this change!
+ .dev= {
+ .platform_data = rx51_charger_data,
+ },
};
+static void __init
Hi,
-Original Message-
From: ext Keshava Munegowda [mailto:keshava_mgo...@ti.com]
Sent: 28. maaliskuuta 2011 10:19
To: Jokiniemi Kalle (Nokia-MS/Tampere); linux-...@vger.kernel.org; linux-
o...@vger.kernel.org; Felipe Balbi
Cc: Krogerus Heikki (Nokia-MS/Helsinki);
Hello.
On 28-03-2011 10:51, Kalle Jokiniemi wrote:
The ISP1704/1707 chip can be put to full power down
state by asserting the CHIP_SEL line. This patch enables
platform or board specific hooks to put the device into
power down mode in case not needed.
These patches are preparatio for
On 28-03-2011 10:51, Kalle Jokiniemi wrote:
The isp1704 usb tranceiver is used for charging and can be
disabled when not in use. Provide the powering routine to
the driver via platform data.
Loosely based on earlier patches from Heikki Krogerus in
Nokia N900 maemo kernel.
Signed-off-by:
Hello.
On 28-03-2011 5:49, Ramirez Luna, Omar wrote:
If an error occurs in the L3 on any other initiator than MPU,
the interrupt goes unhandled given that the 'base' register
was calculated with the initialized err_base value (which
coincidentally points to MPU) and not with the actual source
Hi,
On Sat, Mar 26, 2011 at 06:59:18PM -0400, Ben Gamari wrote:
Today I've been trying to work through the mess that is musb bring-up on
recent kernels (v2.6.38). While I still haven't succeeded in getting a
patches are welcome.
working gadget stack (modprobe g_ether fails with ENODEV), I've
Hi,
On Sat, Mar 26, 2011 at 07:42:34PM -0400, Ben Gamari wrote:
Today I've had a very frustrating time trying to bring up a BeagleBoard
(arch/arm/mach-omap2/board-omap2beagle.c) with the 2.6.38
there's no board-omap2beagle
kernel. Unfortunately musb has been giving me great difficulties,
Hi,
(break your lines at 80-chars, I asked you to do this before)
On Mon, Mar 28, 2011 at 08:06:32AM +, kalle.jokini...@nokia.com wrote:
Hi,
-Original Message-
From: ext Keshava Munegowda [mailto:keshava_mgo...@ti.com]
Sent: 28. maaliskuuta 2011 10:19
To: Jokiniemi
On Mon, Mar 28, 2011 at 12:20:02PM +0400, Sergei Shtylyov wrote:
+static void __init rx51_charger_init(void)
+{
+BUG_ON(gpio_request_one(RX51_USB_TRANSCEIVER_RST_GPIO,
+GPIOF_OUT_INIT_LOW, isp1704_reset));
I'm not sure we should kill the machine if this fails...
agreed.
Hi,
-Original Message-
From: ext Felipe Balbi [mailto:ba...@ti.com]
Sent: 28. maaliskuuta 2011 11:39
To: Jokiniemi Kalle (Nokia-MS/Tampere)
Cc: keshava_mgo...@ti.com; linux-...@vger.kernel.org; linux-
o...@vger.kernel.org; ba...@ti.com; Krogerus Heikki (Nokia-MS/Helsinki);
On Mon, Mar 28, 2011 at 08:52:23AM +, kalle.jokini...@nokia.com wrote:
Hi,
-Original Message-
From: ext Felipe Balbi [mailto:ba...@ti.com]
Sent: 28. maaliskuuta 2011 11:39
To: Jokiniemi Kalle (Nokia-MS/Tampere)
Cc: keshava_mgo...@ti.com; linux-...@vger.kernel.org;
Hi,
-Original Message-
From: ext Felipe Balbi [mailto:ba...@ti.com]
Sent: 28. maaliskuuta 2011 11:55
To: Jokiniemi Kalle (Nokia-MS/Tampere)
Cc: ba...@ti.com; keshava_mgo...@ti.com; linux-...@vger.kernel.org; linux-
o...@vger.kernel.org; Krogerus Heikki (Nokia-MS/Helsinki);
Hi Sakari,
On Sun, Mar 27, 2011 at 8:27 PM, Sakari Ailus
sakari.ai...@maxwell.research.nokia.com wrote:
Ramirez Luna, Omar wrote:
On Fri, Mar 25, 2011 at 10:13 AM, Sakari Ailus
sakari.ai...@maxwell.research.nokia.com wrote:
Hi,
This patchset is aimed to fix a problem in arch_iommu
Hi,
Add Anton Vorontsov cbouatmai...@gmail.com to your v3. This will
need ack from him, or this needs to go to him. In this case I guess we
are only dealing with RX51 stuff, so maybe this should go to Tony.
On Mon, Mar 28, 2011 at 09:51:38AM +0300, Kalle Jokiniemi wrote:
The ISP1704/1707 chip
On Mon, Mar 28, 2011 at 4:42 AM, Ramirez Luna, Omar omar.rami...@ti.com wrote:
Hi,
On Sun, Mar 27, 2011 at 12:27 PM, Sakari Ailus
sakari.ai...@maxwell.research.nokia.com wrote:
Ramirez Luna, Omar wrote:
On Fri, Mar 25, 2011 at 10:13 AM, Sakari Ailus
sakari.ai...@maxwell.research.nokia.com
Initialise hardware supervised mode for all clockdomains if it's
supported. Initiate sleep transition for other clockdomains,
if they are not being used.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
This patch exports APIs to get base address for GIC
distributor, CPU interface, SCU and PL310 L2 Cache which
are used in OMAP4 PM code.
This was suggested by Kevin Hilman khil...@ti.com during
OMAP4 PM code review.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Kevin Hilman
The SGI(Software Generated Interrupts) are not wakeup capable from
low power states. This is known limitation on OMAP4 and needs to be
worked around by using software forced clockdomain wake-up. CPU0 forces
the CPU1 clockdomain to software force wakeup. After the wakeup, CPU1
restores its
WakeupGen IP is integrated along with GIC to manage the
interrupt wakeups from CPU low power states. It's located in
always ON power domain. It manages masking/unmasking of
Shared peripheral interrupts(SPI).So the interrupt enable/disable
control should be in sync and consistent at WakeupGen and
This patch adds SAR RAM support on OMAP4430. SAR RAM used to save
and restore the HW context in low power modes.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/include/mach/omap4-common.h |1 +
This patch adds OMAP WakeupGen support. The WakeupGen unit is responsible
for generating wakeup event from the incoming interrupts and enable bits.
The WakeupGen is implemented in MPU Always-On power domain. During normal
operation, WakeupGen delivers external interrupts directly to the GIC.
When
OMAP L2X0 and GIC initialisation code uses BUG_ON() for the
ioremap() failure scenarios.
Use WARN_ON() instead and allow graceful function exits.
This was suggsted by Kevin Hilman khil...@ti.com during
OMAP4 PM code review.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Kevin
As per OMAP4430 TRM, the dynamic dependency between MPUSS-MEMIF
and MPUSS-L3_MAIN_1 clockdomains is enable by default. Refer
register CM_MPU_DYNAMICDEP description for details.
But it doesn't seems to work as expected and MPUSS doesn't wakeup
from off-mode if the static dependency is not set
V3 updates:
It's same as V2 with couple of minor updates and its rebased on Kevin's
latest pm-core branch.
- Dropped 'enable_off_mode' flag altogether for OMAP4 as discussed on the list.
- Removed non-supported pm debug entries
The following changes since commit
On OMAP4 when attempting MPU off-mode or OSWR, the GIC context is
lost. This patch adds GIC context save and restore support.
The context save is done by software and restore is done by
ROM code from predefined SAR locations where the context supposed
to be saved. Refer to OMAP4430 TRM for the
From: Rajendra Nayak rna...@ti.com
The patch adds a basic CPUidle driver for OMAP4. Just
one C state is registered for CPU0 which does a WFI.
CPU1 is left with defualt idle and the low power state
for it is managed via cpu-hotplug.
Signed-off-by: Rajendra Nayak rna...@ti.com
Signed-off-by:
Program non-boot CPUs to hit lowest supported power state
when it is off-lined using cpu hotplug framework.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/omap-hotplug.c | 18 +-
1 files changed, 13
The power management code needs to have access to enable/disable the
gic cpu interface and distributor based on targetted low power
states.
These APIs are suppose to me moved to common ARM GIC library and patch
for the same was posted earlier. The GIC code refactoring is ongoing
and hence for
This patch adds the CPU0 and CPU1 off mode support. CPUX close switch
retention (CSWR) is not supported by hardware design.
The CPUx OFF mode isn't supported on OMAP4430 ES1.0
CPUx sleep code is common for hotplug, suspend and CPUilde.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
When MPUSS hits off-mode e, L2 cache is lost. This patch adds L2X0
necessary maintenance operations and context restoration in the
low power code.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/omap4-mpuss-lowpower.c | 18
This patch adds MPUSS low power states in cpuidle.
C1 - CPU0 ON + CPU1 ON + MPU ON
C2 - CPU0 ON + CPU1 OFF + MPU ON
C3 - CPU0 OFF + CPU1 OFF + MPU CSWR
C4 - CPU0 OFF + CPU1 OFF + MPU OFF
MPU OSWR isn't supported yet. To support OSWR, power domain context
registers
On OMAP4430 ES1.0, Power Management features are not supported.
Avoid omap4_pm_init() on ES1.0 silicon so that we can continue
to use same kernel binary to boot on all OMAP4 silicons.
The ES1.0 boot failure with OMAP4 PM series was because of
the clockdomain initialisation code. Hardware
On OMAP4 CPUidle, the low power states are triggered when CPU1
is offlined to OFF power state. When the CPU1 is online, no
low power states are supported.
The patch adds CPU hotplug notifier to manage the C-state
states using CPUidle prepare() hook and CPUIDLE_FLAG_IGNORE
c-state flag.
This was
With OMAP4 suspend, idle and hotplug series, we no longer need
do_wfi() macro.
Remove the same.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/include/mach/omap4-common.h | 10 --
1 files changed, 0 insertions(+), 10
CPU local timer(TWD) stops when the CPU is transitioning into
deeper C-States. Since these timers are not wakeup capable, we
need the wakeup capable global timer to program the wakeup time
depending on the next timer expiry.
It can be handled by registering a global wakeup capable timer along
This patch adds MPUSS(MPU Sub System) RET and OFF mode support
to suspend path. For both MPUSS RET and OFF support, CPUs are
programmed to OFF state.
Only MPUSS RET and OFF supported at this point of time. CORE RET
will be added subsequently.
Signed-off-by: Santosh Shilimkar
This patch adds configurable wakeup timer support in suspend. Also
for statistics pm counter support is added.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/omap4-mpuss-lowpower.c |4
arch/arm/mach-omap2/pm-debug.c
Hello,
-Original Message-
From: Heikki Krogerus [mailto:heikki.kroge...@nokia.com]
Sent: 28. maaliskuuta 2011 12:13
To: Jokiniemi Kalle (Nokia-MS/Tampere)
Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org; ba...@ti.com;
jhnik...@gmail.com; khil...@ti.com
Subject: Re:
Hi,
-Original Message-
From: ext Sergei Shtylyov [mailto:sshtyl...@mvista.com]
Sent: 28. maaliskuuta 2011 11:20
To: Jokiniemi Kalle (Nokia-MS/Tampere)
Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org; ba...@ti.com;
Krogerus Heikki (Nokia-MS/Helsinki);
Hi,
-Original Message-
From: ext Sergei Shtylyov [mailto:sshtyl...@mvista.com]
Sent: 28. maaliskuuta 2011 11:18
To: Jokiniemi Kalle (Nokia-MS/Tampere)
Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org; ba...@ti.com;
Krogerus Heikki (Nokia-MS/Helsinki);
Kevin
-Original Message-
From: Kevin Hilman [mailto:khil...@ti.com]
Sent: Friday, March 25, 2011 8:54 PM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; Rajendra Nayak; linux-arm-
ker...@lists.infradead.org
Subject: Re: [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug and
Kevin,
I am testing Smartreflex on your Branch 'pm-wip/voltdm'. There seems
an issue with reading VP registers.
For OMAP3 and OMAP4 reading debugfs entries shows constant voltage.
Logs are:
OMAP3:
# cat /debug/voltage/vdd_mpu_iva/curr_nominal_volt
120
# cat
Kevin,
-Original Message-
From: Kevin Hilman [mailto:khil...@ti.com]
Sent: Friday, March 25, 2011 8:54 PM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; Rajendra Nayak; linux-arm-
ker...@lists.infradead.org
Subject: Re: [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug and
Hello All,
Any comments on this patch?
Regards,
Keerthy
On Wed, Mar 2, 2011 at 2:17 AM, Keerthy j-keer...@ti.com wrote:
twl4030_wdt driver and omap_wdt driver are registering as misc_device name as
watchdog and the same minor number WATCHDOG_MINOR( value = 130).
There is a conflict since the
On Fri, Mar 25, 2011 at 4:23 PM, Nicolas Pitre nicolas.pi...@linaro.org wrote:
On Fri, 25 Mar 2011, Jason Kridner wrote:
I very much like this approach. I believed the ability to use the die
ID to get a unique code was reasonable approach and that is why I
didn't get an EEPROM put onto the
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Gulati, Shweta
Sent: Monday, March 28, 2011 4:23 PM
To: linux-omap@vger.kernel.org; Kevin Hilman
Subject: Smartreflex on 'pm-wip/voltdm' Branch
Kevin,
I am testing
Patch series to support mstandby mode handling and enabling runtime PM
support for DMA driver.
Change History:
v4:
Fixed Paul's comment:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg47359.html
v3:
Warning fix:
http://thread.gmane.org/gmane.linux.ports.arm.omap/54753/focus=55097
v2:
If two DMA users tries to set no mstandby mode at the same time, a race
condition would arise. Prevent that by using a spin lock and counting
up/down the number of times nostandby is set/reset.
Initial patch is created by Adrian Hunter adrian.hun...@nokia.com
Certain errata in OMAP2+ processors will require forcing
master standby to no standby mode before completing on going
operation. Without this, the results will be unpredictable.
Since current implementation of PM run time framework does not support
changing sysconfig settings during middle of the
The current DMA context restore clears all the DMA channel registers
even if the channels are in use. This will result in transfer failures
if repeated DMA transfers are initiated with one time DMA channel
configuration.
Also, remove access to sysconfig register during context save/restore
since
Enable runtime pm and use pm_runtime_get_sync and pm_runtime_put_autosuspend
for OMAP DMA driver.
The DMA driver uses auto suspend feature of runtime pm framework through
which the clock gets disabled automatically if there is no activity for
more than one second.
Testing:
Compile:
On Mon, 28 Mar 2011 11:34:51 +0300, Felipe Balbi ba...@ti.com wrote:
Hi,
On Sat, Mar 26, 2011 at 06:59:18PM -0400, Ben Gamari wrote:
Today I've been trying to work through the mess that is musb bring-up on
recent kernels (v2.6.38). While I still haven't succeeded in getting a
patches
On Mon, 28 Mar 2011 11:37:22 +0300, Felipe Balbi ba...@ti.com wrote:
Hi,
On Sat, Mar 26, 2011 at 07:42:34PM -0400, Ben Gamari wrote:
Today I've had a very frustrating time trying to bring up a BeagleBoard
(arch/arm/mach-omap2/board-omap2beagle.c) with the 2.6.38
there's no
Hi,
On Mon, Mar 28, 2011 at 12:38 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
If an error occurs in the L3 on any other initiator than MPU,
the interrupt goes unhandled given that the 'base' register
was calculated with the initialized err_base value (which
coincidentally points to
Hi Santosh,
Santosh Shilimkar santosh.shilim...@ti.com writes:
[...]
Have created two branches as you suggested against latest
pm-core.
Thanks!
1) OMAP4-PM series:
git://dev.omapzoom.org/pub/scm/santosh/kernel-omap4-base.git
omap4_pm_pmcore_v3
Also, can you post this version of the
-Original Message-
From: Kevin Hilman [mailto:khil...@ti.com]
Sent: Monday, March 28, 2011 9:27 PM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; Rajendra Nayak; linux-arm-
ker...@lists.infradead.org
Subject: Re: [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug and
CPUilde
On Mon, 2011-03-28 at 08:56 -0700, Kevin Hilman wrote:
[...]
1) OMAP4-PM series:
git://dev.omapzoom.org/pub/scm/santosh/kernel-omap4-base.git
omap4_pm_pmcore_v3
Also, can you post this version of the series to the list,
w/linux-arm-kernel Cc'd.
Oops, sorry. I see it's already posted
Rafael J. Wysocki r...@sisk.pl writes:
From: Rafael J. Wysocki r...@sisk.pl
Replace the sysdev class and struct sys_device used for power
management in the OMAP's GPIO code with a struct syscore_ops object
which is simpler.
Signed-off-by: Rafael J. Wysocki r...@sisk.pl
Acked-by: Kevin
Vishwa, Shweta,
Vishwanath Sripathy vishwanath...@ti.com writes:
[...]
I am testing Smartreflex on your Branch 'pm-wip/voltdm'. There seems
an issue with reading VP registers.
For OMAP3 and OMAP4 reading debugfs entries shows constant voltage.
Thanks for testing.
[...]
I did a quick
Hi Rajendra,
On Mon, 21 Mar 2011, Rajendra Nayak wrote:
On 3/11/2011 10:17 PM, Kevin Hilman wrote:
Rajendra Nayakrna...@ti.com writes:
[...]
It's also breaking boot on OMAP35xx BeagleBoard rev C2. The kernel
boot messages are below - omap2plus_defconfig + DEBUG_LL.
On Monday, March 28, 2011, Ben Dooks wrote:
On Mon, Mar 28, 2011 at 01:29:49AM +0200, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki r...@sisk.pl
Replace sysdev classes and struct sys_device objects used for core
power management by Samsung platforms with struct syscore_ops objects
* Santosh Shilimkar santosh.shilim...@ti.com [110328 02:20]:
--- a/arch/arm/mach-omap2/omap4-common.c
+++ b/arch/arm/mach-omap2/omap4-common.c
@@ -21,6 +21,7 @@
#include mach/hardware.h
#include mach/omap4-common.h
+#include mach/omap-wakeupgen.h
#ifdef CONFIG_CACHE_L2X0
void
* Santosh Shilimkar santosh.shilim...@ti.com [110328 02:20]:
OMAP L2X0 and GIC initialisation code uses BUG_ON() for the
ioremap() failure scenarios.
Use WARN_ON() instead and allow graceful function exits.
This was suggsted by Kevin Hilman khil...@ti.com during
OMAP4 PM code review.
* Santosh Shilimkar santosh.shilim...@ti.com [110328 02:21]:
--- a/arch/arm/mach-omap2/pm-debug.c
+++ b/arch/arm/mach-omap2/pm-debug.c
@@ -40,6 +41,11 @@ static int omap4_pm_suspend(void)
int state, ret = 0;
u32 cpu_id = smp_processor_id();
+ /* Wakeup timer from suspend
On Mon, Mar 28, 2011 at 09:01:29AM +0300, Tomi Valkeinen wrote:
On Sun, 2011-03-27 at 04:39 +0200, Sebastian Reichel wrote:
Hi,
I've got problems getting a working tty with the mainline 2.6.38
kernel on my Nokia N900. Here is the related output from dmesg:
$ grep -E
Hi All,
Hello All,
Any comments on this patch?
Regards,
Keerthy
On Wed, Mar 2, 2011 at 2:17 AM, Keerthy j-keer...@ti.com wrote:
twl4030_wdt driver and omap_wdt driver are registering as misc_device name
as
watchdog and the same minor number WATCHDOG_MINOR( value = 130).
There
* Tomi Valkeinen tomi.valkei...@ti.com [110323 00:43]:
On Tue, 2011-03-22 at 13:49 -0500, Felipe Contreras wrote:
On Mon, Mar 21, 2011 at 11:51 AM, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
Here are OMAP display subsystem patches for 2.6.39 merge window. Quite a
bit of them, and many
* Hema HK hem...@ti.com [110324 04:03]:
omap4430_phy_init() function can be called with no device pointer
to powerdown the UTMI PHY during board init when USB is disabled.
Fix the function accordingly.
I don't think this is the case any longer, see merge commit
* Hema HK hem...@ti.com [110324 04:36]:
omap4430_phy_init() function can be called with no device pointer,
to powerdown the PHY during board init when USB is disabled.
Fix the function accordingly.
This should no longer be needed after merge commit
0df0914d414a504b975f3cc66ace0c16ef55b7f3.
Hi all,
This series continues the work to only initialize minimal omap code
in init_early and to cut down dependencies to code that should be
initialized later. It also cleans up the omap2+ timer init code to prepare
things for the later patches.
After this series further patches can make the
This allows us to remove cpu_is_omap calls from init_irq functions
and the irq handler. There should not be any need for cpu_is_omap
as at this point we only care about SoC generation, and not about
subcategories.
The main reason for the patch is that we want to initialize only
minimal omap
This is needed for the following patches to initialize non-sys_timer
hardware later on. Again, there's no need to do cpu_is_omap calls
as we only care about the major omap generation. We can do this with
the .timer entry alone.
Note that for now we just set stubs for the various sys_timer
entries
These will be needed when dmtimer platform init code gets split
for omap1 and omap2+. These will also be needed for inline macros
for sys_timer in the following patches. No functional changes.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/plat-omap/dmtimer.c | 121
This patch makes timer-gp.c to use only a subset of dmtimer
functions without the need to initialize dmtimer code early.
Note that omap_dmtimer_init_one can eventually be moved to
omap2+ specific dmtimer.c.
Also note that now with the inline functions, timer_set_next_event
becomes more efficient
This removes the support for setting the wake-up timer for debugging.
Later on we can reserve gptimer1 for PM code only and have similar
functionality.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/pm-debug.c | 27 ---
arch/arm/mach-omap2/pm.h
There's no need to initialize the dmtimer framework early.
Just mark the clocksource and timesource as reserved, and
initialize dmtimer with an arch_initcall.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap1/timer32k.c|4
arch/arm/mach-omap2/timer-gp.c
This will allow us to share the code between system timer and
dmtimer device driver code without having to initialize all
dmtimers early. It will also make the timer_set_next_event
more efficient as the inline functions will optimize the code
better in this case.
Signed-off-by: Tony Lindgren
Use dmtimer macros for clocksource. As with the clockevent,
this allows us to initialize the rest of dmtimer code later on.
Note that eventually we will be initializing the timesource
from init_early so sched_clock will work properly for
CONFIG_PRINTK_TIME.
Signed-off-by: Tony Lindgren
This is no longer needed as we now just set the desired
.timer in MACHINE_START. We can now also remove timer-gp.h.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/board-4430sdp.c|4
arch/arm/mach-omap2/board-devkit8000.c |4
We can keep everything sys_timer and gptimer.c related code in
timer.c as the code will be very minimal.
Later on we can also remove timer-mpu.c, as it can be called from
omap4_timer_init function.
This allows us to get rid of confusing existing files. We currently
have timer-gp.c, timer-mpu.c,
The DSI protocol engine has no interrupt for signalling the end of a Frame
transfer. The present approach is to send a BTA after DISPC generates a
FRAMEDONE interrupt, and unlock the dsi bus only when the BTA Ack is received.
The assumption made with this approach was that OMAP will send a BTA
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:20 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Add omap
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:20 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Add omap
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:31 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-debug:
Hi,
-Original Message-
From: Jokiniemi Kalle (Nokia-MS/Tampere)
snip
diff --git a/include/linux/power/isp1704_charger.h
b/include/linux/power/isp1704_charger.h
new file mode 100644
index 000..68096a6
--- /dev/null
+++
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:20 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Add omap
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:31 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-debug:
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:20 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Add omap
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:31 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-debug:
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:20 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Add omap
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:31 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-debug:
As a part of Voltage Layer Cleanup Patches,
submitted by Kevin Hilman, Voltage domain
Information is removed from hwmod,
So the patch removes 'vdd_name' info from omap_hwmod
and adds that info into dev_attr as SR code uses vdd_name
to get voltagedomain sructure info.
Tested on OMAP3630 SDP and
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, March 29, 2011 2:20 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
linux-arm-ker...@lists.infradead.org
Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Add omap
100 matches
Mail list logo
