From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Nikula Subject: Re: [PATCH 3/3] ASoC: tlv320aic3x: Complete the soc-cache conversion Date: Tue, 14 Sep 2010 15:14:45 +0300 Message-ID: <20100914151445.2fe7fd54.jhnikula@gmail.com> References: <1284465289-4865-1-git-send-email-jhnikula@gmail.com> <1284465289-4865-3-git-send-email-jhnikula@gmail.com> <20100914120458.GE27029@rakim.wolfsonmicro.main> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ey0-f179.google.com (mail-ey0-f179.google.com [209.85.215.179]) by alsa0.perex.cz (Postfix) with ESMTP id 3CFAF10387C for ; Tue, 14 Sep 2010 14:14:49 +0200 (CEST) Received: by eye27 with SMTP id 27so2019322eye.38 for ; Tue, 14 Sep 2010 05:14:48 -0700 (PDT) In-Reply-To: <20100914120458.GE27029@rakim.wolfsonmicro.main> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: alsa-devel@alsa-project.org, Liam Girdwood List-Id: alsa-devel@alsa-project.org On Tue, 14 Sep 2010 13:04:58 +0100 Mark Brown wrote: > On Tue, Sep 14, 2010 at 02:54:49PM +0300, Jarkko Nikula wrote: > > Complete the phasing out of aic3x_read_reg_cache, aic3x_write_reg_cache, > > aic3x_read and aic3x_write calls. > > > > This patch replaces the aic3x_read with codec->hw_read that points to a > > function implemented by soc-cache. There is no need to cache the value from > > chip since the functions using aic3x_read are interested only read-only > > bits. > > > > Signed-off-by: Jarkko Nikula > > It'd be a bit nicer to do this by using snd_soc_read() here also and > marking the registers as volatile. This makes the process much less > error prone since users can just use snd_soc_read() and the register > cache code will work out if it needs to go to the chip or not. Actually I looked that but problem with aic3x is that most of the volatile bits are with r/w configuration bits in the same registers. There are a few completely volatile read-only registers but currently there is no use for them. -- Jarkko