mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: lee.jones@linaro.org
Cc: patches@opensource.wolfsonmicro.com, sameo@linux.intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] mfd: arizona: Mark additional registers as volatile
Date: Wed, 13 Aug 2014 10:22:09 +0100	[thread overview]
Message-ID: <20140813092209.GE15833@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1407851483-19207-4-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On Tue, Aug 12, 2014 at 02:51:23PM +0100, Charles Keepax wrote:
> Mark some additional registers as volatile. The write sequencer control
> registers should not be cached, as we don't ever want their value
> synchronised as this might cause a write sequence to be accidentally
> initiated.
> 
> Additionally, the DAC_COMP registers require special preconditions to
> write so there values wouldn't be updated accurately during a register
> sync.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---

Apologies please ignore this patch, I forgot I was carrying a
patch from Mark that it depends on that doesn't appear to be in
your MFD tree. I will resend Mark's patch first.

Thanks,
Charles

  reply	other threads:[~2014-08-13  9:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 13:51 [PATCH 1/4] mfd: arizona: Add additional dummy IRQ callbacks Charles Keepax
2014-08-12 13:51 ` [PATCH 2/4] mfd: arizona: Propagate irq_wake through to parent IRQ Charles Keepax
2014-08-21 11:57   ` Lee Jones
2014-08-12 13:51 ` [PATCH 3/4] mfd: arizona: Avoid use of legacy IRQ mapping Charles Keepax
2014-08-21 11:59   ` Lee Jones
2014-08-12 13:51 ` [PATCH 4/4] mfd: arizona: Mark additional registers as volatile Charles Keepax
2014-08-13  9:22   ` Charles Keepax [this message]
2014-08-21 11:56 ` [PATCH 1/4] mfd: arizona: Add additional dummy IRQ callbacks Lee Jones
2014-08-21 12:05   ` Charles Keepax
2014-09-02 14:09   ` Charles Keepax
2014-09-02 14:26     ` 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=20140813092209.GE15833@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=lee.jones@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome