public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: wens@csie.org, maxime.ripard@free-electrons.com, sre@kernel.org,
	dbaryshkov@gmail.com, dwmw2@infradead.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
	linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
	linux-sunxi@googlegroups.com, robh+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] mfd: axp20x: add adc volatile ranges for axp22x
Date: Fri, 5 Aug 2016 08:46:22 +0100	[thread overview]
Message-ID: <20160805074622.GL5243@dell> (raw)
In-Reply-To: <20160701092926.32005-1-icenowy@aosc.xyz>

On Fri, 01 Jul 2016, Icenowy Zheng wrote:

> AXP22x has also some different register map than axp20x, they're also
> added here.
> 
> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
> ---
>  drivers/mfd/axp20x.c       | 1 +
>  include/linux/mfd/axp20x.h | 4 ++++
>  2 files changed, 5 insertions(+)

Applied, thanks.

> diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
> index d62209d..cee5288 100644
> --- a/drivers/mfd/axp20x.c
> +++ b/drivers/mfd/axp20x.c
> @@ -96,6 +96,7 @@ static const struct regmap_range axp22x_volatile_ranges[] = {
>  	regmap_reg_range(AXP20X_PWR_INPUT_STATUS, AXP20X_PWR_OP_MODE),
>  	regmap_reg_range(AXP20X_IRQ1_EN, AXP20X_IRQ5_STATE),
>  	regmap_reg_range(AXP22X_GPIO_STATE, AXP22X_GPIO_STATE),
> +	regmap_reg_range(AXP22X_PMIC_ADC_H, AXP20X_IPSOUT_V_HIGH_L),
>  	regmap_reg_range(AXP20X_FG_RES, AXP20X_FG_RES),
>  };
>  
> diff --git a/include/linux/mfd/axp20x.h b/include/linux/mfd/axp20x.h
> index 0be4982..ad3d9c7 100644
> --- a/include/linux/mfd/axp20x.h
> +++ b/include/linux/mfd/axp20x.h
> @@ -201,6 +201,10 @@ enum {
>  #define AXP20X_OCV_MAX			0xf
>  
>  /* AXP22X specific registers */
> +#define AXP22X_PMIC_ADC_H		0x56
> +#define AXP22X_PMIC_ADC_L		0x57
> +#define AXP22X_TS_ADC_H			0x58
> +#define AXP22X_TS_ADC_L			0x59
>  #define AXP22X_BATLOW_THRES1		0xe6
>  
>  /* AXP288 specific registers */

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      parent reply	other threads:[~2016-08-05  7:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160701092926.32005-1-icenowy@aosc.xyz>
     [not found] ` <20160701092926.32005-2-icenowy@aosc.xyz>
2016-07-05  5:26   ` [linux-sunxi] [PATCH 2/4] power: add axp20x-battery driver Michael Haas
     [not found]     ` <112861467708458@web7h.yandex.ru>
2016-07-05 12:43       ` Bruno Prémont
     [not found]     ` <4101467707611@web7h.yandex.ru>
2016-07-05  9:25       ` maxime.ripard
2016-07-05 12:45         ` Bruno Prémont
2016-07-06  4:34       ` Michael Haas
2016-08-05  7:46 ` Lee Jones [this message]

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=20160805074622.GL5243@dell \
    --to=lee.jones@linaro.org \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=icenowy@aosc.xyz \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh+dt@kernel.org \
    --cc=sre@kernel.org \
    --cc=wens@csie.org \
    /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