public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Przemyslaw Marczak <p.marczak@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] POWER framework v3 - wish list
Date: Tue, 20 May 2014 11:16:57 +0200	[thread overview]
Message-ID: <537B1D89.6010909@samsung.com> (raw)
In-Reply-To: <CAPnjgZ1RqsN4+sjhO-_3m9cen-k47bi-i-7_Wp4OQ+4D55N4nw@mail.gmail.com>

Hello Simon,

On 05/19/2014 08:37 PM, Simon Glass wrote:
> Hi,
>
> On 9 May 2014 03:25, Przemyslaw Marczak <p.marczak@samsung.com> wrote:
>> Hello,
>>
>> Some time ago I had a pleasure to work on some kind of a simple
>> charger manager for u-boot. For checking battery charge level, cable
>> state, and some more info I made a common calls which were implemented in
>> board files, so actually it didn't base directly on PMIC framework. This
>> allowed making charger abstraction but it was a second power related
>> framework next to the PMIC.
>>  From my side I would like to introduce its next version according to the
>> doc/README.power-framework documents "TO DO" list and some more...
>>
>> In this RFC any comments about next version of power management framework
>> are welcome.
>> What new PMIC framework should provide?
>> How to extend it?
>> What can be fixed?
>>
>> So, what should be done (in my opinion):
>
> Can I suggest we try to build this with driver model if possible? It
> seems like you will otherwise end up duplicating much of the plumbing
> of that. For example, see 'struct device'.
>
> Regards,
> Simon
>

Yes, I also would like to take it into account - but I am not sure that 
driver model is not too redundant for it?
If I well understand the current driver model - each driver can have 
only one uclass, right? If yes, then for each previous listed ops we 
need to register separate driver - isn't it too much for read one 
register or turn on the led in the same physically device?

So maybe better is to register one "power" driver in driver model? And 
the power uclass driver could init more then one class specific ops.

I just would like to keep it simply.

Thanks
-- 
Przemyslaw Marczak
Samsung R&D Institute Poland
Samsung Electronics
p.marczak at samsung.com

  reply	other threads:[~2014-05-20  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <536C7C7A.40107@samsung.com>
2014-05-09 10:25 ` [U-Boot] [RFC] POWER framework v3 - wish list Przemyslaw Marczak
2014-05-19 18:37   ` Simon Glass
2014-05-20  9:16     ` Przemyslaw Marczak [this message]
2014-05-20 17:25       ` Simon Glass
2014-05-15 19:01 ` Marek Vasut
2014-05-20  8:47   ` Przemyslaw Marczak

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=537B1D89.6010909@samsung.com \
    --to=p.marczak@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