Hi all
While testing audio capture (using arecord e,g.),I'm getting only noise in the
(zeroed out) output buffers on the OMAP3 EVM.
I have enabled AUXL and AUXR mic inputs through alsamixer, which according to
the schematics are connected to the Audio In
connector on the board, even though the
Thanks Peter,
Your comment helped.
-Original Message-
From: Peter Ujfalusi [mailto:peter.ujfal...@nokia.com]
Sent: Friday, January 21, 2011 1:27 PM
To: Koyamangalath, Abhilash
Cc: linux-omap@vger.kernel.org; alsa-de...@vger.kernel.org
Subject: Re: [QUERY] [AUDIO][OMAP3 EVM] arecord
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Gulati, Shweta
Sent: Monday, January 24, 2011 11:07 AM
To: linux-omap@vger.kernel.org
Cc: Gopinath, Thara; Gulati, Shweta
Subject: [PATCH V2] OMAP3: PM: Set/reset T2 bit
On Tue, Aug 30, 2011 Laurent Pinchart wrote:
Hi,
On Wednesday 10 August 2011 16:03:12 Deepthy Ravi wrote:
From: Abhilash K V abhilash...@ti.com
While resuming from the suspended to memory state,
occasionally CCDC fails to get enabled and thus fails
to capture frames any more till the
hi
On the am35x, I can see that resumption (after a suspend command was issued)
from ram using the serial console
hangs without any messages, ONLY when I use no_console_suspend in boot-args.
The last message I see is this :
Disabling non-boot CPUs ...\n
Using logs I can
Hi
On Wed, Aug 31, 2011 at 4:28 AM, Hilman, Kevin wrote:
Abhilash K V abhilash...@ti.com writes:
1. Patch to disable dynamic sleep (as it is not supported
on AM35xx).
2. Imported the unique suspend/resume sequence for AM3517,
contained in the new file arch/arm/mach-omap2/sleep3517.S.
hi Kevin
On Tue, Sep 13, 2011 at 11:54 PM, Hilman, Kevin wrote:
Hi Abhilash,
Koyamangalath, Abhilash abhilash...@ti.com writes:
Hi
On Wed, Aug 31, 2011 at 4:28 AM, Hilman, Kevin wrote:
Abhilash K V abhilash...@ti.com writes:
snip
In addition to Russell's comments about using
Hi Paul
On Wed, Sep 14, 2011 at 7:21 PM, Premi, Sanjeev wrote:
-Original Message-
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Wednesday, September 14, 2011 7:19 PM
To: Premi, Sanjeev
Cc: nota...@gmail.com; t...@atomide.com; Igor
())
+ voltdm-scalable = false;
voltdm-sys_clk.name = sys_clk_name;
+ }
voltdm_init(voltagedomains_omap3);
};
From: Hilman, Kevin
Sent: Friday, September 23, 2011 4:00 AM
To: Koyamangalath, Abhilash
Cc: linux
hi Kevin,
On Fri, Sep 23, 2011 at 3:05 PM, Hilman, Kevin wrote:
Abhilash K V abhilash...@ti.com writes:
In case of AM3517 AM3505, SmartReflex is not applicable so
we must not enable it.
This part is fine, but...
So omap3_twl_init() is now not called when the processor does not
support
hi Kevin
Thanks for reviewing the patch.
On Fri, Sep 23, 2011 at 3:25 AM, Hilman, Kevin wrote:
Abhilash K V abhilash...@ti.com writes:
This patch-set adds support for suspension to RAM and
resumption on the AM3517. This includes:
1. Patch to disable dynamic sleep (as it is not supported
hi Kevin,
Apologies for the delayed response, I was on vacation.
On October 01, 2011 4:57 AM, Hilman, Kevin wrote:
Abhilash,
Kevin Hilman khil...@ti.com writes:
Abhilash K V abhilash...@ti.com writes:
From: Abhilash K V abhilash...@ti.com
In case of AM3517 AM3505, SmartReflex is not
powerdomains3xxx_data.c defines core_3xxx_pre_es3_1_pwrdm and
core_3xxx_es3_1_pwrdm to take care of differences in core_pwrdm
implementations across revisions.
However,_pwrdm_lookup(core_pwrdm) always matches the first definition for
3630 ES 1.1 and 1.2 which is incorrect. This patch fixes this
Kevin Hilman wrote:
Abhilash K V abhilash...@ti.com writes:
From: Vaibhav Hiremath hvaib...@ti.com
In case of AM3517 AM3505, Smart Reflex is not applicable so
we must not enable it. So add check for am3517/05 cpu revision
in omap3_twl_init() and return -ENODEV if true, else continue.
Hi
On Friday, July 15, 2011 5:14 PM +0530, Koyamangalath, Abhilash wrote:
From: Koyamangalath, Abhilash
Sent: Friday, July 15, 2011 5:14 PM
To: linux-omap@vger.kernel.org
Cc: t...@atomide.com; li...@arm.linux.org.uk;
linux-arm-ker
On Wed, May 18, 2011 at 10:22:28AM -0600, Paul Walmsley wrote:
On Mon, 9 May 2011, Avinash.H.M. wrote:
On Thu, May 05, 2011 at 03:58:56PM -0600, Paul Walmsley wrote:
The patch is based on
*
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
On Thu, May 19, 2011 at 06:05:21PM +0530, Koyamangalath, Abhilash wrote:
I have tried the patch on am37x evm and the i2c soft-reset time-out issue
doesn't
seem to go off for me. Previously I used to get a log :
[0.00] omap_hwmod: i2c1: softreset failed (waited 1 usec
hi all
On the 2.6.37 , I've seen that when I set enable_off_mode mode through
debug-fs, VDD1 ( as measured across pin 2 of J6 and GND on OMAP3
EVM) increases from a nominal value of 1.225 V to 1.247 V.
When the uart finally times-out and the mpu_pwrdm enters OFF mode,
it finally goes down to
There this boot-time message (on both omap3 and am3517 evms atleast):
[1.904418] omap_device: omap_wdt.-1: new worst case activate latency 0: 6105
omap_init_wdt() initializes the id to -1 and then omap_device_build() is called
with this value; this eventually calls platform_device_register()
I understand, but is there a subtle reason why are starting from
an erroneous-looking -1 rather than a more natural 0 (or 1 ?).
-Original Message-
From: Balbi, Felipe
Sent: Friday, February 18, 2011 4:27 PM
To: Koyamangalath, Abhilash
Cc: linux-omap@vger.kernel.org
Subject: Re
There is this boot-time message on the am3517evm (and possibly
other omap 35xx based boards as well)
[0.00] _omap_mux_init_gpio: Multiple gpio paths
(2) for gpio126
I realized that this happens due to dual mappings for gpio_126 in
arch/arm/mach-omap2/mux34xx.c:
static struct omap_mux
While trying to register the sound card on the AM3517EVM (which uses a
tlv320aic23 codec), with the 2.6.37 kernel I get the following error message:
CODEC tlv320aic23-codec not registered
This is despite having gotten previously:
Registered codec 'tlv320aic23-codec.2-001a'
I
22 matches
Mail list logo
