From: Ameya Palande <ameya.palande@nokia.com>
To: "ext Gupta, Ramesh" <grgupta@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Menon, Nishanth" <nm@ti.com>,
"Kanigeri, Hari" <h-kanigeri2@ti.com>
Subject: Re: [PATCH] DSPBRIDGE Fix for auto image load updated
Date: Mon, 16 Mar 2009 16:27:54 +0200 [thread overview]
Message-ID: <49BE61EA.8000206@nokia.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02A90DFDE6@dbde02.ent.ti.com>
Hi Ramesh,
ext Gupta, Ramesh wrote:
> Ameya,
>
>
>>>
>> Hi Ramesh,
>>
>> I am not clear about the issue which this patch fixes.
>> As I understand that:
>>
>> 1. You have increased the count for
>> pdata->mpu_speed[i] = vdd1_rate_table_bridge[i].rate;
>>
>> 2. Moved driverContext = DSP_Init(&initStatus) after
>> clk_notifier_register stuff.
>
> These 2 changes fix the issue.
>
>> 3. Coding Style cleanups.
>
> This is to fix only the checkpatch warnings.
>
>> I am not able to understand what this patch is fixing and how?
>> Some explanation about this will be helpful.
>
> Clock registration is called after DSP_Init mistakenly , the image autoloading loads PROC_Load
> Inturn that calls for OPP boosting while loading the image , this fails as the clock registration is not called.
>
> There was a typo in filling the platform data (5 instead of 6) because of that, the OPP5 frequency value is not updated, that causes WARN_ON()
> In the SRF.
>
> Please let me know if you need any more information on these changes.
>
> Thanks
> Ramesh Gupta G
Just by looking at the patch these things were not clear to me.
Thanks a lot for your quick reply :)
Cheers,
Ameya.
prev parent reply other threads:[~2009-03-16 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 15:24 [PATCH] DSPBRIDGE Fix for auto image load updated Gupta, Ramesh
2009-03-13 0:16 ` Menon, Nishanth
2009-03-16 14:11 ` Ameya Palande
2009-03-16 14:23 ` Gupta, Ramesh
2009-03-16 14:27 ` Ameya Palande [this message]
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=49BE61EA.8000206@nokia.com \
--to=ameya.palande@nokia.com \
--cc=grgupta@ti.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.