From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] MFD: mc13xxx workaround SPI hardware bug on i.Mx
Date: Thu, 31 May 2012 14:57:40 +0100 [thread overview]
Message-ID: <20120531135739.GH2666@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <2358422.efTs8lXp1l@laptop>
On Thu, May 31, 2012 at 09:08:39AM +0200, Philippe R?tornaz wrote:
> I already put it in struct regmap_config, should I put it elsewhere ?
> @@ -54,6 +54,67 @@ static struct regmap_config mc13xxx_regmap_spi_config = {
> .max_register = MC13XXX_NUMREGS,
>
> .cache_type = REGCACHE_NONE,
> + .use_single_rw = 1,
> +};
That's fine, I'd just expected to see it here.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120531/9f8a5d68/attachment.sig>
next prev parent reply other threads:[~2012-05-31 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1338282389-26177-1-git-send-email-philippe.retornaz@epfl.ch>
[not found] ` <1338282389-26177-2-git-send-email-philippe.retornaz@epfl.ch>
[not found] ` <1338282389-26177-3-git-send-email-philippe.retornaz@epfl.ch>
2012-05-30 17:08 ` [PATCH 2/2] MFD: mc13xxx workaround SPI hardware bug on i.Mx Mark Brown
2012-05-31 7:08 ` Philippe Rétornaz
2012-05-31 9:03 ` Samuel Ortiz
2012-06-22 15:48 ` Fabio Estevam
2012-06-29 7:41 ` Philippe Rétornaz
2012-05-31 13:57 ` Mark Brown [this message]
2012-05-30 23:47 ` Marc Reilly
2012-05-31 23:51 ` [PATCH 1/2] MFD: Fix mc13xxx SPI regmap Fabio Estevam
2012-06-29 13:09 ` [PATCH 0/2] MC13xxx: fix access on i.mx31 Samuel Ortiz
2012-07-01 11:03 ` Philippe Rétornaz
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=20120531135739.GH2666@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).