public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] misc:pmic: Support for voltage to register value conversion function
Date: Wed, 28 Mar 2012 13:26:06 +0200	[thread overview]
Message-ID: <20120328132606.7537d9c6@lmajewski.digital.local> (raw)
In-Reply-To: <4F72E766.3050503@denx.de>

Hi Stefano,

On Wed, 28 Mar 2012 12:26:46 +0200
Stefano Babic <sbabic@denx.de> wrote:

> On 28/03/2012 10:45, Lukasz Majewski wrote:
> > Support for voltage (in uV) to proper register value is added.
> > The function tied to this callback is often PMIC dependent
> > and shall be defined for each device.
> > 
> > Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > Cc: Stefano Babic <sbabic@denx.de>
> > ---
> 
> Hi Lukasz,
> 
> >  
> > +int pmic_vol_to_reg(struct pmic *p, int uV)
> 
> You added a new entry point to pmic, but you do not use it...I have
> not found in your patchset why it is necessary for you.
> 

Rationale for this change is in commits following this one.
For trats Samsung target it is necessary to change the default voltage.

I think, that providing access to such a function as a pointer is the
best possible solution.

For example the MAX8997 and MAX8998 PMICs have different way of
calculating the value, which represents the LDO output value.


> I am not sure if we require to add this to the PMIC API or hide in the
> pmic specific code. Other PMICs has not a a register for different
> voltages, but only a bit inside the same register (this is the case
> for the Freescale's PMICs we currently support in u-boot).

I think, that it is easier to define function pointer in the pmic
structure, than separate functions and handling them in target platform
data.


> Best regards,
> Stefano Babic
> 


-- 
Best regards,

Lukasz Majewski

Samsung Poland R&D Center
Platform Group

  reply	other threads:[~2012-03-28 11:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  8:45 [U-Boot] [PATCH 1/3] misc:pmic: Support for voltage to register value conversion function Lukasz Majewski
2012-03-28  8:45 ` [U-Boot] [PATCH 2/3] misc:pmic:max8997 MAX8997 support for PMIC driver Lukasz Majewski
2012-03-28  8:45 ` [U-Boot] [PATCH 3/3] misc:pmic:samsung Convert TRATS target to use MAX8997 instead of MAX8998 Lukasz Majewski
2012-03-28 10:19   ` Minkyu Kang
2012-03-28 10:26 ` [U-Boot] [PATCH 1/3] misc:pmic: Support for voltage to register value conversion function Stefano Babic
2012-03-28 11:26   ` Lukasz Majewski [this message]
2012-03-28 11:41     ` Stefano Babic
     [not found]       ` <20120328143820.44ca652c@lmajewski.digital.local>
2012-03-28 12:50         ` Stefano Babic
2012-03-28 13:13           ` Lukasz Majewski
2012-03-28 14:43             ` Stefano Babic
2012-03-29  7:39               ` Lukasz Majewski

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=20120328132606.7537d9c6@lmajewski.digital.local \
    --to=l.majewski@samsung.com \
    --cc=u-boot@lists.denx.de \
    /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