Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp1150256ybx; Tue, 5 Nov 2019 11:11:14 -0800 (PST) X-Google-Smtp-Source: APXvYqyPBIjmLUrguGG+1iPkYvzYP+G20AGxQA2ckdHT4ngyOMFndf0ea7Ss+N5KnTYEh67G3PxZ X-Received: by 2002:a17:906:70e:: with SMTP id y14mr14143997ejb.70.1572981074413; Tue, 05 Nov 2019 11:11:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572981074; cv=none; d=google.com; s=arc-20160816; b=bZFtZrzfUeQyhPDUadxUVXRXMy2JUBWQ9UuWWERF13dYr0gN6GePANMS+psastfp/w dA2UyKzPDt2wpBz00rAfiKt7/HlbwObmJEqZkNEFxNXu0ZyeD1Zs6rID2M8WFQlUMlSL 5ZKmx4pIfSUQV5vmxamfHiWOzeVl5NjQNpA5YwDCg4gf0sUz1tgUl9lgBVsLAW0/oELY ugn0Js1UHdNZaU0XwFGFEbYQmyQZIlHkuTZLXk16ifh0gGAhQ1aLA6uovw80em8IQAbA C9hRFTmclRXEZM63f1YnMmpMVsJtDIWhU8bfLfhZX8c+hbSRPnuNDIfUSi5GgjYeiRGf dVNg== 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=cE1TOwo1gMk9rb3DHiBX3TexI1B9FHfjAexiYuwoYrE=; b=Iknla3fdtAXfMLU9w1AzwHQX/APIH/lxFdPXGy9pnjPgCTlRDhISuLi/qmUNk5n6Dq KObqYckGmwibraGaVKyITLqL+JFgc3ALFqOYMfzWN9W0feGgt1+dUAYPCvvxQngT7w3l 7jh5vZ99dD/azRQL7BWpMZhYJDD2N50EvFXS8G+5I12e/NBqDJr3HvodX1ZAN9us9k1t Blk3gVrZMXRFei34TSXX0nmIqpl8sIVnZq1JTfxmXPWvTKjLfE1wIDadeF1Qo9obTOYw fwblKrLON3ZVnzNFnPyGWbMyENBmJHMt4M5gaYexlGYPxL2jee0+CUx4GgyJ6jWmOsOA vaXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=A4Pyc+ti; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id nq5si3075653ejb.161.2019.11.05.11.10.49; Tue, 05 Nov 2019 11:11:14 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=A4Pyc+ti; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390937AbfKETIy (ORCPT + 99 others); Tue, 5 Nov 2019 14:08:54 -0500 Received: from mail.kernel.org ([198.145.29.99]:45838 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390709AbfKETIy (ORCPT ); Tue, 5 Nov 2019 14:08:54 -0500 Received: from mail-qv1-f51.google.com (mail-qv1-f51.google.com [209.85.219.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DF3EC21929; Tue, 5 Nov 2019 19:08:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1572980933; bh=OXmBdFlRHFjSKG93l0PdhfI6GDLFZkT6/eylL4O2BLY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=A4Pyc+titsh2MV21obxyJRFvEjTVhzZVdWlofZbm9ErJqczl1aSdsxzH2xh1K5BrT RQi8cmmYa3bBydJXKkGV83IkSwxjUqGwYyAs11LfD/Y4+MXMyC2wo0/rIObZ9L+ZMd 64yEhJSyMdmn41WGoUwlTmPIbBRE864pCWHECsig= Received: by mail-qv1-f51.google.com with SMTP id w11so366527qvu.13; Tue, 05 Nov 2019 11:08:52 -0800 (PST) X-Gm-Message-State: APjAAAVrpJ1quM72a6Siy0L9B1jQla1F1470E+9A20OrTnKHjkeWPmzI jkrlQJtPCEuN4/yuLoRaa13wjhgl/VeIAvUzlg== X-Received: by 2002:a0c:ca06:: with SMTP id c6mr10688316qvk.136.1572980931880; Tue, 05 Nov 2019 11:08:51 -0800 (PST) MIME-Version: 1.0 References: <20191018001849.27205-1-srinivas.kandagatla@linaro.org> <20191018001849.27205-2-srinivas.kandagatla@linaro.org> <20191025204338.GA25892@bogus> <90b2d83b-f2b2-3a5d-4deb-589f4b48b208@linaro.org> <371955d9-ad2d-5ddc-31b4-710729feae42@linaro.org> <7811be04-dfda-5953-110c-bca685fdcaa4@linaro.org> In-Reply-To: <7811be04-dfda-5953-110c-bca685fdcaa4@linaro.org> From: Rob Herring Date: Tue, 5 Nov 2019 13:08:40 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 01/11] ASoC: dt-bindings: add dt bindings for WCD9340/WCD9341 audio codec To: Srinivas Kandagatla Cc: Mark Brown , Linus Walleij , Lee Jones , Vinod Koul , Linux-ALSA , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , spapothi@codeaurora.org, Banajit Goswami , "open list:GPIO SUBSYSTEM" 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, Oct 30, 2019 at 4:55 AM Srinivas Kandagatla wrote: > > > > On 29/10/2019 20:47, Rob Herring wrote: > > On Mon, Oct 28, 2019 at 7:45 AM Srinivas Kandagatla > > wrote: > >> > >> > >> > >> On 28/10/2019 12:40, Srinivas Kandagatla wrote: > >>> Its Phandle. > >>> > >>> something like this is okay? > >>> > >>> slim-ifc-dev: > >>> $ref: '/schemas/types.yaml#/definitions/phandle-array' > >> > >> Sorry this should not be an array, so something like this: > >> > >> slim-ifc-dev: > >> description: SLIMBus Interface device phandle > > > > You're just spelling out the abbreviated name. I can do that much. > > What is 'SLIMBus Interface device'? > > Each SLIMBus Component contains one Interface Device. Which is > responsible for Monitoring and reporting the status of component, Data > line to Data pin connection setup for SLIMBus streaming. Interface > device is enumerated just like any other slim device. So a standard set of registers every slimbus device has? In hindsight, I would have made reg have 2 entries with both addresses. I guess that ship has sailed. It seems strange you would need both "devices" described as separate nodes in DT. > > We already have exactly same bindings for WCD9335 in upstream at: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/sound/qcom,wcd9335.txt?h=v5.4-rc5#n42 > > > > > Is it a standard SLIMBus property? If so, document it in the right > > place. If not, then needs a vendor prefix. > > "SLIMBus Interface Device" itself is documented in SLIMBus Specification. > > If I remember it correctly You suggested me to move to "slim-ifc-dev" > as this is part of SLIMBus Specification. Probably so. If it is common, then document it in bindings/slimbus/bus.txt. Then here, 'slim-ifc-dev: true' is sufficient. You can just assume we convert bus.txt to schema (or feel free to do that :) ). Rob