From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 34BBDCA9EB0 for ; Sun, 3 Nov 2019 23:20:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E546A205C9 for ; Sun, 3 Nov 2019 23:20:07 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="vYEVAhXl" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728157AbfKCXUH (ORCPT ); Sun, 3 Nov 2019 18:20:07 -0500 Received: from mail-lj1-f196.google.com ([209.85.208.196]:38987 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728059AbfKCXUH (ORCPT ); Sun, 3 Nov 2019 18:20:07 -0500 Received: by mail-lj1-f196.google.com with SMTP id y3so15592426ljj.6 for ; Sun, 03 Nov 2019 15:20:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iVpcN1vOdXs3wwhH+wrUa3RKCmoO3R8+a8ZB0f/AmFQ=; b=vYEVAhXlokOFcchNfSd+V2JmCbFdTJYbvhwaDedCzoFLvtj/YDjkH2J6fS4zy3hjCY qefgD/I7cMWurxOGbXoJERkCxJIgrE516+LJyYBlUqFQrh0cJ84nEZwuVoNtZ5ZUPPpO mqmECtStI09hzbCh3jYmpXbJCQMvbPG/TPUhiJ+MzdvIPR6xxCQWdjTArl89XE7eGWxI DCsqV9f8aY3E/lAXiwf4vcPC++iSRJ/SXB8nGa3e8MuJS56vcsrNGIUfEB6rBK1p/IRe UD5a/66390jHlTwMpnaM0AV/1fXQrM8Ulp6eCpL5FASsHrfuoLzHf8CjkyGG0Sp3zbZ+ AIxA== 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=iVpcN1vOdXs3wwhH+wrUa3RKCmoO3R8+a8ZB0f/AmFQ=; b=Zm39xiFGG8YYp/lAf1X30HPmJwvA4cS+66THm56aA+WJqF2bcJygYSwd9kjr0QWtPE LdXyJdC1cfdX2Z65cXBfWnJKb0yMPPvlfifq1Db9N1M0FpUIhwGjh/3cMyHdd7JMSyW1 vJ+39PZP7l4nmuSUTSot0iQeSWyl1VAtsQUeqywxghlaIv/+JQV+m8ODvRBfHmFK69vK Lu8T8SHAmhBhO+G7/MygoC84f7um6mItX7j1E0uws8P4nbb5geOe8/TwJBUQ0HrHOcrL OdMDGPQFtQCEsDIcdFgo0vs5xxZyv3vKqqIxipvTnC4okJsS6Tyj8CMQx9GYUw9vmVF7 Q72A== X-Gm-Message-State: APjAAAVIkD8+pArjXQthPH4NNRx3MGDdwk6AyKmP5rP4qq1GswnO53zG ZhXF/RPa5iF7ssOCjCSsp0PZi9MeRwXNwDiptW8hWg== X-Google-Smtp-Source: APXvYqxTxFkdLmpGie3z+n1NoTiUXGL0EZTOt83bLBNwDXdy7iOJZES3zs0O3WqyGV8LxjgkqUR638pDafjAOULX0gI= X-Received: by 2002:a2e:a0c9:: with SMTP id f9mr16639653ljm.77.1572823204990; Sun, 03 Nov 2019 15:20:04 -0800 (PST) MIME-Version: 1.0 References: <20191029112700.14548-1-srinivas.kandagatla@linaro.org> <20191029112700.14548-9-srinivas.kandagatla@linaro.org> In-Reply-To: <20191029112700.14548-9-srinivas.kandagatla@linaro.org> From: Linus Walleij Date: Mon, 4 Nov 2019 00:19:51 +0100 Message-ID: Subject: Re: [PATCH v3 08/11] dt-bindings: pinctrl: qcom-wcd934x: Add bindings for gpio To: Srinivas Kandagatla Cc: Rob Herring , Mark Brown , Lee Jones , vinod.koul@linaro.org, "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , spapothi@codeaurora.org, bgoswami@codeaurora.org, "open list:GPIO SUBSYSTEM" Content-Type: text/plain; charset="UTF-8" Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Tue, Oct 29, 2019 at 12:29 PM Srinivas Kandagatla wrote: > Qualcomm Technologies Inc WCD9340/WCD9341 Audio Codec has integrated > gpio controller to control 5 gpios on the chip. This patch adds > required device tree bindings for it. > > Signed-off-by: Srinivas Kandagatla > --- > .../pinctrl/qcom,wcd934x-pinctrl.yaml | 52 +++++++++++++++++++ The bindings look OK, but remind me if I have asked before (sorry then) does these GPIOs expose some pin control properties and that is why the driver is placed under pin control rather than the GPIO namespace? Sorry if this is something I asked before, I just get too much mail. Yours, Linus Walleij From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 03241CA9EB0 for ; Sun, 3 Nov 2019 23:21:05 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id F04B8205C9 for ; Sun, 3 Nov 2019 23:21:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="cq/3E3xO"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="vYEVAhXl" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F04B8205C9 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 7E5E516A4; Mon, 4 Nov 2019 00:20:11 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 7E5E516A4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1572823261; bh=IiRNq7lvu3GhNFtQcBn1sQyCmV+4HrnJHCy0xmkW7k4=; h=References:In-Reply-To:From:Date:To:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=cq/3E3xOTE2Vq8QHNkN+0UBzjagtCzDYa/+0qE8OysUNDr8nx+CSPjfdpndPQwR9J 9LSYjHprEXsmmcxqhLvy5th3pnietNkC3RPKaADiqKmLZIxbCcbOAdBSsNEgmUvCzy 6OX3aymZnK1xLZoyRfHc2z3FaBqXB6hDopYh55eI= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 03317F80446; Mon, 4 Nov 2019 00:20:10 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 21C5DF80535; Mon, 4 Nov 2019 00:20:09 +0100 (CET) Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 33A36F8014A for ; Mon, 4 Nov 2019 00:20:05 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 33A36F8014A Authentication-Results: alsa1.perex.cz; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="vYEVAhXl" Received: by mail-lj1-x242.google.com with SMTP id y23so4677775ljh.10 for ; Sun, 03 Nov 2019 15:20:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iVpcN1vOdXs3wwhH+wrUa3RKCmoO3R8+a8ZB0f/AmFQ=; b=vYEVAhXlokOFcchNfSd+V2JmCbFdTJYbvhwaDedCzoFLvtj/YDjkH2J6fS4zy3hjCY qefgD/I7cMWurxOGbXoJERkCxJIgrE516+LJyYBlUqFQrh0cJ84nEZwuVoNtZ5ZUPPpO mqmECtStI09hzbCh3jYmpXbJCQMvbPG/TPUhiJ+MzdvIPR6xxCQWdjTArl89XE7eGWxI DCsqV9f8aY3E/lAXiwf4vcPC++iSRJ/SXB8nGa3e8MuJS56vcsrNGIUfEB6rBK1p/IRe UD5a/66390jHlTwMpnaM0AV/1fXQrM8Ulp6eCpL5FASsHrfuoLzHf8CjkyGG0Sp3zbZ+ AIxA== 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=iVpcN1vOdXs3wwhH+wrUa3RKCmoO3R8+a8ZB0f/AmFQ=; b=NqVBWWvyHMda1ivxpgfw1GNhW1dooM4qk6bOFzmMjS2ivloL7ZW40frjE9VBZoxXRw Xd7apnZr0PgR5zYQ7hOvwQo+N9+N78/68pEWaRMzWVmwGcKQ5/neuZYtGOTSf2b1zjRM gtP15i8+JKYw8basKiH1HSnO3xvi8Ep2NpmLyBD75SPcPkc5b+XoKkRMNV18RAItTARo 1u+ffdvtEOKrDOZyJgTs97N4juCYm51vd+iP0ygf87xBsGK5c4+oWntQ3eA4VgwznpND NbRuwWO+94qGSNjmMs5XT9VQctYcjY5rdQ4ywIw/7pAHOd3bVQCp7P7Iq95BhIXKLxAy FDjQ== X-Gm-Message-State: APjAAAVppQKcBBGoNVtJcJPpKby6pvALqHoJbxW2k3fB5RJSAoAVwfPU aAUouQ3MIRYJJ+XFr87ialJYo6y6QfitNQem3UIFow== X-Google-Smtp-Source: APXvYqxTxFkdLmpGie3z+n1NoTiUXGL0EZTOt83bLBNwDXdy7iOJZES3zs0O3WqyGV8LxjgkqUR638pDafjAOULX0gI= X-Received: by 2002:a2e:a0c9:: with SMTP id f9mr16639653ljm.77.1572823204990; Sun, 03 Nov 2019 15:20:04 -0800 (PST) MIME-Version: 1.0 References: <20191029112700.14548-1-srinivas.kandagatla@linaro.org> <20191029112700.14548-9-srinivas.kandagatla@linaro.org> In-Reply-To: <20191029112700.14548-9-srinivas.kandagatla@linaro.org> From: Linus Walleij Date: Mon, 4 Nov 2019 00:19:51 +0100 Message-ID: To: Srinivas Kandagatla Cc: Rob Herring , "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." , bgoswami@codeaurora.org, vinod.koul@linaro.org, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , spapothi@codeaurora.org, "linux-kernel@vger.kernel.org" , "open list:GPIO SUBSYSTEM" , Mark Brown , Lee Jones Subject: Re: [alsa-devel] [PATCH v3 08/11] dt-bindings: pinctrl: qcom-wcd934x: Add bindings for gpio X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Tue, Oct 29, 2019 at 12:29 PM Srinivas Kandagatla wrote: > Qualcomm Technologies Inc WCD9340/WCD9341 Audio Codec has integrated > gpio controller to control 5 gpios on the chip. This patch adds > required device tree bindings for it. > > Signed-off-by: Srinivas Kandagatla > --- > .../pinctrl/qcom,wcd934x-pinctrl.yaml | 52 +++++++++++++++++++ The bindings look OK, but remind me if I have asked before (sorry then) does these GPIOs expose some pin control properties and that is why the driver is placed under pin control rather than the GPIO namespace? Sorry if this is something I asked before, I just get too much mail. Yours, Linus Walleij _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel