From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751728AbcFGCuK (ORCPT ); Mon, 6 Jun 2016 22:50:10 -0400 Received: from regular1.263xmail.com ([211.150.99.136]:41866 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750886AbcFGCuI (ORCPT ); Mon, 6 Jun 2016 22:50:08 -0400 X-263anti-spam: KSV:0;BIG:0;ABS:1;DNS:0;ATT:0;SPF:S; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ABS-CHECKED: 1 X-SKE-CHECKED: 1 X-ADDR-CHECKED: 0 X-RL-SENDER: zhengxing@rock-chips.com X-FST-TO: broonie@kernel.org X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: zhengxing@rock-chips.com X-UNIQUE-TAG: X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Message-ID: <5756363F.40208@rock-chips.com> Date: Tue, 07 Jun 2016 10:49:35 +0800 From: Xing Zheng User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1 MIME-Version: 1.0 To: Mark Brown CC: Rob Herring , linux-rockchip@lists.infradead.org, dianders@chromium.org, heiko@sntech.de, Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: [PATCH v3] ASoC: rockchip: Add machine driver for MAX98357A/RT5514/DA7219 References: <1464267742-15312-1-git-send-email-zhengxing@rock-chips.com> <20160601144542.GA3835@rob-hp-laptop> <5751912C.6080904@rock-chips.com> <20160606235026.GP7510@sirena.org.uk> In-Reply-To: <20160606235026.GP7510@sirena.org.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mark, On 2016年06月07日 07:50, Mark Brown wrote: > On Fri, Jun 03, 2016 at 10:16:12PM +0800, Xing Zheng wrote: > >> I refered to MTK's mt8173-rt5650-rt5514.txt on upstream, that compatible >> name is "mediatek,mt8173-rt5650-rt5514". >> Because our platform need to support 3 codecs (max98357a / da7219 / rt5514). >> Perhaps, you maybe feel that name is too long? And, could you please tell me >> what names would be better? >> For example: "rk3399-composite-codecs" ? > It should probably be three compatibles, one per CODEC, if the driver > needs to handle each separately. Do you mean like this: -------- sound { compatible = "rockchip,rk3399-max98357a-rt5514-da7219"; dailink-0 { compatible = "rockchip,rk3399-max98357a"; rockchip,cpu = <&i2s0>; rockchip,codec = <&max98357a>; }; dailink-1 { compatible = "rockchip,rk3399-rt5514"; rockchip,cpu = <&i2s0>; rockchip,codec = <&headsetcodec>; }; dailink-2 { compatible = "rockchip,rk3399-da7219"; rockchip,cpu = <&i2s0>; rockchip,codec = <&codec>; }; }; -------- Above, the machine drvier will handle them. Please correct me if I misunderstand. Thanks. -- - Xing Zheng