linux-kernel - RE: [PATCH v4 2/9] dt-bindings: media: nxp: Add Wave6 video codec device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID:
 <PU4P216MB12399BBA5513DAE7D1D60BA0FBF0A@PU4P216MB1239.KORP216.PROD.OUTLOOK.COM>
Date: Thu, 23 Oct 2025 05:13:40 +0000
From: Nas Chung <nas.chung@...psnmedia.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, "mchehab@...nel.org"
	<mchehab@...nel.org>, "hverkuil@...all.nl" <hverkuil@...all.nl>,
	"robh@...nel.org" <robh@...nel.org>, "krzk+dt@...nel.org"
	<krzk+dt@...nel.org>, "conor+dt@...nel.org" <conor+dt@...nel.org>,
	"shawnguo@...nel.org" <shawnguo@...nel.org>, "s.hauer@...gutronix.de"
	<s.hauer@...gutronix.de>
CC: "linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-imx@....com" <linux-imx@....com>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, jackson.lee
	<jackson.lee@...psnmedia.com>, lafley.kim <lafley.kim@...psnmedia.com>,
	"marek.vasut@...lbox.org" <marek.vasut@...lbox.org>
Subject: RE: [PATCH v4 2/9] dt-bindings: media: nxp: Add Wave6 video codec
 device

Hi, Krzysztof.

>-----Original Message-----
>From: Krzysztof Kozlowski <krzk@...nel.org>
>Sent: Wednesday, October 22, 2025 5:31 PM
>To: Nas Chung <nas.chung@...psnmedia.com>; mchehab@...nel.org;
>hverkuil@...all.nl; robh@...nel.org; krzk+dt@...nel.org;
>conor+dt@...nel.org; shawnguo@...nel.org; s.hauer@...gutronix.de
>Cc: linux-media@...r.kernel.org; devicetree@...r.kernel.org; linux-
>kernel@...r.kernel.org; linux-imx@....com; linux-arm-
>kernel@...ts.infradead.org; jackson.lee <jackson.lee@...psnmedia.com>;
>lafley.kim <lafley.kim@...psnmedia.com>; marek.vasut@...lbox.org
>Subject: Re: [PATCH v4 2/9] dt-bindings: media: nxp: Add Wave6 video codec
>device
>
>On 22/10/2025 09:47, Nas Chung wrote:
>> Add documentation for the Chips&Media Wave6 video codec on
>> NXP i.MX SoCs.
>>
>> The Wave6 video codec functionality is split between a VPU
>> control region and VPU core regions.
>> The VPU control region is represented as the parent node and
>> manages shared resources such as firmware memory. Each VPU
>> core region is represented as a child node and provides the
>> actual encoding and decoding capabilities.
>>
>> Both the control and core regions may be assigned IOMMU
>> stream IDs for DMA isolation.
>
>
>Please wrap commit message according to Linux coding style / submission
>process (neither too early nor over the limit):
>https://elixir.bootlin.com/linux/v6.4-
>rc1/source/Documentation/process/submitting-patches.rst#L597

Thanks, I will address this in v5.

>
>>
>
>
>> +
>> +  ranges: true
>> +
>> +patternProperties:
>> +  "^video-core@[0-9a-f]+$":
>> +    type: object
>> +    description:
>> +      A VPU core region within the Chips&Media Wave6 codec IP.
>> +      Each core provides encoding and decoding capabilities and operates
>> +      under the control of the VPU control region.
>
>
>You explained more in previous email than in this description. Are these
>independent? Can they be independently used?

No, they must be used together with the control region.
I will clarify this in v5.

>
>But you also said there is one processing engine, so I do not understand
>why these are separate. If you have one engine, there is no such thing
>as separate cores.

Although the Wave6 VPU contains a single processing engine, it exposes up
to four hardware interfaces, each with its own MMIO region, interrupt
line, and IOMMU stream ID. These interfaces allow concurrent submission
of decoding/encoding operations via firmware scheduling, while execution
occurs on the single processing engine.

The control region also has its own MMIO region (global registers) and its
own IOMMU stream ID. Because the control and each interface have distinct
resources and stream IDs, I believe representing all regions as a single node
would be inappropriate.

Thanks.
Nas.

>
>Best regards,
>Krzysztof