lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 15 Mar 2012 15:29:31 +0900
From:	Tomoya MORINAGA <tomoya.rohm@...il.com>
To:	Lars-Peter Clausen <lars@...afoo.de>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	alsa-devel@...a-project.org, qi.wang@...el.com,
	Takashi Iwai <tiwai@...e.de>, linux-kernel@...r.kernel.org,
	yong.y.wang@...el.com, kok.howg.ewe@...el.com,
	Liam Girdwood <lrg@...com>, joel.clark@...el.com
Subject: Re: [alsa-devel] [PATCH v6] sound/soc/codecs: add LAPIS Semiconductor ML26124

On Thu, Mar 15, 2012 at 2:40 AM, Lars-Peter Clausen <lars@...afoo.de> wrote:
> If this is for all registers, how does stuff like DAPM work, which uses the
> framework internal update_bits function?
>
> If it's the case that the write address is always read address + 1 you can
> still use the framework if you set write_flag_mask to 0x01 in your regmap
> config. In my opinion it even makes sense to shift all the register numbers
> to the left by one and use a 7/9 instead of a 8/8 addr/reg layout. This will
> reduce the amount of memory wasted due to holes in the register cache.

Thank you for your information.
I've just been investigating these.
I also found ASoC core access i2c driver via snd_soc_update_bits or others.
As a result, write register address is the same as read's.

I'll try to implement these.

BTW, currently, by settting ML26124 codec with fixed value,
I've confirmed both playback and capture work well.

thanks
-- 
ROHM Co., Ltd.
tomoya
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ