From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] mfd: tps65217: Tell regmap what registers are valid
Date: Mon, 8 Sep 2014 09:00:30 +0100 [thread overview]
Message-ID: <20140908080030.GK1397@lee--X1> (raw)
In-Reply-To: <1409951778-30513-1-git-send-email-broonie@kernel.org>
On Fri, 05 Sep 2014, Mark Brown wrote:
> Allow regmap to provide debugfs access to the register map by telling it
> what registers are valid.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> drivers/mfd/tps65217.c | 2 ++
> include/linux/mfd/tps65217.h | 2 ++
> 2 files changed, 4 insertions(+)
Applied, thanks.
> diff --git a/drivers/mfd/tps65217.c b/drivers/mfd/tps65217.c
> index 3cc4c7084b92..a8ee52c95f2f 100644
> --- a/drivers/mfd/tps65217.c
> +++ b/drivers/mfd/tps65217.c
> @@ -146,6 +146,8 @@ EXPORT_SYMBOL_GPL(tps65217_clear_bits);
> static struct regmap_config tps65217_regmap_config = {
> .reg_bits = 8,
> .val_bits = 8,
> +
> + .max_register = TPS65217_REG_MAX,
> };
>
> static const struct of_device_id tps65217_of_match[] = {
> diff --git a/include/linux/mfd/tps65217.h b/include/linux/mfd/tps65217.h
> index 95d6938737fd..ac7fba44d7e4 100644
> --- a/include/linux/mfd/tps65217.h
> +++ b/include/linux/mfd/tps65217.h
> @@ -60,6 +60,8 @@
> #define TPS65217_REG_SEQ5 0X1D
> #define TPS65217_REG_SEQ6 0X1E
>
> +#define TPS65217_REG_MAX TPS65217_REG_SEQ6
> +
> /* Register field definitions */
> #define TPS65217_CHIPID_CHIP_MASK 0xF0
> #define TPS65217_CHIPID_REV_MASK 0x0F
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2014-09-08 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 21:16 [PATCH] mfd: tps65217: Tell regmap what registers are valid Mark Brown
2014-09-08 8:00 ` 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=20140908080030.GK1397@lee--X1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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