Initialization of irqenable, irqstatus registers is the common
operation done in this function for all OMAP platforms, viz. OMAP1,
OMAP2+. The latter _gpio_rmw()'s which supposedly got introduced
wrongly to take care of OMAP2+ platforms were overwriting initially
programmed OMAP1 value breaking
On 04/29/2012 11:35 PM, Russell King - ARM Linux wrote:
Please can someone at TI take a current mainline kernel, build it, and
test out audio support on the 4430SDP - specifically output through the
headset jack into a line input, and report when it works. Thanks.
Try to use my attached aconf
Hi Kevin,
On Fri, Apr 27, 2012 at 01:36:28PM -0700, Kevin Hilman wrote:
Samuel,
Munegowda, Keshava keshava_mgo...@ti.com writes:
On Sun, Apr 22, 2012 at 2:20 PM, Russ Dill russ.d...@ti.com wrote:
On Sun, Apr 22, 2012 at 1:48 AM, Russ Dill russ.d...@ti.com wrote:
'ARM: OMAP3: USB: Fix
The current DPLL code enables and disables autoidle features
without checking whether the autoidle register is available.
Fix this by putting a check for the existence of the autoidle
register in the DPLL data.
With such a check in place, for DPLLs which do not support this
feature, simply
Hi Kevin,
On Fri, Apr 27, 2012 at 1:29 AM, Kevin Hilman khil...@ti.com wrote:
This flag is no longer used since clock init all AM35x devices
is now the same.
Acked-by: Vaibhav Hiremath hvaib...@ti.com
Tested-by: Vaibhav Hiremath hvaib...@ti.com
Signed-off-by: Kevin Hilman khil...@ti.com
Kevin,
On Fri, Apr 27, 2012 at 1:29 AM, Kevin Hilman khil...@ti.com wrote:
The 3505 check is now unused and can be removed.
There are no longer any cpu_is_* checks that depend on specific IP
detection.
Acked-by: Vaibhav Hiremath hvaib...@ti.com
Tested-by: Vaibhav Hiremath hvaib...@ti.com
Op 30 apr. 2012, om 11:07 heeft Jean Pihet het volgende geschreven:
Kevin,
On Fri, Apr 27, 2012 at 1:29 AM, Kevin Hilman khil...@ti.com wrote:
The 3505 check is now unused and can be removed.
There are no longer any cpu_is_* checks that depend on specific IP
detection.
Acked-by:
On Fri, Apr 27, 2012 at 02:01:17PM -0700, Kevin Hilman wrote:
Mark Brown broo...@opensource.wolfsonmicro.com writes:
But presumably these things should integrate somehow - for example,
should devfreq and cpufreq be providing inputs into what AVS is doing,
and if so how?
The way it is
Hi Neil,
As I am supposed to be acting as a maintainer for the drivers/mfd/twl-*,
you can add an ack from me for the twl-core.c part. It looks kind of
okay, even if I would eventually like to remove/fix the ugly regulator
init from twl-core.
Just a question, who is going to merge all this seeing
Hello,
This patch provides hardware NAND BCH ecc support for OMAP3 boards.
It depends on the following patch:
new GPMC BCH api v3 (linux-omap):
http://lists.infradead.org/pipermail/linux-mtd/2012-April/040965.html
This v2 leverages on Mike Dunn's MTD bitflip threshold feature
(5568eb3) in order
Hi,
I am trying to get a working preview from a CMOS
sensor with a CFA bayer pattern.
Does the CCDC_COLPTN register have any effect on
previewer CFA interpolation ?
From my experience it does not. I can set BGGR or GRBG,
but the output is always the same. When doing raw capture,
I get nice
On Fri, 2012-04-27 at 16:15 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
On Tue, 2012-04-24 at 10:07 -0700, Kevin Hilman wrote:
[...]
From 26733dd988ccc9e72355a39e01b2d6e9215a892d Mon Sep 17 00:00:00 2001
From: Tero Kristo t-kri...@ti.com
Date: Mon, 23 Apr 2012
Hi Kevin,
On Fri, 27 Apr 2012, Kevin Hilman wrote:
_enable_module is specific to OMAP4-class SoCs, so rename it to
be consistend with the corresponding _omap4_disable_module.
Signed-off-by: Kevin Hilman khil...@ti.com
I tweaked the commit message here a little bit - please let me know if
Hi Kevin,
On Fri, 27 Apr 2012, Kevin Hilman wrote:
The enable/disable module functions are specific to SoCs with
OMAP4-class PRCM. Rather than use cpu_is* checks at runtime inside
the enable/disable module functions, use cpu_is at init time to
initialize function pointers only for SoCs that
On Fri, 27 Apr 2012, Kevin Hilman wrote:
_omap4_wait_target_disable() is called only from inside
_omap4_disable_module()
which is already protected by SoC specific checks. Remove the cpu_is check
here.
Signed-off-by: Kevin Hilman khil...@ti.com
Looks good to me.
- Paul
--
To
Hi Kevin,
On Fri, 27 Apr 2012, Kevin Hilman wrote:
Rather than using cpu_is* checking at runtime, initialize an SoC specific
function pointer for wait_target_ready().
While here, downgrade the BUG() to a WARN_ON() so it gives a noisy
warning instead of causing a kernel panic.
Hi Kevin,
On Fri, 27 Apr 2012, Kevin Hilman wrote:
Rather than using cpu_is* checking at runtime, initialize SoC specific
function pointers for the various hard reset functions at init time.
Signed-off-by: Kevin Hilman khil...@ti.com
Lots of kerneldoc has been added, and the function
Hi Kevin,
On Fri, 27 Apr 2012, Kevin Hilman wrote:
Rather than use runtime cpu_is* checking inside _init_clkdm, initialize
SoC specific function pointer at init time.
Note that initializing the function pointer oh-init_clkdm pointer
must be done before _init_clocks() is called because it
Hi Kevin,
On Fri, 27 Apr 2012, Kevin Hilman wrote:
This series attempts to remove all the runtime cpu_is* checking in
omap_hwmod.c in favor of using function pointers initialized at init
time.
This series was motivated by the addition of support for the AM335x
series which was done by
Hi,
hi get this at boot on an IGEP board (igep0020), latest linux-omap
master (20 Apr):
[0.047704] WARNING: at fs/sysfs/dir.c:508 sysfs_add_one+0x9c/0xac()
[0.047712] sysfs: cannot create duplicate filename
'/devices/platform/reg-fixed-voltage.0'
[0.047720] Modules linked in:
[
* Russell King - ARM Linux li...@arm.linux.org.uk [120428 09:40]:
On Mon, Apr 23, 2012 at 05:13:30PM -0700, Tony Lindgren wrote:
* Russell King rmk+ker...@arm.linux.org.uk [120423 09:11]:
Add DMA engine support to the OMAP driver. This supplements the
private DMA API implementation
* Santosh Shilimkar santosh.shilim...@ti.com [120430 06:03]:
On Saturday 28 April 2012 01:35 AM, Kevin Hilman wrote:
This series attempts to remove all the runtime cpu_is* checking in
omap_hwmod.c in favor of using function pointers initialized at init
time.
This series was motivated
Hi,
* Enrico ebut...@users.sourceforge.net [120430 08:02]:
Hi,
hi get this at boot on an IGEP board (igep0020), latest linux-omap
master (20 Apr):
[0.047704] WARNING: at fs/sysfs/dir.c:508 sysfs_add_one+0x9c/0xac()
[0.047712] sysfs: cannot create duplicate filename
On Fri, Apr 27, 2012 at 03:25:38PM -0700, Kevin Hilman wrote:
Mark A. Greer mgr...@animalcreek.com writes:
On Thu, Apr 26, 2012 at 04:29:45PM -0700, Kevin Hilman wrote:
Hi Kevin.
This is a rebased version of this series which is ready for broader
testing. I'd especially appreciate
On Sat, Apr 28, 2012 at 03:20:48PM -0500, Derald D. Woods wrote:
Is there a kernel config
that is commonly used by those testing the AM3517? or modified
omap2plus? I think some issues that I am seeing involve wrong
configuration assumptions by me.
I'm using omap2plus_defconfig with
On Sun, Apr 29, 2012 at 09:48:26AM +, Hiremath, Vaibhav wrote:
On Sun, Apr 29, 2012 at 01:50:48, Derald D. Woods wrote:
On Fri, Apr 27, 2012 at 03:25:38PM -0700, Kevin Hilman wrote:
Hello Kevin,
I have a Logic PD AM3517 Zoom Experimenter [SOMAM3517-10-1780RJXR-C (REV
A)].
On Mon, Apr 30, 2012 at 6:11 PM, Tony Lindgren t...@atomide.com wrote:
Hi,
* Enrico ebut...@users.sourceforge.net [120430 08:02]:
Hi,
hi get this at boot on an IGEP board (igep0020), latest linux-omap
master (20 Apr):
[ 0.047704] WARNING: at fs/sysfs/dir.c:508 sysfs_add_one+0x9c/0xac()
On Wed, Apr 25, 2012 at 10:00 AM, Enric Balletbò i Serra
eballe...@gmail.com wrote:
2012/4/4 Javier Martinez Canillas jav...@dowhile0.org:
IGEP-based boards can have two different flash memories, a OneNAND or
a NAND device. The boot configuration pins (sys_boot) are used to
specify which
Paul Walmsley p...@pwsan.com writes:
Hi Kevin,
On Fri, 27 Apr 2012, Kevin Hilman wrote:
_enable_module is specific to OMAP4-class SoCs, so rename it to
be consistend with the corresponding _omap4_disable_module.
Signed-off-by: Kevin Hilman khil...@ti.com
I tweaked the commit message
Jean Pihet jean.pi...@newoldbits.com writes:
Hi Kevin,
On Fri, Apr 27, 2012 at 1:29 AM, Kevin Hilman khil...@ti.com wrote:
This flag is no longer used since clock init all AM35x devices
is now the same.
Acked-by: Vaibhav Hiremath hvaib...@ti.com
Tested-by: Vaibhav Hiremath hvaib...@ti.com
From: Enrico Butera ebut...@users.berlios.de
Using id 0 causes errors at boot:
WARNING: at fs/sysfs/dir.c:508 sysfs_add_one+0x9c/0xac()
sysfs: cannot create duplicate filename '/devices/platform/reg-fixed-voltage.0'
Fix it by using a random (not-already-used) id, as suggested
by Tony Lindgren.
Jean Pihet jean.pi...@newoldbits.com writes:
Kevin,
On Fri, Apr 27, 2012 at 1:29 AM, Kevin Hilman khil...@ti.com wrote:
The 3505 check is now unused and can be removed.
There are no longer any cpu_is_* checks that depend on specific IP
detection.
Acked-by: Vaibhav Hiremath
Commit 384ebe1c2849160d040df3e68634ec506f13d9ff, gpio/omap: Add DT
support to GPIO driver, introduced dynamic IRQ numbering of OMAP GPIO
interrupts, breaking all IH_GPIO_BASE based IRQ number calculations.
This issue was corrected in the OMAP GPIO driver and the related header
file with commit
Dnia czwartek, 26 kwietnia 2012 08:20:59 Artem Bityutskiy pisze:
On Wed, 2012-04-25 at 19:01 +0200, Janusz Krzysztofik wrote:
Both drivers use separate subsets of registers that belong to the
OMAP1
MPU I/O device, but are used for controlling different sets of I/O
pins.
The NAND driver
Hola,
What is the latest version of the Linux kernel OMAP tree that is considered
stable? I'm in the middle of bringing up a bare-metal roll of Linux on a
derivative of the AM3517 family (Jacinto 3) on a commercial automotive radio.
I'm new to Linux on OMAP but old to Linux kernel
On Sat, Apr 28, 2012 at 06:06:40, Paul Walmsley wrote:
Hi Vaibhav
On Wed, 21 Mar 2012, Vaibhav Hiremath wrote:
Define AM33XX control register, in order to allow access to
control register address space, also add CONTROL_SEC_CLK_CTRL
register offset; both are required in clock tree
On Sat, Apr 28, 2012 at 05:34:53, Paul Walmsley wrote:
On Fri, 27 Apr 2012, Hiremath, Vaibhav wrote:
On Thu, Apr 26, 2012 at 14:19:28, Paul Walmsley wrote:
looking at Table 1-1 Device Features of SPRUH73D, it seems that some
AM33xx family chips come with some features disabled, such as
Hi,
* a...@alanlee.org a...@alanlee.org [120430 11:24]:
What is the latest version of the Linux kernel OMAP tree that is considered
stable? I'm in the middle of bringing up a bare-metal roll of Linux on a
derivative of the AM3517 family (Jacinto 3) on a commercial automotive radio.
I'm
Tero Kristo t-kri...@ti.com writes:
On Fri, 2012-04-27 at 16:15 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
On Tue, 2012-04-24 at 10:07 -0700, Kevin Hilman wrote:
[...]
From 26733dd988ccc9e72355a39e01b2d6e9215a892d Mon Sep 17 00:00:00 2001
From: Tero Kristo
Paul Walmsley p...@pwsan.com writes:
Hi Vaibhav, Kevin,
On Fri, 30 Mar 2012, Vaibhav Hiremath wrote:
Currently dummy voltage domain data is being created
in order to succeed boot process, nothing has been done
w.r.t actual hardware (voltage control).
Also, hook up the AM33XX voltage
Grazvydas Ignotas nota...@gmail.com writes:
On Tue, Apr 24, 2012 at 5:23 PM, Kevin Hilman khil...@ti.com wrote:
commit e7410cf7 (02fdb03e69699f26e1370d0e51593dbc8a4e5265) moved
mangement of cam_pwrdm to CPUidle but left some remnants behind,
namely the call to clkcm_allo_idle() for the
Mark A. Greer mgr...@animalcreek.com writes:
On Fri, Apr 27, 2012 at 03:25:38PM -0700, Kevin Hilman wrote:
Mark A. Greer mgr...@animalcreek.com writes:
On Thu, Apr 26, 2012 at 04:29:45PM -0700, Kevin Hilman wrote:
Hi Kevin.
This is a rebased version of this series which is ready for
From: Jon Hunter jon-hun...@ti.com
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
[1] http://article.gmane.org/gmane.linux.drivers.devicetree/12022
[2]
From: Jon Hunter jon-hun...@ti.com
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
Aim of DMA helpers
- The purpose of device-tree (as far as I understand), is to
From: Jon Hunter jon-hun...@ti.com
These selftests are covering the new DT DMA helpers for both legacy controllers
(not supporting DMA Engine) and controllers supporting DMA Engine. They will
test both error and normal cases.
A dummy DMA engine filter function is also provided to show how this
From: Mark A. Greer mgr...@animalcreek.com
Some parts of the OMAP code assume that all power
domains support certain states (e.g., RET OFF).
This isn't always true (e.g., the am35x family of
SoC's) so those assumptions need to be removed.
Remove those assumptions by looking up the deepest
state
From: Mark A. Greer mgr...@animalcreek.com
The am35x family of SoCs only support the PWRSTS_ON
state so create a new set of powerdomain structures
that ensure that only the ON state is entered.
Signed-off-by: Mark A. Greer mgr...@animalcreek.com
---
These patches apply on top of Kevin's patch
On Fri, Apr 27, 2012 at 02:12:12PM -0700, Kevin Hilman wrote:
Mark A. Greer mgr...@animalcreek.com writes:
On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
Just thinking out loud...
We could chose whether pm_idle cpuidle issue a wfi based on
whether there is a
Mark Brown broo...@opensource.wolfsonmicro.com writes:
On Fri, Apr 27, 2012 at 02:01:17PM -0700, Kevin Hilman wrote:
Mark Brown broo...@opensource.wolfsonmicro.com writes:
But presumably these things should integrate somehow - for example,
should devfreq and cpufreq be providing inputs
Mark A. Greer mgr...@animalcreek.com writes:
On Fri, Apr 27, 2012 at 02:12:12PM -0700, Kevin Hilman wrote:
Mark A. Greer mgr...@animalcreek.com writes:
On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
Just thinking out loud...
We could chose whether pm_idle cpuidle
On Fri, Apr 27, 2012 at 02:07:13PM -0700, Kevin Hilman wrote:
Mark A. Greer mgr...@animalcreek.com writes:
On Wed, Apr 11, 2012 at 03:46:20PM -0700, Kevin Hilman wrote:
Hi Mark,
Hi Kevin.
Mark A. Greer mgr...@animalcreek.com writes:
From: Mark A. Greer mgr...@animalcreek.com
On Mon, Apr 30, 2012 at 03:00:56PM -0700, Kevin Hilman wrote:
Mark A. Greer mgr...@animalcreek.com writes:
On Fri, Apr 27, 2012 at 02:12:12PM -0700, Kevin Hilman wrote:
Mark A. Greer mgr...@animalcreek.com writes:
On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
Hi Will,
Will Deacon will.dea...@arm.com writes:
On Wed, Apr 04, 2012 at 12:15:24PM +0100, Will Deacon wrote:
On Wed, Apr 04, 2012 at 12:29:49AM +0100, Paul Walmsley wrote:
Part of the problem is that the clockdomain data for the emu_sys
clockdomain is wrong. Here's something to try
Daniel Lezcano daniel.lezc...@linaro.org writes:
On 04/24/2012 04:05 PM, Daniel Lezcano wrote:
This patchset makes some cleanup on these cpuidle drivers
and consolidate the code across both architecture.
Tested on OMAP3 (igepV2).
Partially tested on OMAP4 (pandaboard), without offlining the
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Remove the following functions from the OMAP PM API:
omap_pm_set_max_mpu_wakeup_lat
omap_pm_set_max_dev_wakeup_lat
omap_pm_set_max_sdma_lat
and updated the kernel Documentation accordingly.
The generic per-device PM QoS
On Mon, Apr 30, 2012 at 12:44:17PM -0700, Tony Lindgren wrote:
Hi,
* a...@alanlee.org a...@alanlee.org [120430 11:24]:
What is the latest version of the Linux kernel OMAP tree that is considered
stable? I'm in the middle of bringing up a bare-metal roll of Linux on a
derivative of
Hi Jean,
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
. Implement the devices wake-up latency constraints using the global
device PM QoS notification handler which applies the constraints to the
underlying layer,
. Implement the low level code which controls the
Remove all AM35xx specifics from the clock tree and tree and treat all
AM35xx devices the same.
Kevin Hilman (2):
ARM: OMAP3: clock data: replace 3503/3517 flag with AM35x flag for
UART4
ARM: OMAP3: clock data: treat all AM35x devices the same
Paul Walmsley (1):
ARM: OMAP: clock:
The AM35x UART4 is common to all AM35x devices, so use CK_AM35XX instead
of (CK_3505 | CK_3517), which is equivalent.
Acked-by: Vaibhav Hiremath hvaib...@ti.com
Tested-by: Vaibhav Hiremath hvaib...@ti.com
Signed-off-by: Kevin Hilman khil...@ti.com
[p...@pwsan.com: also fixed AM35xx UART4
The init for 3505/3517 specific clocks depends on the ordering of
cpu_is checks, is error prone and confusing (there are 2 separate
checks for cpu_is_omap3505()).
Remove the 3505-specific checking since CK_3505 flag is not used, and
treat all AM35x clocks the same.
This means that the SGX clock
From: Paul Walmsley p...@pwsan.com
To improve the clarity of the code, replace the CK_3517 flag used in
the clock data with CK_AM35XX. The CK_3505 flag can also be
removed, since it is now unused.
Acked-by: Vaibhav Hiremath hvaib...@ti.com
Signed-off-by: Kevin Hilman khil...@ti.com
The detection of AM35xx SoCs is confusing and has redundancies. Clean
this up so that SoC detection is only based on SoC family: AM35xx.
Kevin Hilman (2):
ARM: OMAP: AM35xx: remove redunant cpu_is checks for AM3505
ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx
There are several checks for AM35x devices done using
if (cpu_is_omap3517() || cpu_is_omap3505())
However, since the 3505 is just a 3517 without an SGX, the 3505 check
is redundant because cpu_is_omap3517() will always be true whenever
cpu_is_omap3505() is true. From plat/cpu.h:
#define
Currently cpu_is_omap3517() actually detects any device in the AM35x
family (3517 and no-SGX version 3505.) To make it more clear what is
being detected, convert the names from 3517 to AM35xx.
This adds a new cpu_is_am35xx() which duplicates the cpu_is_omap3517().
In order to avoid cross-tree
On Mon, 30 Apr 2012, Kevin Hilman wrote:
From: Paul Walmsley p...@pwsan.com
Looks good to me but I think you created this patch, right? :-)
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info
Kevin Hilman khil...@ti.com writes:
This is a rebased version of this series which is ready for broader
testing. I'd especially appreciate testing from those of you with
AM35x platforms.
Currently, our SoC detection is based on SoC family detection
(using die ID) and the presence of
From: Mark A. Greer mgr...@animalcreek.com
The Chip Identification register on the am35x family of SoCs
has bits 12, 7:5, and 3:2 marked as reserved and are read as
zeroes. Unfortunately, on other omap SoCs, a 0 bit means a
feature is Full Use so the OMAP3_CHECK_FEATURE() macro
called by
Paul Walmsley p...@pwsan.com writes:
On Mon, 30 Apr 2012, Kevin Hilman wrote:
From: Paul Walmsley p...@pwsan.com
Looks good to me but I think you created this patch, right? :-)
er, yeah.
Seems the combined version I pulled from your temporary branch had your
authorship (maybe because of
On Mon, 30 Apr 2012 13:14:32 +0300 Tero Kristo t-kri...@ti.com wrote:
Hi Neil,
As I am supposed to be acting as a maintainer for the drivers/mfd/twl-*,
you can add an ack from me for the twl-core.c part. It looks kind of
okay, even if I would eventually like to remove/fix the ugly regulator
69 matches
Mail list logo
