Hi Tomi,
On Thu, Mar 1, 2012 at 5:01 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Hi,
On Thu, 2012-03-01 at 13:44 +0530, mythr...@ti.com wrote:
From: Mythri P K mythr...@ti.com
Currently TX_PHY is put to TX_ON(transmission state) on receiving HPD.
It just ensures that the TV is
Hi Tony,
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
Hi all,
This series adds gpio_find_by_name() that allows finding
GPIOs on specific gpio_chips. As the GPIO numbers can be
dynamic, it's hard to find the GPIO numbers from drivers
using them directly.
So far we've dealt with this
On Fri, Mar 2, 2012 at 12:41 PM, S, Venkatraman svenk...@ti.com wrote:
+Chris queues all MMC patches including omap_hsmmc.
Ping ?
Just realized that it's already queued in mmc-next
http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commitdiff;h=25d6ba8171995230b3757c78c7470fa76a931b98
On Thu, 2012-03-01 at 14:37 -0800, Kevin Hilman wrote:
Rajendra Nayak rna...@ti.com writes:
On Wednesday 29 February 2012 07:56 PM, Tero Kristo wrote:
From: Vishwanath BSvishwanath...@ti.com
Enable IO Wake up for OMAP3 as part of PM Init. Currently this has been
managed in cpuidle
On Thu, Mar 01, 2012 at 04:02:19PM -0800, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [120223 00:15]:
Hi,
On Wed, Feb 22, 2012 at 02:09:37PM -0800, Tony Lindgren wrote:
From 54c4785b8d274f8d282b4243945ae0b17edf4686 Mon Sep 17 00:00:00 2001
From: Tony Lindgren t...@atomide.com
On Friday 02 March 2012 02:49 PM, Tero Kristo wrote:
On Thu, 2012-03-01 at 14:37 -0800, Kevin Hilman wrote:
Rajendra Nayakrna...@ti.com writes:
On Wednesday 29 February 2012 07:56 PM, Tero Kristo wrote:
From: Vishwanath BSvishwanath...@ti.com
Enable IO Wake up for OMAP3 as part of PM Init.
On Thu, 01 Mar 2012 10:55:24 -0800, Tony Lindgren t...@atomide.com wrote:
Currently there is no way for drivers to request a GPIO on a particular
gpio chip. This makes it hard to support multiple GPIO controllers
with dynamic GPIO and interrupt numbering, such as with CONFIG_SPARSE_IRQ.
Make
Hi Tony,
On Thu, Mar 01, 2012 at 10:55:35AM -0800, Tony Lindgren wrote:
There's no need to use callbacks for this, we can
do it directly between MMC driver and twl6030.
Cc: Samuel Ortiz sa...@linux.intel.com
Acked-by: Samuel Ortiz sa...@linux.intel.com
Cheers,
Samuel.
--
Intel Open Source
On Thu, 2012-03-01 at 14:07 -0800, Kevin Hilman wrote:
+Tero
Kevin Hilman khil...@ti.com writes:
Afzal Mohammed af...@ti.com writes:
Specify voltage in ranges for regulator. Range
used is tolerance specified for OPP.
This helps to achieve DVFS with a wider range of
regulators.
Hi
On Fri, 2 Mar 2012, Hiremath, Vaibhav wrote:
Paul,
Thanks for your review comments, can we also align on the approach,
Whether to merge am33xx powerdomain with omap4 (same direction we are now)
OR
Have separate implementation (my original approach).
Could you please take a look at the
Hi
On Fri, 3 Feb 2012, Vaibhav Hiremath wrote:
AM33xx PRM module is closer to OMAP4 PRM module, and
in order to reuse prminst api's we have to address
some of the differences like, base addresses and partitions.
Unlike OMAP4 PRM, AM33xx doesn't have any partitions and
maintains single
On Fri, 2012-03-02 at 13:35 +0530, K, Mythri P wrote:
Hi Tomi,
On Thu, Mar 1, 2012 at 5:01 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Hi,
On Thu, 2012-03-01 at 13:44 +0530, mythr...@ti.com wrote:
From: Mythri P K mythr...@ti.com
Currently TX_PHY is put to TX_ON(transmission
Hi Kevin,
On Fri, Mar 02, 2012 at 03:37:51, Hilman, Kevin wrote:
Thanks, will queue this with the CPUfreq changes for MPU DVFS.
Actually, not quite yet...
After some testing with the SMPS regulators, this won't quite work with
the current SMPS regulators. Does this actually work with
While building modules with randconfig the below errors are observed.
ERROR: omap_bus_sync [drivers/watchdog/sp805_wdt.ko] undefined!
ERROR: omap_bus_sync [drivers/watchdog/dw_wdt.ko] undefined!
ERROR: omap_bus_sync [drivers/virtio/virtio_ring.ko] undefined!
ERROR: omap_bus_sync
Hi Tomi,
Damage never happens with the cable connected for a long time.. Damage
happens only
when the cable is connected when the PHY is in TX ON state. Which
requires the following sequence to be followed.
1. Wait for HPD connect
2. Wait for the PHY connect ( TMDS lines are up)
3. Enable
On Fri, 2012-03-02 at 16:55 +0530, K, Mythri P wrote:
Hi Tomi,
Damage never happens with the cable connected for a long time.. Damage
happens only
when the cable is connected when the PHY is in TX ON state. Which
requires the following sequence to be followed.
1. Wait for HPD connect
On Thu, Mar 1, 2012 at 9:55 PM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120301 00:38]:
On Wed, Feb 29, 2012 at 11:07 PM, Tony Lindgren t...@atomide.com wrote:
Hi Santosh,
Looks like OMAP4_ERRATA_I688 still has one more issue:
Modules won't
Hi,
On Tue, Feb 28, 2012 at 03:09:10PM +0530, Rajendra Nayak wrote:
From: Tero Kristo t-kri...@ti.com
vdd1 and vdd2 are now common regulators for twl4030 and twl6030. Also
added vdd3 as a new regulator for twl6030. twl6030 vdd1...vdd3 smps
regulator voltages can only be controlled through
On Fri, Feb 24, 2012 at 5:14 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Fri, Feb 24, 2012 at 3:46 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Fri, Feb 24, 2012 at 03:36:15PM +0530, Keshava Munegowda wrote:
From: Keshava Munegowda keshava_mgo...@ti.com
It is observed that the
Hi Mark,
On 02/28/2012 12:49 PM, Mark Brown wrote:
On Tue, Feb 28, 2012 at 09:40:10AM +0200, Peter Ujfalusi wrote:
NOTE: this series has been generated agains Takashi's topic/asoc branch
merged
with Mark's for-next branch since this series depends on changes in Marks'
branch, but not yet
On Fri, Mar 02, 2012 at 02:53:35PM +0100, Samuel Ortiz wrote:
Mark, Liam, are you guys taking this one ?
Yes.
signature.asc
Description: Digital signature
Hi,
Changes compared to previous version:
- patch2:
* changed timeout value to 100us (from 1000)
* added poll for the IO status == 0 at the end of trigger sequence
- patch4:
* omap3: global wakeup done in PRM init instead of OMAP3 PM init
* omap4: moved global wakeup enable from trigger func
From: Mohan V moh...@ti.com
Currently the enabling and disabling of IO Daisy chain is not
according to the TRM. The below steps are followed to enable/
disable the IO chain according to the Sec 3.5.7.2.2
I/O Wake-Up Mechanism in OMAP3630 Public TRM[1].
Steps to enable IO chain:
[a] Set
From: Vishwanath BS vishwanath...@ti.com
Since IO Daisychain modifies only PRM registers, it makes sense to move
it to PRM File. Also changed the timeout value for IO chain enable to
100us and added a wait for status disable at the end.
Signed-off-by: Vishwanath BS vishwanath...@ti.com
From: Rajendra Nayak rna...@ti.com
IO daisychain is a mechanism that allows individual IO pads to generate
wakeup events on their own based on a switch of an input signal level.
This allows the hardware module behind the pad to be powered down, but
still have device level capability to detect IO
Enable IO Wake up for OMAP3/4 as part of PRM Init. Currently this has been
managed in cpuidle path which is not the right place. Subsequent patch
will remove IO Daisy chain handling in cpuidle path once daisy chain is
handled as part of hwmod mux. This patch also moves the OMAP4 IO wakeup
enable
From: Vishwanath BS vishwanath...@ti.com
As IO Daisy chain sequence is triggered via hwmod mux, there is no need to
control it from cpuidle path for OMAP3.
Also as omap3_disable_io_chain is no longer being used, just remove the
function.
Signed-off-by: Vishwanath BS vishwanath...@ti.com
From: Vishwanath BS vishwanath...@ti.com
IO Daisychain feature has to be triggered whenever there is a change in
device's mux configuration (See section 3.9.4 in OMAP4 Public TRM vP).
Now devices can idle independent of the powerdomain, there can be a
window where device is idled and
Hi,
When running the mtd_subpagetest I'm seeing more or less spurious ECC
corrections. I.e., one round may show 4 corrections and the next will
show 7, only some of which are the same as the previous 4.
Are the ECC errors expected to be that volatile and frequent?
I've seen various
On 03/02/2012 05:17 PM, Orjan Friberg wrote:
Hi,
When running the mtd_subpagetest I'm seeing more or less spurious ECC
corrections. I.e., one round may show 4 corrections and the next will
show 7, only some of which are the same as the previous 4.
FWIW
* I'm seeing the same behaviour (i.e.
Hi Samuel and Tony,
Here is a fix + cleanup + SPARSE_IRQ series for TWL4030 and TWL6030.
The first goal was to fix the current regression due to irqdomain
support inside twl-core for OMAP3 + twl4030.
The issue is that there is no quick and dirty fix for that, hence this
exhaustive series
From: Felipe Balbi ba...@ti.com
With sparse IRQs the driver shouldn't depend at all on
any IRQ values coming from board-file.
Remove every occurences of pdata-irq_base/end.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Benoit Cousson b-cous...@ti.com
---
drivers/mfd/twl-core.c | 49
From: Felipe Balbi ba...@ti.com
This driver doesn't really need plat/cpu.h, so remove it.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/twl-core.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/twl-core.c b/drivers/mfd/twl-core.c
index
The twl-core exported functions are already declared in twl-core.h
Include the header file instead or re-declaring the functions.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/twl-core.c |7 ++-
1 files changed, 2 insertions(+), 5
twl4030 is using a two level irq controllers infrastruture.
So far, only the first level was using dynamic irq_desc allocation
to be able to have irq_domain support for device tree.
There is a need to allocate separate irq_descs for the SIH too to
avoid hacking the first level with interrupts from
During DT adaptation, the irq_alloc_desc was added into twl-core, but
due to the rather different and weird IRQ management required by the twl4030,
it is much better to have a different approach for it.
The issue is that twl4030 uses a two level IRQ mechanism but handles all the
PWR interrupts as
Add the DT support for the I2C GPIO expander inside the twl4030.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
---
.../devicetree/bindings/gpio/gpio-twl4030.txt | 23 ++
drivers/gpio/gpio-twl4030.c| 79 ---
Add the twl-gpio node inside twl4030 definition.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Felipe Balbi ba...@ti.com
---
arch/arm/boot/dts/twl4030.dtsi |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/twl4030.dtsi
Card detect IRQ from the TWL6030 used to be provided to the MMC
controller code using a statically allocated IRQ scheme:
card_detect_irq = TWL6030_IRQ_BASE + MMCDETECT_INTR_OFFSET;
This is no longer valid in a SPARSE_IRQ context since there is no more
pre-defined TWL6030_IRQ_BASE.
Return the
With the introduction of dynamically allocated IRQ in the twl6030 driver,
the board files can no longer rely of static IRQ defines like before.
Retrieve the value dynamically allocated from the mmc - twl6030 init
callback.
Note: The Panda board does not seems to use the card detect IRQ.
Do not use the board pdata for irq_base, but allocate them dynamically
to allow a proper support of SPARSE_IRQ.
Fix an unneeded line wrap.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
---
drivers/gpio/gpio-twl4030.c | 33 +
From: Felipe Balbi ba...@ti.com
__ffs() will be far faster than the for loop used.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/twl4030-irq.c | 14 +++---
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/mfd/twl4030-irq.c b/drivers/mfd/twl4030-irq.c
Hi,
Correcting a typo in the LKML address..
* Grant Likely grant.lik...@secretlab.ca [120302 01:00]:
On Thu, 01 Mar 2012 10:55:24 -0800, Tony Lindgren t...@atomide.com wrote:
Currently there is no way for drivers to request a GPIO on a particular
gpio chip. This makes it hard to support
* Rajendra Nayak rna...@ti.com [120301 21:23]:
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
Use gpio_find_by_chip_name() to find the GPIO pins as they can
be dynamically allocated on various gpio_chips.
Note that we don't want to touch the platform data as it can
now specify the
* Rajendra Nayak rna...@ti.com [120301 22:54]:
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
+if (slot-gpiochip_cd) {
+pr_warning(MMC %s card detect GPIO chip %s
unavailable\n,
+slot-name, slot-gpiochip_cd);
+
* Rajendra Nayak rna...@ti.com [120301 21:31]:
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
--- a/arch/arm/mach-omap2/board-3430sdp.c
+++ b/arch/arm/mach-omap2/board-3430sdp.c
@@ -231,14 +231,16 @@ static struct omap2_hsmmc_info mmc[] = {
* so the SIM card isn't used;
Hello,
On Fri, Mar 2, 2012 at 6:17 PM, Orjan Friberg o...@flatfrog.com wrote:
When running the mtd_subpagetest I'm seeing more or less spurious ECC
corrections. I.e., one round may show 4 corrections and the next will show
7, only some of which are the same as the previous 4.
Are the ECC
* Rajendra Nayak rna...@ti.com [120301 21:38]:
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
--- a/arch/arm/mach-omap2/board-omap4panda.c
+++ b/arch/arm/mach-omap2/board-omap4panda.c
@@ -153,8 +153,8 @@ static struct omap2_hsmmc_info mmc[] = {
{
.mmc=
On Thu, 1 Mar 2012 15:31:01 Tony Lindgren wrote:
I've pushed ams-delta branch that's based on -rc5 merged
with what Arnd pulled yesterday as -rc1 has i2c-omap.c
a compile bug for omap1. I've applied these two patches
there as the second one depends on what got pulled:
ARM: OMAP1:
* Rajendra Nayak rna...@ti.com [120302 00:35]:
Hi Tony,
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
Hi all,
This series adds gpio_find_by_name() that allows finding
GPIOs on specific gpio_chips. As the GPIO numbers can be
dynamic, it's hard to find the GPIO numbers from
* Shilimkar, Santosh santosh.shilim...@ti.com [120302 03:15]:
On Thu, Mar 1, 2012 at 9:55 PM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120301 00:38]:
On Wed, Feb 29, 2012 at 11:07 PM, Tony Lindgren t...@atomide.com wrote:
Hi Santosh,
Looks
* Tony Lindgren t...@atomide.com [120302 08:31]:
* Grant Likely grant.lik...@secretlab.ca [120302 01:00]:
On Thu, 01 Mar 2012 10:55:24 -0800, Tony Lindgren t...@atomide.com wrote:
+
+/**
+ * gpiochip_find_by_name() - iterator for locating a gpio_chip by name
+ * @name: name of the
Hi,
On Fri, Mar 02, 2012 at 05:50:23PM +0100, Benoit Cousson wrote:
Card detect IRQ from the TWL6030 used to be provided to the MMC
controller code using a statically allocated IRQ scheme:
card_detect_irq = TWL6030_IRQ_BASE + MMCDETECT_INTR_OFFSET;
This is no longer valid in a
* Tony Lindgren t...@atomide.com [120302 08:38]:
* Rajendra Nayak rna...@ti.com [120301 22:54]:
@@ -2093,8 +2123,7 @@ err1:
platform_set_drvdata(pdev, NULL);
mmc_free_host(mmc);
err_alloc:
- omap_hsmmc_gpio_free(pdata);
-err:
+ omap_hsmmc_gpio_free(host);
This error
On Fri, 2 Mar 2012 10:08:48 -0800, Tony Lindgren t...@atomide.com wrote:
* Tony Lindgren t...@atomide.com [120302 08:31]:
* Grant Likely grant.lik...@secretlab.ca [120302 01:00]:
On Thu, 01 Mar 2012 10:55:24 -0800, Tony Lindgren t...@atomide.com
wrote:
+
+/**
+ *
* Grant Likely grant.lik...@secretlab.ca [120302 10:16]:
On Fri, 2 Mar 2012 10:08:48 -0800, Tony Lindgren t...@atomide.com wrote:
* Tony Lindgren t...@atomide.com [120302 08:31]:
* Grant Likely grant.lik...@secretlab.ca [120302 01:00]:
On Thu, 01 Mar 2012 10:55:24 -0800, Tony Lindgren
* Felipe Balbi ba...@ti.com [120302 09:43]:
Hi,
On Fri, Mar 02, 2012 at 05:50:23PM +0100, Benoit Cousson wrote:
Card detect IRQ from the TWL6030 used to be provided to the MMC
controller code using a statically allocated IRQ scheme:
card_detect_irq = TWL6030_IRQ_BASE +
Hi Tony,
On 3/2/2012 8:20 PM, Tony Lindgren wrote:
* Felipe Balbiba...@ti.com [120302 09:43]:
Hi,
On Fri, Mar 02, 2012 at 05:50:23PM +0100, Benoit Cousson wrote:
Card detect IRQ from the TWL6030 used to be provided to the MMC
controller code using a statically allocated IRQ scheme:
Since a structure device is available now, use the dev_ macros instead
of the pr_ ones.
Clean some badly formatted comments.
Remove some unused variables.
Move some variable to the place they belong.
Clean some badly wrapped lines.
Align variable definition
Add missing braces in if-then-else
For people who were really impatient to get that patch #7, here is the
reason it was rejected...
vger.kernel.org #vger.kernel.org #5.7.1 SMTP; 550 5.7.1 Content-Policy
reject msg: The capital Triple-X in subject is way too often associated
with junk email, please rephrase. BF:H 0;
On 3/2/2012 9:28 PM, Cousson, Benoit wrote:
Hi Tony,
On 3/2/2012 8:20 PM, Tony Lindgren wrote:
* Felipe Balbiba...@ti.com [120302 09:43]:
Hi,
On Fri, Mar 02, 2012 at 05:50:23PM +0100, Benoit Cousson wrote:
Card detect IRQ from the TWL6030 used to be provided to the MMC
controller code using
* Cousson, Benoit b-cous...@ti.com [120302 13:06]:
I created a for_3.4/twl_irq_gpio_fix branch based on irqdomain/next
with all the TWL + GPIO patches except the DTS and without the MMC
hacks.
And I merged it into your hsmmc-gpio branch. There is a small
conflict in gpio-twl4030 but
+Nishanth
Tero Kristo t-kri...@ti.com writes:
On Thu, 2012-03-01 at 14:07 -0800, Kevin Hilman wrote:
+Tero
Kevin Hilman khil...@ti.com writes:
Afzal Mohammed af...@ti.com writes:
Specify voltage in ranges for regulator. Range
used is tolerance specified for OPP.
This helps to
When using the SMPS regulators to scale voltages, the regulator
framework may pass a minimum voltage that is not an exact OPP voltage.
For the VC/VP controlled voltage domains, we must ensure that the
voltage requested is the exact voltage from the OPP table. This is
especially critical when
Hi Tony,
On 3/1/2012 19:10, Jon Hunter wrote:
From: Jon Hunterjon-hun...@ti.com
I recently noticed there are a couple bugs in the OMAP2-PLUS DMA driver code.
1. The CCDN DMA register is valid for all OMAP devices from OMAP3630 onwards.
For OMAP3630+ devices the CCDN register is the upper
65 matches
Mail list logo
