All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Vishwanath Sripathy <vishwanath.bs@ti.com>
Cc: Sanjeev Premi <premi@ti.com>, linux-omap@vger.kernel.org
Subject: Re: [query] smartreflex: No PMIC hook to init smartreflex
Date: Thu, 27 Jan 2011 22:23:59 +0530	[thread overview]
Message-ID: <4D41A327.6040206@ti.com> (raw)
In-Reply-To: <2dcb8dc49945099cbbc5c4f725d845a5@mail.gmail.com>

Vishwanath Sripathy wrote, on 01/27/2011 07:55 PM:
> Nishant,
>
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>> owner@vger.kernel.org] On Behalf Of Menon, Nishanth
>> Sent: Thursday, January 27, 2011 3:06 PM
>> To: Premi, Sanjeev
>> Cc: linux-omap@vger.kernel.org
>> Subject: Re: [query] smartreflex: No PMIC hook to init smartreflex
>>
>> Sanjeev,
>>
>> On Tue, Jan 25, 2011 at 20:55, Premi, Sanjeev<premi@ti.com>  wrote:
>>> While building the kernel at 2.6.37, i see this warning for omap3evm -
>> with omap3630:
>>>
>>> Power Management for TI OMAP3.
>>> sr_init: No PMIC hook to init smartreflex<-- THIS IS THE WARNING.
>>> smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver
>> initialized
>>> smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver
>> initialized
>>> SmartReflex Class3 initialized
>>>
>>> In the code, i see this comment:
>>>   /*
>>>   * sr_init is a late init. If by then a pmic specific API is not
>>>   * registered either there is no need for anything to be done on
>>>   * the PMIC side or somebody has forgotten to register a PMIC
>>>   * handler. Warn for the second condition.
>>>   */
>>>   if (sr_pmic_data&&  sr_pmic_data->sr_pmic_init)
>>>   sr_pmic_data->sr_pmic_init();
>>>   else
>>>   pr_warning("%s: No PMIC hook to init smartreflex\n", __func__);
>>>
>>> But, I couldn't find any place where PMIC is being registered.
>>
>> This is a harmless warning (ideally, we should remove the pr_warning).
>>   the intent here is to have hook for pmic_init which could be
>> populated for custom PMICs which may need "something additional" for
>> Smart reflex enablement. if you look at the sr_pmic_data - it just has
>> a single api for pmic_init
>>
>> e.g. in the case of TWL4030/5030, we might need to set the bit to
>> switch mode from I2C1 to I2C_SR - e.g. the patch from Shweta[1]
>>
>> if Smartreflex AVS was the *only* mechanism in the system, we could
>> have hooked pmic_init to this bit setting. but since the system can do
>> voltage scaling (VP forceupdate/vc bypass) independent of SR AVS
>> block, the patch in [1] does initialization independent of
>> sr_pmic_data->pmic_init which makes sense.
>>
>> in short, my 2cents: the warning is probably something we should
>> remove from the code.
> As you mentioned, incase of TWL4030/5030, we do not need any hook. However
> if some other PMIC is used that genuinely needs this hook, then shouldn't
> SR throw up this warning? As SR module is independent of PMIC, it cannot
> distinguish them. So I feel this warning should be present probably
> reworded better like "No PMIC hook registered to init smartreflex. Either
> this PM IC does not need SR init or PMIC hook is missing".

Fair enough - but how do we know if the warning spawns off question such 
as this thread? aka false alarm? if a platform does need initialization 
it should be up to the platform porting person rt?

Just that I dont think it makes sense to false flag folks considering 
that the API is optional.

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2011-01-27 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 15:25 [query] smartreflex: No PMIC hook to init smartreflex Premi, Sanjeev
2011-01-27  9:35 ` Menon, Nishanth
2011-01-27 14:07   ` Gulati, Shweta
2011-01-27 14:25   ` Vishwanath Sripathy
2011-01-27 16:53     ` Nishanth Menon [this message]
2011-01-31 16:20     ` Premi, Sanjeev
2011-02-01  4:50       ` 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=4D41A327.6040206@ti.com \
    --to=nm@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.com \
    --cc=vishwanath.bs@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.