From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 082/102] ASoC: Add SOC_ENUM_SINGLE_CONST()
	and SOC_ENUM_DOUBLE_CONST() macros
Date: Thu, 20 Feb 2014 08:08:51 +0100
Message-ID: <s5heh2yxnuk.wl%tiwai@suse.de>
References: <1392724308-13375-1-git-send-email-tiwai@suse.de>
 <1392724308-13375-2-git-send-email-tiwai@suse.de>
 <20140220023339.GR2669@sirena.org.uk>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15])
 by alsa0.perex.cz (Postfix) with ESMTP id 145FB265715
 for <alsa-devel@alsa-project.org>; Thu, 20 Feb 2014 08:08:52 +0100 (CET)
In-Reply-To: <20140220023339.GR2669@sirena.org.uk>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/options/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel/>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Errors-To: alsa-devel-bounces@alsa-project.org
Sender: alsa-devel-bounces@alsa-project.org
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
List-Id: alsa-devel@alsa-project.org

At Thu, 20 Feb 2014 11:33:39 +0900,
Mark Brown wrote:
> 
> On Tue, Feb 18, 2014 at 12:51:28PM +0100, Takashi Iwai wrote:
> > Add new helper macros for defining the enum elements with a constant
> > array.  With these macros, redundant ARRAY_SIZE() can be removed in
> > the code.
> 
> So, this doesn't seem like the best way to do things.  For one thing
> it's not really that the arrays are const, it's the fact that they are a
> fixed size that makes the difference with these macros.  An array where
> we fill in a fixed number of strings at runtime would work just as well
> for this.

Hm, in theory, yes.  I thought of _FIXED instead of _CONST, too, but
the former sounds also obscure, so I picked the latter in the end.

>  I'd also expect this to be more what the default naming does
> since we want to try to steer people towards using the simplest and
> least error prone mechanism for doing this.

If changing the existing API is fine for you (not adding the new one),
it's trivial to convert the patches to do so.  Looking at the end
result, all SOC_ENUM_SINGLE() and SOC_ENUM_DOUBLE() usages are
covered.  For any specific usage in future, we may provide lowlevel
macros, __SOC_ENUM_SINGLE() with the number of items, too.


Takashi