Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751366AbeACTt0 (ORCPT + 1 other); Wed, 3 Jan 2018 14:49:26 -0500 Received: from mail-pl0-f41.google.com ([209.85.160.41]:44985 "EHLO mail-pl0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751268AbeACTtY (ORCPT ); Wed, 3 Jan 2018 14:49:24 -0500 X-Google-Smtp-Source: ACJfBotihe2l6GoljROKDL/rUiYuFT9/h7RS6+3kEnKZb0Lh8BL6349ofxE8+ZUONg2SZe5V0qwe2Q== Date: Wed, 3 Jan 2018 11:49:20 -0800 From: Bjorn Andersson To: Srinivas Kandagatla Cc: Andy Gross , Mark Brown , linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org, David Brown , Rob Herring , Mark Rutland , Liam Girdwood , Patrick Lai , Banajit Goswami , Jaroslav Kysela , Takashi Iwai , linux-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, sboyd@codeaurora.org Subject: Re: [RESEND PATCH v2 13/15] dt-bindings: sound: qcom: Add devicetree bindings for apq8096 Message-ID: <20180103194920.GA478@tuxbook> References: <20171214173402.19074-1-srinivas.kandagatla@linaro.org> <20171214173402.19074-14-srinivas.kandagatla@linaro.org> <20180103002835.GW478@tuxbook> <787ecdc5-66d8-23ee-7136-2a8759c86536@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <787ecdc5-66d8-23ee-7136-2a8759c86536@linaro.org> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Wed 03 Jan 08:27 PST 2018, Srinivas Kandagatla wrote: > > > On 03/01/18 00:28, Bjorn Andersson wrote: > > On Thu 14 Dec 09:34 PST 2017, srinivas.kandagatla@linaro.org wrote: > > > > > +++ b/Documentation/devicetree/bindings/sound/qcom,apq8096.txt > > > > Wouldn't it be possible to describe all(?) qdsp based machines in this > > one document? I.e. should we name it a little bit more generic? > > You mean like downstream ? > I mean that I'm guessing that apq8084, msm8994, msm8998 etc would come with the same binding document, but a different compatible. This is fine for now though, we can always rename the file and reword the description later. Regards, Bjorn