From: Lars-Peter Clausen <lars@metafoo.de>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: Mark Brown <broonie@kernel.org>, Lee Jones <lee.jones@linaro.org>,
patches@opensource.wolfsonmicro.com,
Samuel Ortiz <sameo@linux.intel.com>,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: wm5102: Mark register 0x19 readable
Date: Mon, 10 Mar 2014 18:17:22 +0100 [thread overview]
Message-ID: <531DF3A2.80504@metafoo.de> (raw)
In-Reply-To: <20140310170524.GN8570@opensource.wolfsonmicro.com>
On 03/10/2014 06:05 PM, Charles Keepax wrote:
> On Mon, Mar 10, 2014 at 04:49:04PM +0000, Mark Brown wrote:
>> On Mon, Mar 10, 2014 at 04:38:11PM +0000, Lee Jones wrote:
>>
>>> Can we have a #define for these please?
>>
>> It'd be nice but you'd need to ask the Wolfson guys to tell us what it's
>> called, all the information I have is the read in the driver source.
>> Meanwile we've got a bug.
>
> WRITE_SEQUENCER_CTRL_3, seems we should add that in since it is
> required for that 5102 boot stuff. Slightly confused as to how
> that ever worked without the register being readable, but guess
> it has been a while since I have fired up 5102 on mainline.
>
Presumably this change triggered it:
http://git.kernel.org/cgit/linux/kernel/git/broonie/regmap.git/commit/?h=topic/core&id=d4807ad2c4c0e17b6f00e3be9492c81de0804f40
next prev parent reply other threads:[~2014-03-10 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 16:29 [PATCH] mfd: wm5102: Mark register 0x19 readable Mark Brown
2014-03-10 16:38 ` Lee Jones
2014-03-10 16:49 ` Mark Brown
2014-03-10 17:05 ` Charles Keepax
2014-03-10 17:12 ` Mark Brown
2014-03-10 17:17 ` Lars-Peter Clausen [this message]
2014-03-10 17:29 ` Mark Brown
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=531DF3A2.80504@metafoo.de \
--to=lars@metafoo.de \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--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 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.