public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: voice <voice.shen@atmel.com>
Cc: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
	JM.Lin@atmel.com, Hong.Xu@atmel.com
Subject: Re: [PATCH] atmel ac97c: using software reset instead hardware reset if not available
Date: Thu, 15 Dec 2011 14:04:12 +0100	[thread overview]
Message-ID: <4EE9F04C.6080906@atmel.com> (raw)
In-Reply-To: <1322042701-32100-1-git-send-email-voice.shen@atmel.com>

On 11/23/2011 11:05 AM, voice :
> Using software reset instead hardware reset if not available

Ping?
Can you please tell me what is the status of this fix? Will it go
upstream for 3.3?

> Signed-off-by: Bo Shen <voice.shen@atmel.com>
> ---
>  sound/atmel/ac97c.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/sound/atmel/ac97c.c b/sound/atmel/ac97c.c
> index 6e5adde..73516f6 100644
> --- a/sound/atmel/ac97c.c
> +++ b/sound/atmel/ac97c.c
> @@ -899,6 +899,10 @@ static void atmel_ac97c_reset(struct atmel_ac97c *chip)
>  		/* AC97 v2.2 specifications says minimum 1 us. */
>  		udelay(2);
>  		gpio_set_value(chip->reset_pin, 1);
> +	} else {
> +		ac97c_writel(chip, MR, AC97C_MR_WRST | AC97C_MR_ENA);
> +		udelay(2);
> +		ac97c_writel(chip, MR, AC97C_MR_ENA);
>  	}
>  }
>  


-- 
Nicolas Ferre

  parent reply	other threads:[~2011-12-15 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 10:05 [PATCH] atmel ac97c: using software reset instead hardware reset if not available voice
2011-11-24 10:44 ` Nicolas Ferre
2011-12-15 13:04 ` Nicolas Ferre [this message]
2011-12-16  1:52   ` Shen, Voice
2011-12-16  8:39     ` Nicolas Ferre
  -- strict thread matches above, loose matches on Subject: below --
2011-12-19  9:57 voice
2011-12-19 10:28 ` Takashi Iwai

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=4EE9F04C.6080906@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=Hong.Xu@atmel.com \
    --cc=JM.Lin@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=voice.shen@atmel.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