From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> To: Sebastian Fricke <sebastian.fricke@collabora.com>, Rob Herring <robh@kernel.org> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, NXP Linux Team <linux-imx@nxp.com>, Conor Dooley <conor+dt@kernel.org>, Mauro Carvalho Chehab <mchehab@kernel.org>, Jackson Lee <jackson.lee@chipsnmedia.com>, Hans Verkuil <hverkuil@xs4all.nl>, Sascha Hauer <s.hauer@pengutronix.de>, Pengutronix Kernel Team <kernel@pengutronix.de>, Shawn Guo <shawnguo@kernel.org>, Philipp Zabel <p.zabel@pengutronix.de>, Nas Chung <nas.chung@chipsnmedia.com>, Fabio Estevam <festevam@gmail.com>, linux-media@vger.kernel.org, Tomasz Figa <tfiga@chromium.org>, linux-kernel@vger.kernel.org, Nicolas Dufresne <nicolas.dufresne@collabora.com>, kernel@collabora.com, Robert Beckett <bob.beckett@collabora.com>, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Darren Etheridge <detheridge@ti.com> Subject: Re: [PATCH v13 6/8] media: dt-bindings: wave5: add Chips&Media 521c codec IP support Date: Sun, 22 Oct 2023 18:01:31 +0200 [thread overview] Message-ID: <3d465d3c-386d-467b-87e9-806962464ac5@linaro.org> (raw) In-Reply-To: <20231021120526.eqe3esyxyi5b3e5d@basti-XPS-13-9310> On 21/10/2023 14:05, Sebastian Fricke wrote: > Hey Rob and Krzysztof, > > On 16.10.2023 08:47, Rob Herring wrote: >> On Thu, Oct 12, 2023 at 03:24:12PM +0200, Krzysztof Kozlowski wrote: >>> On 12/10/2023 13:01, Sebastian Fricke wrote: >>>> From: Robert Beckett <bob.beckett@collabora.com> >>>> >>>> Add bindings for the chips&media wave5 codec driver >>>> >>>> Signed-off-by: Robert Beckett <bob.beckett@collabora.com> >>>> Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com> >>>> Signed-off-by: Sebastian Fricke <sebastian.fricke@collabora.com> >>>> --- >>>> .../devicetree/bindings/media/cnm,wave5.yaml | 60 ++++++++++++++++++++++ >>>> 1 file changed, 60 insertions(+) >>>> >>>> diff --git a/Documentation/devicetree/bindings/media/cnm,wave5.yaml b/Documentation/devicetree/bindings/media/cnm,wave5.yaml >>>> new file mode 100644 >>>> index 000000000000..b31d34aec05b >>>> --- /dev/null >>>> +++ b/Documentation/devicetree/bindings/media/cnm,wave5.yaml >>>> @@ -0,0 +1,60 @@ >>>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) >>>> +%YAML 1.2 >>>> +--- >>>> +$id: http://devicetree.org/schemas/media/cnm,wave5.yaml# >>> >>> Filename matching compatible, so: cnm,cm521c-vpu.yaml > > With which compatible should the filename match? (see below) > And just to be sure, this means that I rename the file to: > `.../devicetree/bindings/media/cnm,wave521c.yaml` With the fallback compatible. > >>> >>>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>>> + >>>> +title: Chips&Media Wave 5 Series multi-standard codec IP >>>> + >>>> +maintainers: >>>> + - Nas Chung <nas.chung@chipsnmedia.com> >>>> + - Jackson Lee <jackson.lee@chipsnmedia.com> >>>> + >>>> +description: >>>> + The Chips&Media WAVE codec IP is a multi format video encoder/decoder >>>> + >>>> +properties: >>>> + compatible: >>>> + enum: >>>> + - cnm,cm521c-vpu >>> >>> Can this device be anything else? Why VPU suffix? >> >> It needs an SoC specific compatible (TI something...) as well (or >> instead). Unless there's a public spec with details on how many >> clocks, resets, interrupts, etc. there are. > > Okay so how about this, a bit similar to the Coda driver supplying both > a general option and a SoC specific version: Can generic compatible be used alone in board designs? If it is licensed block, then most likely you want a fallback. > > properties: > compatible: > enum: > - ti,k3-j721sX-wave521c > - cnm,wave521c > > (ti,k3-j721sX-wave521c = manufacturer,SoC-codec) > (tested on j721s2 but should work on other variations as well) > > Another alternative could be: ti,k3-wave521c (less specific on a single > SoC series but connected to a bigger range of devices) Best regards, Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> To: Sebastian Fricke <sebastian.fricke@collabora.com>, Rob Herring <robh@kernel.org> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, NXP Linux Team <linux-imx@nxp.com>, Conor Dooley <conor+dt@kernel.org>, Mauro Carvalho Chehab <mchehab@kernel.org>, Jackson Lee <jackson.lee@chipsnmedia.com>, Hans Verkuil <hverkuil@xs4all.nl>, Sascha Hauer <s.hauer@pengutronix.de>, Pengutronix Kernel Team <kernel@pengutronix.de>, Shawn Guo <shawnguo@kernel.org>, Philipp Zabel <p.zabel@pengutronix.de>, Nas Chung <nas.chung@chipsnmedia.com>, Fabio Estevam <festevam@gmail.com>, linux-media@vger.kernel.org, Tomasz Figa <tfiga@chromium.org>, linux-kernel@vger.kernel.org, Nicolas Dufresne <nicolas.dufresne@collabora.com>, kernel@collabora.com, Robert Beckett <bob.beckett@collabora.com>, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Darren Etheridge <detheridge@ti.com> Subject: Re: [PATCH v13 6/8] media: dt-bindings: wave5: add Chips&Media 521c codec IP support Date: Sun, 22 Oct 2023 18:01:31 +0200 [thread overview] Message-ID: <3d465d3c-386d-467b-87e9-806962464ac5@linaro.org> (raw) In-Reply-To: <20231021120526.eqe3esyxyi5b3e5d@basti-XPS-13-9310> On 21/10/2023 14:05, Sebastian Fricke wrote: > Hey Rob and Krzysztof, > > On 16.10.2023 08:47, Rob Herring wrote: >> On Thu, Oct 12, 2023 at 03:24:12PM +0200, Krzysztof Kozlowski wrote: >>> On 12/10/2023 13:01, Sebastian Fricke wrote: >>>> From: Robert Beckett <bob.beckett@collabora.com> >>>> >>>> Add bindings for the chips&media wave5 codec driver >>>> >>>> Signed-off-by: Robert Beckett <bob.beckett@collabora.com> >>>> Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com> >>>> Signed-off-by: Sebastian Fricke <sebastian.fricke@collabora.com> >>>> --- >>>> .../devicetree/bindings/media/cnm,wave5.yaml | 60 ++++++++++++++++++++++ >>>> 1 file changed, 60 insertions(+) >>>> >>>> diff --git a/Documentation/devicetree/bindings/media/cnm,wave5.yaml b/Documentation/devicetree/bindings/media/cnm,wave5.yaml >>>> new file mode 100644 >>>> index 000000000000..b31d34aec05b >>>> --- /dev/null >>>> +++ b/Documentation/devicetree/bindings/media/cnm,wave5.yaml >>>> @@ -0,0 +1,60 @@ >>>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) >>>> +%YAML 1.2 >>>> +--- >>>> +$id: http://devicetree.org/schemas/media/cnm,wave5.yaml# >>> >>> Filename matching compatible, so: cnm,cm521c-vpu.yaml > > With which compatible should the filename match? (see below) > And just to be sure, this means that I rename the file to: > `.../devicetree/bindings/media/cnm,wave521c.yaml` With the fallback compatible. > >>> >>>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>>> + >>>> +title: Chips&Media Wave 5 Series multi-standard codec IP >>>> + >>>> +maintainers: >>>> + - Nas Chung <nas.chung@chipsnmedia.com> >>>> + - Jackson Lee <jackson.lee@chipsnmedia.com> >>>> + >>>> +description: >>>> + The Chips&Media WAVE codec IP is a multi format video encoder/decoder >>>> + >>>> +properties: >>>> + compatible: >>>> + enum: >>>> + - cnm,cm521c-vpu >>> >>> Can this device be anything else? Why VPU suffix? >> >> It needs an SoC specific compatible (TI something...) as well (or >> instead). Unless there's a public spec with details on how many >> clocks, resets, interrupts, etc. there are. > > Okay so how about this, a bit similar to the Coda driver supplying both > a general option and a SoC specific version: Can generic compatible be used alone in board designs? If it is licensed block, then most likely you want a fallback. > > properties: > compatible: > enum: > - ti,k3-j721sX-wave521c > - cnm,wave521c > > (ti,k3-j721sX-wave521c = manufacturer,SoC-codec) > (tested on j721s2 but should work on other variations as well) > > Another alternative could be: ti,k3-wave521c (less specific on a single > SoC series but connected to a bigger range of devices) Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-22 16:01 UTC|newest] Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-12 11:00 [PATCH v13 0/8] Wave5 codec driver Sebastian Fricke 2023-10-12 11:00 ` Sebastian Fricke 2023-10-12 11:00 ` [PATCH v13 1/8] media: v4l2: Add ignore_cap_streaming flag Sebastian Fricke 2023-10-12 11:00 ` Sebastian Fricke 2023-10-12 11:01 ` [PATCH v13 2/8] media: v4l2: Allow M2M job queuing w/o streaming CAP queue Sebastian Fricke 2023-10-12 11:01 ` Sebastian Fricke 2023-10-12 11:01 ` [PATCH v13 3/8] media: platform: chips-media: Move Coda to separate folder Sebastian Fricke 2023-10-12 11:01 ` Sebastian Fricke 2023-10-12 11:01 ` [PATCH v13 4/8] media: chips-media: wave5: Add vpuapi layer Sebastian Fricke 2023-10-22 16:27 ` Christophe JAILLET 2023-10-22 16:27 ` Christophe JAILLET 2023-10-12 11:01 ` [PATCH v13 5/8] media: chips-media: wave5: Add the v4l2 layer Sebastian Fricke 2023-10-16 11:57 ` Hans Verkuil 2023-10-16 11:57 ` Hans Verkuil 2023-10-16 13:35 ` Sebastian Fricke 2023-10-16 13:35 ` Sebastian Fricke 2023-10-16 13:39 ` Hans Verkuil 2023-10-16 13:39 ` Hans Verkuil 2023-10-17 22:13 ` Ivan Bornyakov 2023-10-17 22:13 ` Ivan Bornyakov 2023-11-02 17:07 ` Deborah Brouwer 2023-11-02 17:07 ` Deborah Brouwer 2023-11-03 10:42 ` Ivan Bornyakov 2023-11-03 10:42 ` Ivan Bornyakov 2023-10-12 11:01 ` [PATCH v13 6/8] media: dt-bindings: wave5: add Chips&Media 521c codec IP support Sebastian Fricke 2023-10-12 11:01 ` Sebastian Fricke 2023-10-12 13:24 ` Krzysztof Kozlowski 2023-10-12 13:24 ` Krzysztof Kozlowski 2023-10-16 13:47 ` Rob Herring 2023-10-16 13:47 ` Rob Herring 2023-10-21 12:05 ` Sebastian Fricke 2023-10-21 12:05 ` Sebastian Fricke 2023-10-22 16:01 ` Krzysztof Kozlowski [this message] 2023-10-22 16:01 ` Krzysztof Kozlowski 2023-10-24 5:17 ` Sebastian Fricke 2023-10-24 5:17 ` Sebastian Fricke 2023-10-24 7:24 ` Krzysztof Kozlowski 2023-10-24 7:24 ` Krzysztof Kozlowski 2023-10-25 6:17 ` Sebastian Fricke 2023-10-25 6:17 ` Sebastian Fricke 2023-10-25 7:04 ` Krzysztof Kozlowski 2023-10-25 7:04 ` Krzysztof Kozlowski 2023-10-17 13:39 ` Devarsh Thakkar 2023-10-17 13:39 ` Devarsh Thakkar 2023-10-21 11:53 ` Sebastian Fricke 2023-10-21 11:53 ` Sebastian Fricke 2023-10-22 16:12 ` Krzysztof Kozlowski 2023-10-22 16:12 ` Krzysztof Kozlowski 2023-10-26 16:33 ` Sebastian Fricke 2023-10-26 16:33 ` Sebastian Fricke 2023-10-27 7:07 ` Krzysztof Kozlowski 2023-10-27 7:07 ` Krzysztof Kozlowski 2023-10-12 11:01 ` [PATCH v13 7/8] media: chips-media: wave5: Add wave5 driver to maintainers file Sebastian Fricke 2023-10-12 11:01 ` Sebastian Fricke 2023-10-12 11:01 ` [PATCH v13 8/8] arm64: dts: ti: k3-j721s2-main: add wave5 video encoder/decoder node Sebastian Fricke 2023-10-12 11:01 ` Sebastian Fricke
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=3d465d3c-386d-467b-87e9-806962464ac5@linaro.org \ --to=krzysztof.kozlowski@linaro.org \ --cc=bob.beckett@collabora.com \ --cc=conor+dt@kernel.org \ --cc=detheridge@ti.com \ --cc=devicetree@vger.kernel.org \ --cc=festevam@gmail.com \ --cc=hverkuil@xs4all.nl \ --cc=jackson.lee@chipsnmedia.com \ --cc=kernel@collabora.com \ --cc=kernel@pengutronix.de \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=mchehab@kernel.org \ --cc=nas.chung@chipsnmedia.com \ --cc=nicolas.dufresne@collabora.com \ --cc=p.zabel@pengutronix.de \ --cc=robh@kernel.org \ --cc=s.hauer@pengutronix.de \ --cc=sebastian.fricke@collabora.com \ --cc=shawnguo@kernel.org \ --cc=tfiga@chromium.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.