From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965129AbbBBVIk (ORCPT ); Mon, 2 Feb 2015 16:08:40 -0500 Received: from avon.wwwdotorg.org ([70.85.31.133]:53528 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754884AbbBBVIi (ORCPT ); Mon, 2 Feb 2015 16:08:38 -0500 Message-ID: <54CFE754.7000500@wwwdotorg.org> Date: Mon, 02 Feb 2015 14:08:36 -0700 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Tomeu Vizoso , linux-kernel@vger.kernel.org CC: Javier Martinez Canillas , Dylan Reid , Andrew Bresticker , Simon Glass , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Thierry Reding , Alexandre Courbot , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-tegra@vger.kernel.org Subject: Re: [PATCH v3 01/10] ARM: tegra: Set the sound card model that alsaucm expects References: <1422442278-10405-1-git-send-email-tomeu.vizoso@collabora.com> <1422442278-10405-2-git-send-email-tomeu.vizoso@collabora.com> In-Reply-To: <1422442278-10405-2-git-send-email-tomeu.vizoso@collabora.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/28/2015 03:50 AM, Tomeu Vizoso wrote: > Patches are on its way to add a config file to alsaucm for the Nyan > boards. Use the same card ID that alsaucm will expect. > diff --git a/arch/arm/boot/dts/tegra124-nyan-big.dts b/arch/arm/boot/dts/tegra124-nyan-big.dts > sound { > - compatible = "nvidia,tegra-audio-max98090-nyan-big", > + compatible = "nvidia,tegra-audio-max98090-nyan", > "nvidia,tegra-audio-max98090"; I'm not convinced that removing the board-specific compatible value is a great idea. What if we find we need to distinguish between different boards that use this same binding in the future. That situation is exactly why we have board-/SoC-specific values in compatible even if we don't immediately use them. > - nvidia,model = "Acer Chromebook 13"; > + nvidia,model = "GoogleNyan"; I believe this also technically breaks ABI, since some user-space tools use the model to look up saved state. Can we not leave this as is, and just have the UCM files know about both names? Aside from that, I think the series looks OK at a quick glance.