All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "Gulati, Shweta" <shweta.gulati@ti.com>
Cc: Vishwanath Sripathy <vishwanath.bs@ti.com>, linux-omap@vger.kernel.org
Subject: Re: Smartreflex on 'pm-wip/voltdm' Branch
Date: Wed, 30 Mar 2011 07:52:54 -0700	[thread overview]
Message-ID: <87pqp8slrt.fsf@ti.com> (raw)
In-Reply-To: <AANLkTinHsk0dSKVwTK4DMYn+wmLnxXFxQkbRUREa2REy@mail.gmail.com> (Shweta Gulati's message of "Wed, 30 Mar 2011 11:51:48 +0530")

Hi Shweta,

"Gulati, Shweta" <shweta.gulati@ti.com> writes:

[...]

>>> I did a quick debug on this and found that the root cause of the issue is
>>> in usage of ffs (because of this, i2c slave address was configured wrongly
>>> in vc).
>>> Basically ffs returns the position of the first (least significant) bit
>>> set in the word and the least significant bit is position 1 where as our
>>> bit operation assumes that least significant position is 0.
>>
>> Vishwa, Thanks for findingg this.  Indeed, I had assumed ffs() was zero based,
>> but it is 1 based.
>>
>>> I tested the attached patch on OMAP3 and it seems to work fine.
> Attached, is Patch which fixes the Issue, It works Fine for OMAP3 and
> OMAP4 SDP boards.

Thanks for the patch, but my voltage cleanup series is work-in-progress,
and a moving target at the moment.  I've changed (again) the way I'm
splitting up the code so this patch won't apply directly.

I will however change to using __ffs instead of ffs.  Thanks for
pointing that out.  I wasn't aware of the difference between __ffs() and
ffs()

Kevin


--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-03-30 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 10:53 Smartreflex on 'pm-wip/voltdm' Branch Gulati, Shweta
2011-03-28 13:40 ` Vishwanath Sripathy
2011-03-28 16:27   ` Kevin Hilman
2011-03-30  6:21     ` Gulati, Shweta
2011-03-30 14:52       ` Kevin Hilman [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=87pqp8slrt.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=shweta.gulati@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.