From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH v3 2/8] ASoC: da7210: Add support for DAPM Date: Wed, 19 Oct 2011 13:13:41 +0100 Message-ID: <20111019121341.GE3107@opensource.wolfsonmicro.com> References: <1318590098.12107.509.camel@matrix> <20111014192008.GD2931@opensource.wolfsonmicro.com> <1318666803.613.21.camel@matrix> <20111017214107.GC5200@opensource.wolfsonmicro.com> <1319008895.7230.11.camel@matrix> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 6B7862455F for ; Wed, 19 Oct 2011 14:13:43 +0200 (CEST) Content-Disposition: inline In-Reply-To: <1319008895.7230.11.camel@matrix> 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: Ashish Chavan Cc: linux-kernel , alsa-devel , lrg , "kuninori.morimoto.gx" , David Dajun Chen List-Id: alsa-devel@alsa-project.org On Wed, Oct 19, 2011 at 12:51:35PM +0530, Ashish Chavan wrote: > BTW if in case, hardware designers reiterate to use STANDBY registers, > will it suffice to only document this somewhere is the source? The main thing is to make sure that the code is understandable and doesn't look buggy to visual inspection so yes, if there's adequate documentation that would be OK. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756036Ab1JSMNo (ORCPT ); Wed, 19 Oct 2011 08:13:44 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:46928 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754377Ab1JSMNn (ORCPT ); Wed, 19 Oct 2011 08:13:43 -0400 Date: Wed, 19 Oct 2011 13:13:41 +0100 From: Mark Brown To: Ashish Chavan Cc: lrg , alsa-devel , David Dajun Chen , "kuninori.morimoto.gx" , linux-kernel Subject: Re: [alsa-devel] [PATCH v3 2/8] ASoC: da7210: Add support for DAPM Message-ID: <20111019121341.GE3107@opensource.wolfsonmicro.com> References: <1318590098.12107.509.camel@matrix> <20111014192008.GD2931@opensource.wolfsonmicro.com> <1318666803.613.21.camel@matrix> <20111017214107.GC5200@opensource.wolfsonmicro.com> <1319008895.7230.11.camel@matrix> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1319008895.7230.11.camel@matrix> X-Cookie: Big book, big bore. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 19, 2011 at 12:51:35PM +0530, Ashish Chavan wrote: > BTW if in case, hardware designers reiterate to use STANDBY registers, > will it suffice to only document this somewhere is the source? The main thing is to make sure that the code is understandable and doesn't look buggy to visual inspection so yes, if there's adequate documentation that would be OK.