All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Hsu <KCHSU0@nuvoton.com>
To: Mark Brown <broonie@kernel.org>
Cc: YHCHuang@nuvoton.com, alsa-devel@alsa-project.org,
	CTLIN0@nuvoton.com, lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: nau8810: Add driver for Nuvoton codec chip NAU88C10
Date: Mon, 8 Aug 2016 10:27:38 +0800	[thread overview]
Message-ID: <57A7EE1A.1040307@nuvoton.com> (raw)
In-Reply-To: <20160805120804.GV10383@sirena.org.uk>

Hi

On 8/5/2016 8:08 PM, Mark Brown wrote:
> On Mon, Jul 04, 2016 at 11:34:19AM +0800, John Hsu wrote:
>   
>> On 7/1/2016 6:04 PM, Mark Brown wrote:
>>     
>
>   
>>> No, you don't - this is entirely normal for 7x9 regmaps, I've never seen
>>> such a device that supported readback.  Look at devices like wm8731 for
>>> examples.
>>>       
>
>   
>> Sometimes, we need to know the codec information and need read it
>> from hardware, not cache. I'm afraid that it can't be done in this
>> case.
>>     
>
> What does the read actually look like on this device?
>   

The data read from codec by the IIC bus is as the following.
0 0 0 0 0 0 0 D8 ACK D7 D6 D5 D4 D3 D2 D1 D0
The bottom 9 bits are the real register value. The nau8810_reg_read
in driver is made by the formate.

  reply	other threads:[~2016-08-08  2:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  8:40 [PATCH] ASoC: nau8810: Add driver for Nuvoton codec chip NAU88C10 John Hsu
2016-06-27 17:15 ` Mark Brown
2016-07-01  3:34   ` John Hsu
2016-07-01 10:04     ` Mark Brown
2016-07-04  3:34       ` John Hsu
2016-08-05 12:08         ` Mark Brown
2016-08-08  2:27           ` John Hsu [this message]
2016-08-08 15:18             ` Mark Brown
2016-08-09  2:09               ` John Hsu
  -- strict thread matches above, loose matches on Subject: below --
2016-08-15  9:02 John Hsu
2016-08-15 14:06 ` Mark Brown
2016-08-16  3:57   ` John Hsu
2016-08-16 10:38     ` Mark Brown
2016-08-17  0:34       ` John Hsu
2016-08-17  9:42         ` Mark Brown
2016-08-18  1:04           ` John Hsu
2016-08-18 18:24             ` Mark Brown
2016-08-19  2:51               ` John Hsu
2016-08-19  9:24 John Hsu

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=57A7EE1A.1040307@nuvoton.com \
    --to=kchsu0@nuvoton.com \
    --cc=CTLIN0@nuvoton.com \
    --cc=YHCHuang@nuvoton.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.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.