public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v1 2/2] power: regulator: support ROHM BD71837 PMIC
Date: Thu, 4 Apr 2019 10:03:36 +0300	[thread overview]
Message-ID: <20190404070336.GD3493@localhost.localdomain> (raw)
In-Reply-To: <3ec638180b97ce4acb8da2710c3a42c1ed816441.1553690211.git.matti.vaittinen@fi.rohmeurope.com>

Hi de Ho Peeps,

On Wed, Mar 27, 2019 at 02:40:47PM +0200, Matti Vaittinen wrote:
> Add regulator driver for ROHM BD71837 PMIC. BD71837 contains
> 8 bucks and 7 LDOS. Voltages for bucks 1-4 can be adjusted
> when regulators are enabled. For other bucks and LDOs we may
> have over- or undershooting if voltage is adjusted when
> regulator is enabled. Thus this is prevented by default.
> 
> BD71837 has a quirk which may leave power output disabled
> after reset if enable/disable state was controlled by SW.
> Thus the SW control is only allowed for bucks3 and 4 by
> default.
> 
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> ---
>  drivers/power/regulator/Kconfig   |  15 ++
>  drivers/power/regulator/Makefile  |   1 +
>  drivers/power/regulator/bd71837.c | 373 ++++++++++++++++++++++++++++++
>  include/power/bd71837.h           |  20 ++
>  4 files changed, 409 insertions(+)
>

This Patch:

This was my first patch to U-boot so I wonder if there is something to
improve. Is this Ok like this or should I have formatted it somehow
differently?

Also, is this type of submissions welcome? Any place to check if
submissions are rejected, being reviewed or forgotten?


Next Steps:

Finally, the BD71837 is mainly targeted for powering the i.MX8M. There's
another ROHM PMIC BD71847 - which is mainly used for powering the
i.MX8MM. The Linux driver I wrote does support both of these PMICs and I
was thinking that maybe I should add support for BD71847 in this u-Boot
driver too. But before investing on that work I would like to get some
feedback regarding the BD71837 u-boot driver. At least a sign that this
kind of submissions are welcome or information if I am doing something
completely wrong =)


About RFC tag:

I used RFC tag here mainly because I am unsure if the driver design fits
what the u-boot is heading on or if this is kind of driver u-Boot should
include. Is this correct use of RFC, and what are the consequences of
using RFC-tag? My assumption was that the patch with RFC is reviewed as
ither patches, but it is also a sign that the patch might have something
that makes it unsuitable for applying to u-Boot. Is this correct?

Finally, I guess I need to (re)submit the driver(s) without the RFC tag
at some point, any suggestions when?


Best Regards
	Matti Vaittinen

  reply	other threads:[~2019-04-04  7:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 12:39 [U-Boot] [RFC PATCH v1 1/2] copy the bd71837 pmic driver from NXP imx u-boot Matti Vaittinen
2019-03-27 12:40 ` [U-Boot] [RFC PATCH v1 2/2] power: regulator: support ROHM BD71837 PMIC Matti Vaittinen
2019-04-04  7:03   ` Matti Vaittinen [this message]
2019-04-24  3:54   ` Simon Glass
2019-04-24  5:59     ` Vaittinen, Matti
2019-04-24 16:54       ` Simon Glass

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=20190404070336.GD3493@localhost.localdomain \
    --to=matti.vaittinen@fi.rohmeurope.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