From: Lee Jones <lee.jones@linaro.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 1/2] mfd: twl6040: The chip does not support bulk access
Date: Wed, 31 Aug 2016 15:39:31 +0100 [thread overview]
Message-ID: <20160831143931.GM9415@dell> (raw)
In-Reply-To: <20160831114621.6301-2-peter.ujfalusi@ti.com>
On Wed, 31 Aug 2016, Peter Ujfalusi wrote:
> Bulk access is not working with twl6040, we need to use single register
> access. Bulk access would happen when we try to sync the regcache after
> power on.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> drivers/mfd/twl6040.c | 1 +
> 1 file changed, 1 insertion(+)
Applied, thanks.
> diff --git a/drivers/mfd/twl6040.c b/drivers/mfd/twl6040.c
> index ab328ec49353..c3ad59ef43dd 100644
> --- a/drivers/mfd/twl6040.c
> +++ b/drivers/mfd/twl6040.c
> @@ -609,6 +609,7 @@ static const struct regmap_config twl6040_regmap_config = {
> .writeable_reg = twl6040_writeable_reg,
>
> .cache_type = REGCACHE_RBTREE,
> + .use_single_rw = true,
> };
>
> static const struct regmap_irq twl6040_irqs[] = {
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-08-31 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 11:46 [PATCH RESEND 0/2] mfd: twl6040: bulk access fix and pdmclk registration Peter Ujfalusi
2016-08-31 11:46 ` Peter Ujfalusi
2016-08-31 11:46 ` [PATCH RESEND 1/2] mfd: twl6040: The chip does not support bulk access Peter Ujfalusi
2016-08-31 11:46 ` Peter Ujfalusi
2016-08-31 14:39 ` Lee Jones [this message]
2016-08-31 11:46 ` [PATCH RESEND 2/2] mfd: twl6040: Register child device for twl6040-pdmclk Peter Ujfalusi
2016-08-31 11:46 ` Peter Ujfalusi
2016-08-31 14:38 ` Lee Jones
2016-08-31 14:39 ` Lee Jones
2016-09-27 8:14 ` Peter Ujfalusi
2016-09-27 8:14 ` Peter Ujfalusi
2016-09-27 18:50 ` Lee Jones
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=20160831143931.GM9415@dell \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.