From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH RFT] ASoC: wm8904: Make undocumented registers non-readable
Date: Tue, 20 Oct 2015 10:20:49 +0100 [thread overview]
Message-ID: <20151020092049.GC10520@ck-lbox> (raw)
In-Reply-To: <1445051470.3014.1.camel@ingics.com>
On Sat, Oct 17, 2015 at 11:11:10AM +0800, Axel Lin wrote:
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> I think the intention of wm8904_readable_register is to return false for
> undocumented registers, but current code returns true for all cases in
> wm8904_readable_register.
> Please review if this patch is correct or not.
> Thanks.
Ok so I have been through every register access in the driver
(yes that was a bit boring) and it looks like the driver only
accesses a register that isn't marked as readable once. But this
looks to be a bug. WM8904_EQ_REGS is set to 25, but there are
only 24 registers in the EQ. This appears to be a mistake caused
by the fact the registers start numbering from 1 rather than 0. I
will send a patch to fix this small bug and this patch looks fine
to me:
Reviewed-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Unfortunately I don't have hardware to test the patch, but I have
reviewed it pretty carefully and am happy.
Thanks,
Charles
next prev parent reply other threads:[~2015-10-20 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 3:11 [PATCH RFT] ASoC: wm8904: Make undocumented registers non-readable Axel Lin
2015-10-20 9:20 ` Charles Keepax [this message]
2015-11-18 18:09 ` Applied "ASoC: wm8904: Make undocumented registers non-readable" to the asoc tree 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=20151020092049.GC10520@ck-lbox \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.