From: Petr Kulhavy <petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: cernekee-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/5] Sound: SOC: TAS571x: added missing register literals
Date: Wed, 30 Mar 2016 10:14:56 +0200 [thread overview]
Message-ID: <56FB8B00.4000408@barix.com> (raw)
In-Reply-To: <20160329213305.GO2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
Hi Mark,
On 29.03.2016 23:33, Mark Brown wrote:
> On Tue, Mar 29, 2016 at 09:39:34AM +0200, Petr Kulhavy wrote:
>
>> The list of TAS571x registers was incomplete.
>> Added the missing register definitions up to register 0x25
> According to the driver the device has registers up to 0xff?
That is indeed true. But from address 0x29 on (0x26 to 0x28 are
reserved) the register width varies between 20, 12 and 8 bytes, which
I'm afraid the register map is unable to represent.
>> /* device registers */
>> +#define TAS571X_CLK_CTRL_REG 0x00
>> +#define TAS571X_DEV_ID_REG 0x01
>> +#define TAS571X_ERR_STATUS_REG 0x02
>> +#define TAS571X_SYS_CTRL_1_REG 0x03
> These look like volatile registers but the device has a register cache
> and we're not adding a list of volatile registers (or readable registers
> for that matter).
That's a good point, thanks! 0x03 is a regular RW register but 0x00 to
0x02 are indeed volatile.
Is it better to make them read-only, or volatile?
Petr
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-03-30 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 7:39 [PATCH v2 1/5] Sound: SOC: TAS571x: added missing register literals Petr Kulhavy
[not found] ` <1459237178-12920-1-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-03-29 7:39 ` [PATCH v2 2/5] Sound: SOC: TAS571x: chip type detection via I2C name Petr Kulhavy
2016-03-29 7:39 ` [PATCH v2 3/5] Sound: SOC: TAS571x: implemented digital mute Petr Kulhavy
2016-03-29 7:39 ` [PATCH v2 4/5] Sound: SOC: TAS571x: added support for TAS5721 Petr Kulhavy
2016-03-29 7:39 ` [PATCH v2 5/5] dt/bindings: sound: new chip added into TAS571x binding Petr Kulhavy
[not found] ` <1459237178-12920-5-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-03-31 14:21 ` Rob Herring
2016-03-31 17:33 ` Applied "ASoC: tas571x: new chip added into TAS571x binding" to the asoc tree Mark Brown
2016-03-29 16:52 ` [PATCH v2 1/5] Sound: SOC: TAS571x: added missing register literals Mark Brown
2016-03-29 18:11 ` Kevin Cernekee
2016-03-29 21:33 ` Mark Brown
[not found] ` <20160329213305.GO2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-03-30 8:14 ` Petr Kulhavy [this message]
[not found] ` <56FB8B00.4000408-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-03-30 17:21 ` 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=56FB8B00.4000408@barix.com \
--to=petr-qh/3xlp0evwavxtiumwx3w@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=cernekee-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 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.