mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Zhang <markz@nvidia.com>
To: <blaws05@gmail.com>, <lee.jones@linaro.org>,
	<linux-kernel@vger.kernel.org>
Cc: <linux-tegra@vger.kernel.org>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Venkat Reddy Talla <vreddytalla@nvidia.com>
Subject: Re: [2/2] mfd: max77620: Add low battery monitor support
Date: Tue, 29 Jan 2019 14:52:31 +0800	[thread overview]
Message-ID: <bd942195-4f1c-1a39-283f-610354308f45@nvidia.com> (raw)
In-Reply-To: <3587c682-e1db-5140-fd8e-13c46d882dd3@gmail.com>

On 1/27/2019 10:54 PM, Billy Laws wrote:
>  >This patch adds PMIC configurations for low-battery
>  >monitoring by handling max77620 register CNFGGLBL1.
>  >
> It might be an idea to add lbhyst configuration here and support using
> custom lbdac values to specify a different cutoff point.

Yeah this patch doesn't have support to program LBHYST & LBDAC because
according to our experiences, we don't have requirement to modify them
when low battery monitor support added.

I think we can create a new patch to support these 2 fields in the future
when we really need them. Or you can create a patch if you have requirement
for them, is this OK to you Billy?

Mark

> 
> See: https://datasheetspdf.com/pdf-file/924230/Maxim/MAX8698C/1  pg 46
>  >Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>  >Signed-off-by: Venkat Reddy Talla <vreddytalla@nvidia.com>
>  >Signed-off-by: Mark Zhang <markz@nvidia.com>
>  >---
>  > drivers/mfd/max77620.c | 57 +++++++++++++++++++++++++++++++++++++++++-
>  > 1 file changed, 56 insertions(+), 1 deletion(-)
>  >
>  >diff --git a/drivers/mfd/max77620.c b/drivers/mfd/max77620.c
>  >index f58143103185..9e50d145afd8 100644
>  >--- a/drivers/mfd/max77620.c
>  >+++ b/drivers/mfd/max77620.c
>  >@@ -474,6 +474,57 @@ static int 
> max77620_init_backup_battery_charging(struct max77620_chip *chip)
>  >  return ret;
>  > }
>  >
>  >+static int max77620_init_low_battery_monitor(struct max77620_chip *chip)
>  >+{
>  >+ struct device *dev = chip->dev;
>  >+ struct device_node *np;
>  >+ bool pval;
>  >+ u8 mask = 0;
>  >+ u8 val = 0;
>  >+ int ret;
>  >+
>  >+ np = of_get_child_by_name(dev->of_node, "low-battery-monitor");
>  >+ if (!np) {
>  >+ dev_info(dev, "Low battery monitoring support disabled\n");
>  >+ return 0;
>  >+ }
>  >+
>  >+ pval = of_property_read_bool(np, "maxim,low-battery-dac-enable");
>  >+ if (pval) {
>  >+ mask |= MAX77620_CNFGGLBL1_LBDAC_EN;
>  >+ val |= MAX77620_CNFGGLBL1_LBDAC_EN;
>  >+ }
>  >+
>  >+ pval = of_property_read_bool(np, "maxim,low-battery-dac-disable");
>  >+ if (pval)
>  >+ mask |= MAX77620_CNFGGLBL1_LBDAC_EN;
>  >+
>  >+ pval = of_property_read_bool(np, "maxim,low-battery-shutdown-enable");
>  >+ if (pval) {
>  >+ mask |= MAX77620_CNFGGLBL1_MPPLD;
>  >+ val |= MAX77620_CNFGGLBL1_MPPLD;
>  >+ }
>  >+
>  >+ pval = of_property_read_bool(np, "maxim,low-battery-shutdown-disable");
>  >+ if (pval)
>  >+ mask |= MAX77620_CNFGGLBL1_MPPLD;
>  >+
>  >+ pval = of_property_read_bool(np, "maxim,low-battery-reset-enable");
>  >+ if (pval) {
>  >+ mask |= MAX77620_CNFGGLBL1_LBRSTEN;
>  >+ val |= MAX77620_CNFGGLBL1_LBRSTEN;
>  >+ }
>  >+
>  >+ pval = of_property_read_bool(np, "maxim,low-battery-reset-disable");
>  >+ if (pval)
>  >+ mask |= MAX77620_CNFGGLBL1_LBRSTEN;
>  >+
>  >+ ret = regmap_update_bits(chip->rmap, MAX77620_REG_CNFGGLBL1, mask, val);
>  >+ if (ret < 0)
>  >+ dev_err(dev, "Reg CNFGGLBL1 update failed: %d\n", ret);
>  >+ return ret;
>  >+}
>  >+
>  > static int max77620_read_es_version(struct max77620_chip *chip)
>  > {
>  >  unsigned int val;
>  >@@ -563,7 +614,11 @@ static int max77620_probe(struct i2c_client *client,
>  >  if (ret < 0)
>  >  return ret;
>  >
>  >- ret =  devm_mfd_add_devices(chip->dev, PLATFORM_DEVID_NONE,
>  >+ ret = max77620_init_low_battery_monitor(chip);
>  >+ if (ret < 0)
>  >+ return ret;
>  >+
>  >+ ret = devm_mfd_add_devices(chip->dev, PLATFORM_DEVID_NONE,
>  >      mfd_cells, n_mfd_cells, NULL, 0,
>  >      regmap_irq_get_domain(chip->top_irq_data));
>  >  if (ret < 0) {
> 

  parent reply	other threads:[~2019-01-29  6:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-27 14:54 Billy Laws
2019-01-28  7:15 ` Lee Jones
2019-01-28  7:16 ` Lee Jones
2019-01-28  7:33   ` Billy Laws
2019-01-29  6:52 ` Mark Zhang [this message]
2019-01-29  7:36   ` Billy Laws
2019-01-29  7:41     ` 答复: " Mark Zhang
2019-01-29  9:03     ` Mark Zhang
2019-01-29 13:33       ` Billy Laws
2019-01-30  1:44         ` 答复: " Mark Zhang

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=bd942195-4f1c-1a39-283f-610354308f45@nvidia.com \
    --to=markz@nvidia.com \
    --cc=blaws05@gmail.com \
    --cc=ldewangan@nvidia.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=vreddytalla@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®