All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Samuel Mendoza-Jonas <sam@mendozajonas.com>, linux-hwmon@vger.kernel.org
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH] hwmon (pmbus): Add client driver for IR35221
Date: Fri, 28 Apr 2017 07:11:37 -0700	[thread overview]
Message-ID: <0ce48f3c-9c7b-4bf8-2ed7-817098ecdfdf@roeck-us.net> (raw)
In-Reply-To: <1493354043.32554.1.camel@mendozajonas.com>

On 04/27/2017 09:34 PM, Samuel Mendoza-Jonas wrote:
> On Wed, 2017-04-26 at 11:03 +1000, Samuel Mendoza-Jonas wrote:
>> On Fri, 2017-04-21 at 06:49 -0700, Guenter Roeck wrote:
>>> On 04/20/2017 09:25 PM, Samuel Mendoza-Jonas wrote:
>>>> IR35221 is a Digital DC-DC Multiphase Converter
>>>>
>>>> Signed-off-by: Samuel Mendoza-Jonas <sam@mendozajonas.com>
>>>> ---
>>>> - Tested on a ppc64 system which includes several of these devices.
>>>> - This patch re-implements the linear reg2data/data2reg functions from
>>>>   pmbus-core like some other drivers in order to scale some results. Is
>>>>   this something that would be better off being made generic for pmbus
>>>>   drivers to call?
>>>
>>> That might make sense. The only other driver is zl6100, or am I missing
>>> something ?
>>
>> I believe ltc2978 has a small implementation as well.
>>
>>>
>>> Trying to understand the code, the data format seems to be linear11 with
>>> an added exponent on top of it. Is that correct ? If so, I wonder if we should
>>> make that configurable, ie store the additional exponent in R and handle it
>>> in the pmbus core. Would that help ?
>>
>> Yes that's essentially what it is. Using R for the extra exponent would
>> be a neat solution, however at least for this chip commands in the same
>> class have different scaling exponents (eg VIN_UV_WARN_LIMIT vs
>> READ_VIN). I'll have a look though and see if I can cover this - maybe a
>> small wrapper function that updates the exponent in the data returned by
>> pmbus_read_word_data()/etc?
>
> After thinking about this for a bit I don't think it's as straightforward
>  as I would like :)
>

Hm ... lets drop this for now; we can always revisit it later. Can you address
the other comments and resubmit ?

Thanks,
Guenter


  reply	other threads:[~2017-04-28 14:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  4:25 [PATCH] hwmon (pmbus): Add client driver for IR35221 Samuel Mendoza-Jonas
2017-04-21 13:49 ` Guenter Roeck
2017-04-26  1:03   ` Samuel Mendoza-Jonas
2017-04-28  4:34     ` Samuel Mendoza-Jonas
2017-04-28 14:11       ` Guenter Roeck [this message]
2017-04-21 20:55 ` Patrick Williams
2017-04-21 21:48   ` Guenter Roeck

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=0ce48f3c-9c7b-4bf8-2ed7-817098ecdfdf@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sam@mendozajonas.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.