linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP4: Intialize IVA Device in addition to DSP device.
Date: Thu, 10 Mar 2011 19:25:44 +0530	[thread overview]
Message-ID: <4D78D860.2050609@ti.com> (raw)
In-Reply-To: <fc1162b5d4e1a7deb77aa800a3e8fdb3@mail.gmail.com>

Few cosmetic comments follow:
Vishwanath Sripathy wrote, on 03/10/2011 02:36 PM:
>> -----Original Message-----
>> From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-arm-
>> kernel-bounces at lists.infradead.org] On Behalf Of Shweta Gulati
>> Sent: Thursday, March 10, 2011 11:52 AM
>> To: linux-omap at vger.kernel.org
>> Cc: Shweta Gulati; linux-arm-kernel at lists.infradead.org
>> Subject: [PATCH] OMAP4: Intialize IVA Device in addition to DSP device.
>>
>> OMAP4 has two different Devices IVA and DSP. DSP is bound
>> with MPU for DVFS and IVA has its own well defined OPPs.
> DSP is not in MPU voltage domain. DSP(Tesla) and IVAHD are in the same
> voltage domain. Pls correct this in the commit log.
True for OMAP4 - DSP and MPU DVFS are independent, in OMAP3, they were 
scaled together ;)

[...]
>> This Patch adds IVA init to 'omap2_init_processor_devices'
>> and make sure that API 'omap2_set_init_voltage' is called
>> for apt dev pointer.

set_init_voltage error is just one symptom of the problem. infact, if we 
wanted to do anything with iva - e.g. dvfs, we would'nt have been able 
to without the device being registered.

>>
>> It fixes Error logs:
"This also fixes the following error seen during boot as 
omap2_set_init_voltage can now find the iva device" is better than the 
"This patch...."?
>>
>> 	omap2_set_init_voltage: Invalid parameters!
>> 	omap2_set_init_voltage: Unable to put vdd_iva to its init voltage

Thanks for catching and fixing this - I had noticed this in my SR 1.5 
testing(should have posted as well), but had'nt tried to dig further.

>>
>> Tested on OMAP4430 SDP Board.
>> Baseline:
>> http://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-
>> pm.git
>> Branch :pm-core
Do you really want this information in commit log? I suggest you move 
this to the diffstat section.

>>
>> Signed-off-by: Shweta Gulati<shweta.gulati@ti.com>
>> ---
>>   arch/arm/mach-omap2/pm.c |    1 +
>>   1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c
>> index 30af335..49486f5 100644
>> --- a/arch/arm/mach-omap2/pm.c
>> +++ b/arch/arm/mach-omap2/pm.c
>> @@ -89,6 +89,7 @@ static void omap2_init_processor_devices(void)
>>   	if (cpu_is_omap44xx()) {
>>   		_init_omap_device("l3_main_1",&l3_dev);
>>   		_init_omap_device("dsp",&dsp_dev);
>> +		_init_omap_device("iva",&iva_dev);
>>   	} else {
>>   		_init_omap_device("l3_main",&l3_dev);
>>   	}



-- 
Regards,
Nishanth Menon

  reply	other threads:[~2011-03-10 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10  6:22 [PATCH] OMAP4: Intialize IVA Device in addition to DSP device Shweta Gulati
2011-03-10  9:06 ` Vishwanath Sripathy
2011-03-10 13:55   ` Nishanth Menon [this message]
2011-03-11  5:39     ` Gulati, Shweta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D78D860.2050609@ti.com \
    --to=nm@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).