AM3505/3517 don't have IO wakeup capability, so we don not need to set
the bit OMAP3430_EN_IO and the bit OMAP3430_EN_IO_CHAIN in the register
PM_WKEN_WKUP when the system enters retention.
Signed-off-by: Stanley.Miao stanley.m...@windriver.com
---
arch/arm/mach-omap2/id.c |2 ++
Andi Kleen wrote:
Zach Pfeffer zpfef...@codeaurora.org writes:
This patch contains the documentation for and the main header file of
the API, termed the Virtual Contiguous Memory Manager. Its use would
allow all of the IOMMU to VM, VM to device and device to IOMMU
interoperation code to be
On 06/25/2010 03:25 AM, Simon Horman wrote:
On Thu, Jun 24, 2010 at 10:14:14AM +0200, Sebastien Jan wrote:
Define a new module parameter 'macaddr' to override the MAC address
fetched either from eeprom, or randomly generated.
The expected MAC address shall be in the 01:23:45:67:89:AB format.
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Friday, June 25, 2010 4:55 AM
To: Gopinath, Thara
Cc: linux-omap@vger.kernel.org; p...@pwsan.com; Cousson, Benoit; Sripathy,
Vishwanath; Sawant, Anand
Subject: Re: [PATCH 0/8] OMAP3: Adding Smartreflex and
Hi Simon,
On 6/25/2010 2:40 AM, Que, Simon wrote:
Hi,
We are introducing a kernel driver for hardware spinlock, called hwspinlock.
It is designed to interface with the OMAP4 hardware spinlock module. This
driver supports:
- Reserved spinlocks for internal use
- Dynamic allocation of
Hi Sebastien,
I'm confused as to why this is desirable when the mac address
can already be configured after module insertion via
smsc95xx_netdev_ops.eth_mac_addr().
For example for booting over NFS using a pre-defined MAC address, with
a minimal setup (no initrd). Or is there another
On Wed, Jun 23, 2010 at 5:16 AM, Nishanth Menon n...@ti.com wrote:
Introduce a single omap generic check_revision that routes the
request to the right revision of check_revision.
Cc: Tony Lindgren t...@atomide.com
Cc: Angelo Arrifano mik...@gmail.com
Cc: Zebediah C. McClure z...@lurian.net
[Reply 1/2]
Gopinath, Thara had written, on 06/24/2010 10:02 AM, the following:
This patch removes the usage of vdd and sr id alltogether.
good.. thanks for doing this :). /me had enough of them ;)
This is achieved by introducing a separte voltage domain per
VDD and hooking this up with the
Kevin,
On 6/25/2010 1:44 AM, Kevin Hilman wrote:
From: Rajendra Nayakrna...@ti.com
Enable omap_device layer support for OMAP4, so that drivers can
use them to enable/idle/shutdown devices.
Signed-off-by: Rajendra Nayakrna...@ti.com
Signed-off-by: Benoit Coussonb-cous...@ti.com
Cc: Paul
Grazvydas Ignotas had written, on 06/25/2010 04:31 AM, the following:
On Wed, Jun 23, 2010 at 5:16 AM, Nishanth Menon n...@ti.com wrote:
Introduce a single omap generic check_revision that routes the
request to the right revision of check_revision.
[...]
diff --git
On Fri, Jun 25, 2010 at 3:52 AM, Kanigeri, Hari h-kanige...@ti.com wrote:
I don't know what PCMIIW stands for :)
please correct me if I'm wrong :)
It looks like the variable mbox_configured that was added previously doesn't
cover all the issues. It covers the shutdown issue with reference
sgx, iva, l2cache, sgx, neon, isp are generic features, make
them generic features, current OMAP3 detection mechanism
is still retained. 192Mhz is more specific OMAP3 feature
so it is retained as is
Cc: Tony Lindgren t...@atomide.com
Cc: Angelo Arrifano mik...@gmail.com
Cc: Zebediah C. McClure
Introduce a single omap generic check_revision that routes the
request to the right revision of check_revision.
Cc: Tony Lindgren t...@atomide.com
Cc: Angelo Arrifano mik...@gmail.com
Cc: Zebediah C. McClure z...@lurian.net
Cc: Alistair Buxton a.j.bux...@gmail.com
Cc: Grazvydas Ignotas
On Wed, 2010-06-23 at 08:57 +0100, Tony Lindgren wrote:
MVFR0 and MVFR1 are only available starting with ARM1136 r1p0 release
according to B.5 VFP changes in DDI0211F_arm1136_r1p0_trm.pdf. This is
also when TLS register got added, so we can use HAS_TLS also to test for
MVFR0 and MVFR1.
Nishant,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Menon, Nishanth
Sent: Friday, June 25, 2010 6:57 PM
To: linux-omap
Cc: Menon, Nishanth; Tony Lindgren; Angelo Arrifano; Zebediah C. McClure;
Alistair Buxton;
DebBarma, Tarun Kanti had written, on 06/25/2010 08:50 AM, the following:
Nishant,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Menon, Nishanth
Sent: Friday, June 25, 2010 6:57 PM
To: linux-omap
Cc: Menon, Nishanth;
On Wed, Jun 23, 2010 at 4:03 PM, Ghorai, Sukumar s-gho...@ti.com wrote:
[Ghorai] It's working for me.
it's good to hear !
This is what I see:
## Booting image at 81c0 ...
Image Name: Linux-2.6.35-rc3-1-g945a7eb
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:
On Fri, Jun 25, 2010 at 5:05 PM, Neshama Parhoti pnesh...@gmail.com wrote:
1. console=ttyS0
you are absolutely right !!!
i changed it to ttyS0 and now I get the boot msgs ! :)
can you please check out my whole boot args to see if i have any other error ?
just to make sure..
setenv
On Fri, 25 Jun 2010 17:05:53 +0300
Neshama Parhoti pnesh...@gmail.com wrote:
1. console=ttyS0
are you sure ? all TI's docs state ttyS2 (and this works for me with
TI's BSP kernels)
Its ttyS0 if the omap serial driver is compiled in. The omap driver
takes the ports instead of the 8250
Hi Steve,
Thanks for your answer.
On 06/25/2010 10:43 AM, steve.glendinn...@smsc.com wrote:
[...]
I can see you have a different use case, but I don't think this specific
driver is the place for this logic. I'd rather see it added to either
the usbnet framework or (preferably) the netdev
On Fri, Jun 25, 2010 at 5:15 PM, Graeme Gregory d...@xora.org.uk wrote:
Its ttyS0 if the omap serial driver is compiled in. The omap driver
takes the ports instead of the 8250 driver.
thank you, now it makes sense !
Graeme
--
To unsubscribe from this list: send the line unsubscribe
On Fri, Jun 25, 2010 at 7:25 PM, Nishanth Menon n...@ti.com wrote:
DebBarma, Tarun Kanti had written, on 06/25/2010 08:50 AM, the following:
Nishant,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Menon, Nishanth
S, Venkatraman had written, on 06/25/2010 09:38 AM, the following:
On Fri, Jun 25, 2010 at 7:25 PM, Nishanth Menon n...@ti.com wrote:
DebBarma, Tarun Kanti had written, on 06/25/2010 08:50 AM, the following:
Nishant,
-Original Message-
From: linux-omap-ow...@vger.kernel.org
On Fri, Jun 25, 2010 at 8:13 PM, Nishanth Menon n...@ti.com wrote:
S, Venkatraman had written, on 06/25/2010 09:38 AM, the following:
On Fri, Jun 25, 2010 at 7:25 PM, Nishanth Menon n...@ti.com wrote:
DebBarma, Tarun Kanti had written, on 06/25/2010 08:50 AM, the following:
Nishant,
On Thu, Jun 24, 2010 at 5:43 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Implement the new runtime PM framework as a thin layer on top of the
omap_device API. Since we don't have an OMAP-specific bus, override
the runtime PM hooks for the platform_bus for the OMAP specific
Pnesh,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Neshama Parhoti
Sent: Friday, June 25, 2010 9:06 AM
To: Ghorai, Sukumar
Cc: linux-omap@vger.kernel.org
Subject: Re: ZOOM2 doesn't boot on upstream kernel
On
Govindraj.R govindraj.r...@ti.com writes:
Leave the uart_list empty and keep the omap hwmod info
in a seperate uart_oh list and if board file calls
serial init use this uart_oh list info to fill uart_list.
The board file can also call just init_port to initialise
a single uart instance, so
S, Venkatraman had written, on 06/25/2010 10:16 AM, the following:
On Fri, Jun 25, 2010 at 8:13 PM, Nishanth Menon n...@ti.com wrote:
S, Venkatraman had written, on 06/25/2010 09:38 AM, the following:
On Fri, Jun 25, 2010 at 7:25 PM, Nishanth Menon n...@ti.com wrote:
DebBarma, Tarun Kanti had
Introduce a single omap generic check_revision that routes the
request to the right revision of check_revision.
Note: OMAP1 and OMAP2+ are not built into a single kernel. This
allows for the headers definitions of omap1_check_revision() and
omap2_check_revision() to be used without #ifdefs and
-Original Message-
From: Menon, Nishanth
Sent: Friday, June 25, 2010 9:55 PM
To: linux-omap
Cc: Tony Lindgren; Menon, Nishanth; Angelo Arrifano; Zebediah C. McClure;
Alistair Buxton; Grazvydas
Ignotas; Paul Walmsley; Premi, Sanjeev; Shilimkar, Santosh; Guruswamy,
Senthilvadivu;
Cousson, Benoit b-cous...@ti.com writes:
On 6/25/2010 1:44 AM, Kevin Hilman wrote:
From: Rajendra Nayakrna...@ti.com
Enable omap_device layer support for OMAP4, so that drivers can
use them to enable/idle/shutdown devices.
Signed-off-by: Rajendra Nayakrna...@ti.com
Signed-off-by: Benoit
Shilimkar, Santosh had written, on 06/25/2010 11:41 AM, the following:
-Original Message-
From: Menon, Nishanth
Sent: Friday, June 25, 2010 9:55 PM
To: linux-omap
Cc: Tony Lindgren; Menon, Nishanth; Angelo Arrifano; Zebediah C. McClure;
Alistair Buxton; Grazvydas
Ignotas; Paul Walmsley;
Grant Likely grant.lik...@secretlab.ca writes:
On Thu, Jun 24, 2010 at 5:43 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Implement the new runtime PM framework as a thin layer on top of the
omap_device API. Since we don't have an OMAP-specific bus, override
the runtime PM hooks for
-Original Message-
From: Menon, Nishanth
Sent: Friday, June 25, 2010 11:02 PM
To: Shilimkar, Santosh
Cc: linux-omap; Tony Lindgren; Angelo Arrifano; Zebediah C. McClure; Alistair
Buxton; Grazvydas
Ignotas; Paul Walmsley; Premi, Sanjeev; Guruswamy, Senthilvadivu; Kevin
Hilman;
Benoit,
Thanks for the comments. My responses are below.
Why using a Kconfig option in that case? You can reserve the locks at
run time based on other driver request. The goal of the hwspinlock is to
protect data shared between various processors inside OMAP4 like ipu,
iva, dsp and mpu. So
From: Sebastien Jan s-...@ti.com
Date: Fri, 25 Jun 2010 16:20:36 +0200
Hi Steve,
Thanks for your answer.
On 06/25/2010 10:43 AM, steve.glendinn...@smsc.com wrote:
[...]
I can see you have a different use case, but I don't think this specific
driver is the place for this logic. I'd
Thara Gopinath th...@ti.com writes:
This patch removes the usage of vdd and sr id alltogether.
This is achieved by introducing a separte voltage domain per
VDD and hooking this up with the voltage and smartreflex
internal info structure. Any user of voltage or smartreflex layer
should call
Shilimkar, Santosh had written, on 06/25/2010 01:07 PM, the following:
-Original Message-
From: Menon, Nishanth
Sent: Friday, June 25, 2010 11:02 PM
[..]
--- a/arch/arm/plat-omap/include/plat/cpu.h
+++ b/arch/arm/plat-omap/include/plat/cpu.h
@@ -431,7 +431,18 @@ IS_OMAP_TYPE(3517,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Que, Simon
Sent: Thursday, June 24, 2010 7:40 PM
To: linux-omap@vger.kernel.org
Cc: Kanigeri, Hari; Ohad Ben-Cohen
Subject: [RFC] omap: hwspinlock: Added hwspinlock driver
Simon,
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Que,
Simon
Sent: Friday, June 25, 2010 6:10 AM
To: linux-omap@vger.kernel.org
Cc: Kanigeri, Hari; Ohad Ben-Cohen
Subject: [RFC] omap: hwspinlock: Added
Thara Gopinath th...@ti.com writes:
This patch removes the usage of vdd and sr id alltogether.
This is achieved by introducing a separte voltage domain per
VDD and hooking this up with the voltage and smartreflex
internal info structure. Any user of voltage or smartreflex layer
should call
On Fri, Jun 25, 2010 at 09:26:43AM -0600, Grant Likely wrote:
This approach is also not multiplatform friendly (cc'ing Eric and
Nicolas who are working on ARM multiplatform). It won't work for
building a kernel that supports, say, both versatile and OMAP.
And I should also point out that
On Fri, Jun 25, 2010 at 12:04 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Grant Likely grant.lik...@secretlab.ca writes:
On Thu, Jun 24, 2010 at 5:43 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Implement the new runtime PM framework as a thin layer on top of the
omap_device
On Fri, Jun 25, 2010 at 2:06 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, Jun 25, 2010 at 09:26:43AM -0600, Grant Likely wrote:
This approach is also not multiplatform friendly (cc'ing Eric and
Nicolas who are working on ARM multiplatform). It won't work for
building a
On Fri, Jun 25, 2010 at 02:13:15PM -0600, Grant Likely wrote:
On Fri, Jun 25, 2010 at 2:06 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, Jun 25, 2010 at 09:26:43AM -0600, Grant Likely wrote:
This approach is also not multiplatform friendly (cc'ing Eric and
Nicolas who
Santosh,
This reservation KCONFIG isn't necessary. HWSPINLOCK IP is not really for
very generic use
but specific usages where you need to protect the data between independent
softwares
running on different masters.
For other Linux only side software even with dual core, kernel spinlock
From: Que, Simon
Sent: Friday, June 25, 2010 8:14 PM
Benoit,
Thanks for the comments. My responses are below.
Why using a Kconfig option in that case? You can reserve the locks at
run time based on other driver request. The goal of the
hwspinlock is to
protect data shared between various
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Friday, June 25, 2010 8:49 PM
Thara Gopinath th...@ti.com writes:
This patch removes the usage of vdd and sr id alltogether.
This is achieved by introducing a separte voltage domain per
VDD and hooking this up with the voltage and
strings in c dont need to be split accross multiple lines with \
. instead they can be put as abc def and it is equivalent to
abc def. fix the same
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
Add unlikely checks to better optimize the rare occurrance of
erroneous conditions.
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/sr_device.c | 15 ---
1 files changed, 8
in the unlikely case that hwmod database is messed up, dont crash
report error and attempt to recover.
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/sr_device.c |6 ++
1 files changed, 6
few more pr_ need cleanup for printing the function name and
not using multiline prints when c allows us to do .
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/voltage.c |7 ---
1 files
pr_xxx family is not informative for debug unless one decides
to grep the code, instead print the function to help debug
easier on the field.
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
More misc cleanups for Sr branch including print cleans, checks etc.
This series probably should be squashed with other patches in pm-sr
branch. note some of these patches address few other comments I had
made in an unrelated patch.
Related comments prior to providing patches:
a) I looked close
sr_dev_init should return error on error conditions
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/sr_device.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git
we dont need to go down the path of enabling/disabling the SR
if we dont need to. do some sanity check and trigger if needed
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/smartreflex.c | 19
Grant Likely grant.lik...@secretlab.ca writes:
On Fri, Jun 25, 2010 at 12:04 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Grant Likely grant.lik...@secretlab.ca writes:
On Thu, Jun 24, 2010 at 5:43 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Implement the new runtime PM
On Fri, Jun 25, 2010 at 3:58 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Grant Likely grant.lik...@secretlab.ca writes:
Yes, I've got patches which merge of_platform_bus_type with the
platform bus. This was an easy decision to make because the
of-specific bits (specifically, matching
Grant Likely grant.lik...@secretlab.ca writes:
Another way to look at the problem is that these runtime
customizations are kind of a property of the parent device (the bus,
not the bus_type). Would it make sense for parent devices to have
runtime ops to perform for each child that is
Thara Gopinath th...@ti.com writes:
This patch changes the pm_db_init from arch initcall to a postcore
initcall. With arch initcall, it is impossible for pm driver that
gets initialized prior to this driver to use one of the
pm debug fs entries during its init. Making it a postcore initcall
On Fri, Jun 25, 2010 at 4:46 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Grant Likely grant.lik...@secretlab.ca writes:
Another way to look at the problem is that these runtime
customizations are kind of a property of the parent device (the bus,
not the bus_type). Would it make sense
Charulatha V ch...@ti.com writes:
This patch implements GPIO as a platform device. Also it
implements OMAP2PLUS specific GPIO as HWMOD FW adapted device.
This patch makes GPIO to use runtime APIs.
GPIO APIs are used in machine_init functions. Hence it is
required to complete GPIO probe
On Fri, 25 Jun 2010, Russell King - ARM Linux wrote:
Does anyone know where we are on the defconfig problem? From what I
can see, it's mostly stalled for the time being, which is not good
news for us.
What looked to be promizing is the work by Uwe Kleine-König according to
the preview he
63 matches
Mail list logo
