From: "Andrew F. Davis" <afd@ti.com>
To: Andreas Dannenberg <dannenberg@ti.com>, Mark Brown <broonie@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
Stephane Le Provost <stephane.leprovost@mediatek.com>
Subject: Re: [PATCH] ASoC: pcm186x: Fix device reset-registers trigger value
Date: Thu, 15 Nov 2018 11:08:33 -0600 [thread overview]
Message-ID: <a7db24e0-94fe-7875-c4a6-84d739ac185b@ti.com> (raw)
In-Reply-To: <20181115170131.1839-1-dannenberg@ti.com>
On 11/15/18 11:01 AM, Andreas Dannenberg wrote:
> According to the current device datasheet (TI Lit # SLAS831D, revised
> March 2018) the value written to the device's PAGE register to trigger
> a complete register reset should be 0xfe, not 0xff. So go ahead and
> update to the correct value.
>
> Reported-by: Stephane Le Provost <stephane.leprovost@mediatek.com>
> Tested-by: Stephane Le Provost <stephane.leprovost@mediatek.com>
> Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
> ---
Does 0xff not reset the device? If so then this is not just a typo but a
bug and this patch should have a fixes tag. Either way:
Acked-by: Andrew F. Davis <afd@ti.com>
> sound/soc/codecs/pcm186x.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/codecs/pcm186x.h b/sound/soc/codecs/pcm186x.h
> index 2c6ba55bf394..bb3f0c42a1cd 100644
> --- a/sound/soc/codecs/pcm186x.h
> +++ b/sound/soc/codecs/pcm186x.h
> @@ -139,7 +139,7 @@ enum pcm186x_type {
> #define PCM186X_MAX_REGISTER PCM186X_CURR_TRIM_CTRL
>
> /* PCM186X_PAGE */
> -#define PCM186X_RESET 0xff
> +#define PCM186X_RESET 0xfe
>
> /* PCM186X_ADCX_INPUT_SEL_X */
> #define PCM186X_ADC_INPUT_SEL_POL BIT(7)
>
prev parent reply other threads:[~2018-11-15 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 17:01 Andreas Dannenberg
2018-11-15 17:08 ` Andrew F. Davis [this message]
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=a7db24e0-94fe-7875-c4a6-84d739ac185b@ti.com \
--to=afd@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dannenberg@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stephane.leprovost@mediatek.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
all inboxes | Powered by JetHome®