public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Mark WM8350 mask revision as readable to match silicon
Date: Sun, 3 May 2009 23:57:29 +0200	[thread overview]
Message-ID: <20090503215728.GC3278@sortiz.org> (raw)
In-Reply-To: <1241099069-17778-1-git-send-email-broonie@opensource.wolfsonmicro.com>

Hi Mark,

On Thu, Apr 30, 2009 at 02:44:29PM +0100, Mark Brown wrote:
> No impact unless someone has written additional kernel code.
All 3 patches applied to my for-next branch, thanks.

Cheers,
Samuel.


> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>  drivers/mfd/wm8350-regmap.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/mfd/wm8350-regmap.c b/drivers/mfd/wm8350-regmap.c
> index 9a4cc95..97d6aad 100644
> --- a/drivers/mfd/wm8350-regmap.c
> +++ b/drivers/mfd/wm8350-regmap.c
> @@ -3186,7 +3186,7 @@ const struct wm8350_reg_access wm8350_reg_io_map[] = {
>  	/*  read    write volatile */
>  	{ 0xFFFF, 0xFFFF, 0xFFFF }, /* R0   - Reset/ID */
>  	{ 0x7CFF, 0x0C00, 0x7FFF }, /* R1   - ID */
> -	{ 0x0000, 0x0000, 0x0000 }, /* R2 */
> +	{ 0x007F, 0x0000, 0x0000 }, /* R2   - ROM Mask ID */
>  	{ 0xBE3B, 0xBE3B, 0x8000 }, /* R3   - System Control 1 */
>  	{ 0xFEF7, 0xFEF7, 0xF800 }, /* R4   - System Control 2 */
>  	{ 0x80FF, 0x80FF, 0x8000 }, /* R5   - System Hibernate */
> -- 
> 1.6.2.4
> 

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2009-05-03 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 13:44 [PATCH] mfd: Mark WM8350 mask revision as readable to match silicon Mark Brown
2009-05-03 21:57 ` Samuel Ortiz [this message]
2009-05-03 22:04   ` Mark Brown
2009-05-04  7:50     ` Samuel Ortiz
  -- strict thread matches above, loose matches on Subject: below --
2009-04-22 20:46 Mark Brown
2009-03-12 10:17 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=20090503215728.GC3278@sortiz.org \
    --to=sameo@linux.intel.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.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