All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nas Chung <nas.chung@chipsnmedia.com>
Cc: "mchehab@kernel.org" <mchehab@kernel.org>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-imx@nxp.com" <linux-imx@nxp.com>,
	"marex@denx.de" <marex@denx.de>,
	"jackson.lee" <jackson.lee@chipsnmedia.com>,
	"lafley.kim" <lafley.kim@chipsnmedia.com>
Subject: Re: [PATCH v2 2/8] dt-bindings: media: nxp: Add Wave6 video codec device
Date: Tue, 20 May 2025 08:27:09 +0200	[thread overview]
Message-ID: <f9eb4322-cf6f-445d-8ba8-39182325ca4e@kernel.org> (raw)
In-Reply-To: <SL2P216MB1246B1DA93D85C1536476D74FB9CA@SL2P216MB1246.KORP216.PROD.OUTLOOK.COM>

On 19/05/2025 07:08, Nas Chung wrote:
> Hi, Krzysztof.
> 
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Sent: Friday, May 16, 2025 9:56 PM
>> To: Nas Chung <nas.chung@chipsnmedia.com>
>> Cc: mchehab@kernel.org; hverkuil@xs4all.nl; sebastian.fricke@collabora.com;
>> robh@kernel.org; krzk+dt@kernel.org; conor+dt@kernel.org; linux-
>> media@vger.kernel.org; devicetree@vger.kernel.org; linux-
>> kernel@vger.kernel.org; linux-imx@nxp.com; marex@denx.de; jackson.lee
>> <jackson.lee@chipsnmedia.com>; lafley.kim <lafley.kim@chipsnmedia.com>
>> Subject: Re: [PATCH v2 2/8] dt-bindings: media: nxp: Add Wave6 video codec
>> device
>>
>> On 13/05/2025 09:39, Nas Chung wrote:
>>>>
>>>> All of above are wrong for the SoC...
>>>>
>>>>>
>>>>>         #include <dt-bindings/interrupt-controller/arm-gic.h>
>>>>>         #include <dt-bindings/clock/nxp,imx95-clock.h>
>>>>>
>>>>>         soc {
>>>>>           #address-cells = <2>;
>>>>>           #size-cells = <2>;
>>>>>
>>>>>           vpu: video-codec {
>>>>>             compatible = "nxp,imx95-vpu", "cnm,wave633c";
>>>>
>>>> What does this device represent? It is not "ctrl", because you made ctrl
>>>> separate device node. Your binding description suggests that is the VPU
>>>> control region.
>>>
>>> My intention was to represent the MMIO VPU device, which includes
>>> both the core and control nodes.
>>
>> Then what is the VPU device if not CTRL? What is the CTRL device?
> 
> The VPU device represents the entire VPU hardware block,
> which includes 1 CTRL component(node) and 4 CORE components(nodes).

What is entire VPU hardware block?

> 
> The CTRL device represents the VCPU, a 32-bit processor embedded within the
> VPU hardware block. This VCPU is responsible for executing the VPU firmware.
> The CTRL device is in charge of tasks such as firmware booting, power management
> (sleep and wakeup command), and managing memory regions that are exclusively
> accessed by the firmware.

This sounds like CTRL is responsible for entire VPU block. What are the
tasks of VPU block then? What are its registers? What is that device
exactly doing?

You keep repeating the same, so my initial idea - CTRL is not a separate
block - still stands. Can you have more CTRL blocks than one?

Best regards,
Krzysztof

  reply	other threads:[~2025-05-20  6:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  9:31 [PATCH v2 0/8] Add support for Wave6 video codec driver Nas Chung
2025-04-22  9:31 ` [PATCH v2 1/8] media: v4l2-common: Add YUV24 format info Nas Chung
2025-04-24 15:43   ` Nicolas Dufresne
2025-04-22  9:31 ` [PATCH v2 2/8] dt-bindings: media: nxp: Add Wave6 video codec device Nas Chung
2025-04-25 10:34   ` Krzysztof Kozlowski
2025-05-09  9:59     ` Nas Chung
2025-05-09 10:11       ` Krzysztof Kozlowski
2025-05-13  7:39         ` Nas Chung
2025-05-16 12:55           ` Krzysztof Kozlowski
2025-05-19  5:08             ` Nas Chung
2025-05-20  6:27               ` Krzysztof Kozlowski [this message]
2025-05-20  8:31                 ` Nas Chung
2025-04-22  9:31 ` [PATCH v2 3/8] media: chips-media: wave6: Add Wave6 driver Nas Chung
2025-04-24 17:36   ` Nicolas Dufresne
2025-05-14  8:09     ` Nas Chung
2025-04-22  9:31 ` [PATCH v2 4/8] media: chips-media: wave6: Add Wave6 control driver Nas Chung
2025-04-29 20:47   ` Nicolas Dufresne
2025-05-14 10:15     ` Nas Chung
2025-04-22  9:31 ` [PATCH v2 5/8] media: chips-media: wave6: Add Wave6 VPU interface Nas Chung
2025-05-01 17:42   ` Nicolas Dufresne
2025-05-16  8:08     ` Nas Chung
2025-04-22  9:31 ` [PATCH v2 6/8] media: chips-media: wave6: Improve debugging capabilities Nas Chung
2025-04-22  9:31 ` [PATCH v2 7/8] media: chips-media: wave6: Add v4l2 m2m driver support Nas Chung
2025-04-22  9:31 ` [PATCH v2 8/8] media: chips-media: wave6: Add Wave6 core driver Nas Chung
2025-09-03 21:47 ` [PATCH v2 0/8] Add support for Wave6 video codec driver Marek Vasut
2025-09-04 13:25   ` Nicolas Dufresne
2025-09-04 15:32     ` Marek Vasut
2025-09-04 15:54       ` Nicolas Dufresne
2025-09-05  1:22         ` [EXT] " Ming Qian
2025-10-11 10:56           ` Marek Vasut
2025-10-15  5:11             ` Nas Chung
2025-10-15 10:24               ` Marek Vasut
2025-10-16  4:01                 ` Nas Chung
2025-10-16 10:01                   ` Marek Vasut
2025-09-06 21:32         ` Marek Vasut

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=f9eb4322-cf6f-445d-8ba8-39182325ca4e@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jackson.lee@chipsnmedia.com \
    --cc=krzk+dt@kernel.org \
    --cc=lafley.kim@chipsnmedia.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.com \
    --cc=robh@kernel.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: link
Be 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.