From: Rob Herring <robh@kernel.org> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Cc: Mark Brown <broonie@kernel.org>, Linus Walleij <linus.walleij@linaro.org>, Lee Jones <lee.jones@linaro.org>, Vinod Koul <vinod.koul@linaro.org>, Linux-ALSA <alsa-devel@alsa-project.org>, devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, spapothi@codeaurora.org, Banajit Goswami <bgoswami@codeaurora.org>, "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org> Subject: Re: [PATCH v2 01/11] ASoC: dt-bindings: add dt bindings for WCD9340/WCD9341 audio codec Date: Tue, 5 Nov 2019 13:08:40 -0600 [thread overview] Message-ID: <CAL_JsqJNcXe7YSUjHWyFO_czncnR3y7w3NP8ofXfCiXpMrqzRw@mail.gmail.com> (raw) In-Reply-To: <7811be04-dfda-5953-110c-bca685fdcaa4@linaro.org> On Wed, Oct 30, 2019 at 4:55 AM Srinivas Kandagatla <srinivas.kandagatla@linaro.org> wrote: > > > > On 29/10/2019 20:47, Rob Herring wrote: > > On Mon, Oct 28, 2019 at 7:45 AM Srinivas Kandagatla > > <srinivas.kandagatla@linaro.org> 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
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Cc: devicetree@vger.kernel.org, Linux-ALSA <alsa-devel@alsa-project.org>, Banajit Goswami <bgoswami@codeaurora.org>, Vinod Koul <vinod.koul@linaro.org>, Linus Walleij <linus.walleij@linaro.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>, Mark Brown <broonie@kernel.org>, Lee Jones <lee.jones@linaro.org>, spapothi@codeaurora.org Subject: Re: [alsa-devel] [PATCH v2 01/11] ASoC: dt-bindings: add dt bindings for WCD9340/WCD9341 audio codec Date: Tue, 5 Nov 2019 13:08:40 -0600 [thread overview] Message-ID: <CAL_JsqJNcXe7YSUjHWyFO_czncnR3y7w3NP8ofXfCiXpMrqzRw@mail.gmail.com> (raw) In-Reply-To: <7811be04-dfda-5953-110c-bca685fdcaa4@linaro.org> On Wed, Oct 30, 2019 at 4:55 AM Srinivas Kandagatla <srinivas.kandagatla@linaro.org> wrote: > > > > On 29/10/2019 20:47, Rob Herring wrote: > > On Mon, Oct 28, 2019 at 7:45 AM Srinivas Kandagatla > > <srinivas.kandagatla@linaro.org> 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 _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-05 19:08 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-18 0:18 [PATCH v2 00/11] ASoC: Add support to WCD9340/WCD9341 codec Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-18 0:18 ` [PATCH v2 01/11] ASoC: dt-bindings: add dt bindings for WCD9340/WCD9341 audio codec Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-25 20:43 ` Rob Herring 2019-10-25 20:43 ` [alsa-devel] " Rob Herring 2019-10-28 12:40 ` Srinivas Kandagatla 2019-10-28 12:40 ` [alsa-devel] " Srinivas Kandagatla 2019-10-28 12:45 ` Srinivas Kandagatla 2019-10-28 12:45 ` [alsa-devel] " Srinivas Kandagatla 2019-10-29 20:47 ` Rob Herring 2019-10-29 20:47 ` [alsa-devel] " Rob Herring 2019-10-30 9:55 ` Srinivas Kandagatla 2019-10-30 9:55 ` [alsa-devel] " Srinivas Kandagatla 2019-11-05 19:08 ` Rob Herring [this message] 2019-11-05 19:08 ` Rob Herring 2019-11-06 18:09 ` Srinivas Kandagatla 2019-11-06 18:09 ` [alsa-devel] " Srinivas Kandagatla 2019-11-06 19:20 ` Rob Herring 2019-11-06 19:20 ` [alsa-devel] " Rob Herring 2019-10-18 0:18 ` [PATCH v2 02/11] mfd: wcd934x: add support to wcd9340/wcd9341 codec Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-21 10:46 ` Lee Jones 2019-10-21 10:46 ` [alsa-devel] " Lee Jones 2019-10-21 11:25 ` Srinivas Kandagatla 2019-10-21 11:25 ` [alsa-devel] " Srinivas Kandagatla 2019-10-21 11:45 ` Lee Jones 2019-10-21 11:45 ` [alsa-devel] " Lee Jones 2019-10-21 12:14 ` Srinivas Kandagatla 2019-10-21 12:14 ` [alsa-devel] " Srinivas Kandagatla 2019-10-21 13:19 ` Lee Jones 2019-10-21 13:19 ` [alsa-devel] " Lee Jones 2019-10-18 0:18 ` [PATCH v2 03/11] ASoC: " Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-18 0:18 ` [PATCH v2 04/11] ASoC: wcd934x: add basic controls Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-18 0:18 ` [PATCH v2 05/11] ASoC: wcd934x: add playback dapm widgets Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-20 20:05 ` Cezary Rojewski 2019-10-20 20:05 ` [alsa-devel] " Cezary Rojewski 2019-10-21 9:46 ` Srinivas Kandagatla 2019-10-21 9:46 ` [alsa-devel] " Srinivas Kandagatla 2019-10-18 0:18 ` [PATCH v2 06/11] ASoC: wcd934x: add capture " Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-18 0:18 ` [PATCH v2 07/11] ASoC: wcd934x: add audio routings Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-18 0:18 ` [PATCH v2 08/11] dt-bindings: pinctrl: qcom-wcd934x: Add bindings for gpio Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-25 21:00 ` Rob Herring 2019-10-25 21:00 ` [alsa-devel] " Rob Herring 2019-10-28 12:41 ` Srinivas Kandagatla 2019-10-28 12:41 ` [alsa-devel] " Srinivas Kandagatla 2019-10-18 0:18 ` [PATCH v2 09/11] pinctrl: qcom-wcd934x: Add support to wcd934x pinctrl driver Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-18 0:18 ` [PATCH v2 10/11] ASoC: dt-bindings: Add compatible for DB845c and Lenovo Yoga Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla 2019-10-25 21:01 ` Rob Herring 2019-10-25 21:01 ` [alsa-devel] " Rob Herring 2019-10-18 0:18 ` [PATCH v2 11/11] ASoC: qcom: sdm845: add support to " Srinivas Kandagatla 2019-10-18 0:18 ` [alsa-devel] " Srinivas Kandagatla
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAL_JsqJNcXe7YSUjHWyFO_czncnR3y7w3NP8ofXfCiXpMrqzRw@mail.gmail.com \ --to=robh@kernel.org \ --cc=alsa-devel@alsa-project.org \ --cc=bgoswami@codeaurora.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=lee.jones@linaro.org \ --cc=linus.walleij@linaro.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=spapothi@codeaurora.org \ --cc=srinivas.kandagatla@linaro.org \ --cc=vinod.koul@linaro.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.