Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp179106pxk; Wed, 9 Sep 2020 02:27:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz/x7eejcIlGn9p+H4T+AIiPgs2FthhS707sa61snDi3ggpt2VVfTekY9DmtUfP48/EGE3y X-Received: by 2002:a50:d802:: with SMTP id o2mr3240540edj.152.1599643646220; Wed, 09 Sep 2020 02:27:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599643646; cv=none; d=google.com; s=arc-20160816; b=ApViROeVgW+ycGml43j1SseWoYhNpZSm7dI/NfGqMx9cbEU+qtH2kpwC5EJjfC93N1 XFK77FXwK8R9wD+Y3wyhlAulXikgGw8ZHWCnreWV6nG6m6/P+n/YMeV+PWDh/XH01aBm +cRNaNuQ+4oGaqiO6FmQoMFSXeFJzzLZSPMf4XC8DMHBrl/v0aMCPZDZtA6LO9QRUd4U Zt8hKElWnkGrwQGJAaHiFdWYCQFrBiVy8CMyxb1TIiPnYm8ZV+gwBSVszcYG9l+fQxk+ RjwNloLDAAvHRF7sqBEHWQ5l8FDOVHARaihim5Dwe29LVR387VykzQflQOVc5iZ2xuch i2KQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=AmAjr6xvyauDkIBPHoJreMuavbYPMqoWr9WPQMiNPkg=; b=AC6Vh2ypBVmAbYRkbsVhrHzUzAMITf42F9KJEOyxJq0bUYXOvm/XMMlt0DKU3RauvB SOMPeGpc/ivJZa1t44+FMulyzi1sS4znxB/jnLwxVY3nipy0ykMfkYTGq4+yC1nLUxuR hMXRPPjPUJq8FcHsThRXGsDeYARhSn74XH2QITv5AAx3jzxulEqnEnvIdcz/YKx48grs hMEJHuvPpGPaLijyjQrVMwRVc4QvTG2Ae9XhOdKzqRjFcIWUq4Wo6wALW7PLTZ7sHTZY 3Op2WNk8KopIxvZTwErUJkPZGNv7I2cHs5v2NYQ78Tj6kowjkCZYJEo2t6cDEsqFTtKS U/OA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=lgk3l2Qh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b6si1166825eja.559.2020.09.09.02.27.03; Wed, 09 Sep 2020 02:27:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=lgk3l2Qh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729005AbgIIJYR (ORCPT + 99 others); Wed, 9 Sep 2020 05:24:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726414AbgIIJYM (ORCPT ); Wed, 9 Sep 2020 05:24:12 -0400 Received: from mail-wm1-x343.google.com (mail-wm1-x343.google.com [IPv6:2a00:1450:4864:20::343]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CE46DC061573 for ; Wed, 9 Sep 2020 02:24:11 -0700 (PDT) Received: by mail-wm1-x343.google.com with SMTP id q9so1573226wmj.2 for ; Wed, 09 Sep 2020 02:24:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AmAjr6xvyauDkIBPHoJreMuavbYPMqoWr9WPQMiNPkg=; b=lgk3l2QheCZRIdB/DXYePwXEoUJvYOIpV83Gh1pRZ2BYhkcAj5c3ogzbaLtFuFI9ts jpGHnH6HqqegvOnM9Uqug7F1IJiuwk+eek3yWSn2ufF9Y+cYzVYdiFc0zs3ZtTMRf5cM XT5LclUiUzG/7eZUxr9lBGgyThOWt8HJEhlvI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AmAjr6xvyauDkIBPHoJreMuavbYPMqoWr9WPQMiNPkg=; b=RbwWuCez4mX9LCEMu3qkz3R27TLtqOp6vAM8Y3kNloj9l4R8BayL+XU8WN3dY6wA2v HboieTR8zHu+F5TgTVj2c9Yj/unJ+O1Lk6NCfEcR9ElWwHtrHPj/iaOsAKE0oX2p1WOb bkyggFN33yXrEetVkOvXzw5BXjubJSxsg8PHktCIKkiCY9B01q1oQkGEKdubR/ctgr0I 04NGmgKO02a7JgJ74fJlPA5V+Hgy7vf9LVNur6QEB9BhgjMAFRXktFv32a+8JcdayV3D OAMITi+WNE7cLpAtClcG4WBX4MnNO0kkm20o3A0jk2ththu0WjRRl3qggCUav1TDHwRS XBYw== X-Gm-Message-State: AOAM533YHzG9Wh/DP7+Zcu514hIAmhgZ1Wjj0SXVFNwHjkzrx4mZuXDH q2t8wYqSc3bobuVhqfDsOsbrCncOosUQB++jAt0tsg== X-Received: by 2002:a7b:c3c8:: with SMTP id t8mr2599038wmj.101.1599643450162; Wed, 09 Sep 2020 02:24:10 -0700 (PDT) MIME-Version: 1.0 References: <20200907100039.1731457-1-cychiang@chromium.org> <20200907100039.1731457-3-cychiang@chromium.org> <20200908203357.GA861143@bogus> In-Reply-To: <20200908203357.GA861143@bogus> From: Cheng-yi Chiang Date: Wed, 9 Sep 2020 17:23:43 +0800 Message-ID: Subject: Re: [PATCH v7 2/3] ASoC: qcom: dt-bindings: Add sc7180 machine bindings To: Rob Herring Cc: linux-kernel , Mark Brown , Taniya Das , Rohit kumar , Banajit Goswami , Patrick Lai , Andy Gross , Bjorn Andersson , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , Srini Kandagatla , Stephan Gerhold , Matthias Brugger , Heiko Stuebner , Doug Anderson , Dylan Reid , Tzung-Bi Shih , Linux ARM , linux-arm-msm , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." , linux-mediatek@lists.infradead.org, linux-rockchip@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 9, 2020 at 4:34 AM Rob Herring wrote: > > On Mon, Sep 07, 2020 at 06:00:38PM +0800, Cheng-Yi Chiang wrote: > > Add devicetree bindings documentation file for sc7180 sound card. > > > > Signed-off-by: Cheng-Yi Chiang > > --- > > .../bindings/sound/qcom,sc7180.yaml | 143 ++++++++++++++++++ > > 1 file changed, 143 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/sound/qcom,sc7180.yaml > > > > diff --git a/Documentation/devicetree/bindings/sound/qcom,sc7180.yaml b/Documentation/devicetree/bindings/sound/qcom,sc7180.yaml > > new file mode 100644 > > index 000000000000..ae809346ca80 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/sound/qcom,sc7180.yaml > > @@ -0,0 +1,143 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/sound/qcom,sc7180.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Qualcomm Technologies Inc. SC7180 ASoC sound card driver > > + > > +maintainers: > > + - Rohit kumar > > + - Cheng-Yi Chiang > > + > > +description: > > + This binding describes the SC7180 sound card which uses LPASS for audio. > > + > > +properties: > > + compatible: > > + const: qcom,sc7180-sndcard > > + > > + audio-routing: > > + $ref: /schemas/types.yaml#/definitions/non-unique-string-array > > + description: > > + A list of the connections between audio components. Each entry is a > > + pair of strings, the first being the connection's sink, the second > > + being the connection's source. > > + > > + model: > > + $ref: /schemas/types.yaml#/definitions/string > > + description: User specified audio sound card name > > + > > + headset-jack: > > + $ref: /schemas/types.yaml#/definitions/phandle > > + description: phandle of the codec for headset detection > > + > > + hdmi-jack: > > + $ref: /schemas/types.yaml#/definitions/phandle > > + description: phandle of the codec for hdmi jack detection > > You already have links to these devices. Why duplicate it here? > > What if you had 2 headsets? This doesn't scale. > Hi Rob, thanks for reviewing. There was some discussion in https://patchwork.kernel.org/patch/11737905/#23571643 about how to specify the dailink that has a headset jack. I would like to pass the information of headset jack and hdmi jack to the machine driver so the machine driver can call snd_soc_component_set_jack to set jack when init the corresponding link. Headset jack and hdmi jack will be treated differently for button and event type. Because of this, we can not just set a property "jack" in the link. As for the 2 headsets case (I guess you mean hp jack and mic jack), on this board we will not have this use case. If someone really wants to build hp jack and mic jack on the board based on this machine driver, we can add two more property hp-jack and mic-jack to specify that, as the machine driver will need to know the different jack types anyway. What do you think ? Or could you please suggest a proper way to pass such information ? Thanks! > > Rob