devicetree.vger.kernel.org archive mirror
 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>,
	"sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>,
	"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>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"jackson.lee" <jackson.lee@chipsnmedia.com>,
	"lafley.kim" <lafley.kim@chipsnmedia.com>
Subject: Re: [PATCH 3/8] dt-bindings: media: nxp: Add Wave6 video codec device
Date: Thu, 20 Feb 2025 09:32:05 +0100	[thread overview]
Message-ID: <e3403885-ca21-4e67-b117-f40a7a65418b@kernel.org> (raw)
In-Reply-To: <SL2P216MB1246F270DDE8CC8E21EA1DDCFBC42@SL2P216MB1246.KORP216.PROD.OUTLOOK.COM>

On 20/02/2025 08:35, Nas Chung wrote:
> Hi, Krzysztof.
> 
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Sent: Wednesday, February 19, 2025 9:32 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; linux-arm-
>> kernel@lists.infradead.org; jackson.lee <jackson.lee@chipsnmedia.com>;
>> lafley.kim <lafley.kim@chipsnmedia.com>
>> Subject: Re: [PATCH 3/8] dt-bindings: media: nxp: Add Wave6 video codec
>> device
>>
>> On 18/02/2025 10:21, Nas Chung wrote:
>>> For example:
>>> vpu: video-codec@4c480000 {
>>>         compatible = "nxp,imx95-vpu";
>>>         reg = <0x0 0x4c480000 0x0 0x50000>;
>>> 	ranges = <0x0 0x0 0x4c480000 0x50000>;
>>>
>>>         vpuctrl: vpu-ctrl@40000 {
>>>           compatible = "nxp,imx95-vpu-ctrl";
>>> 	  reg = <0x40000 0x10000>;
>>>         };
>>>
>>>         vpucore0: vpu-core@00000 {
>>>           compatible = "nxp,imx95-vpu-core";
>>>           reg = <0x00000 0x10000>;
>>>         };
>>>
>>>         vpucore1: vpu-core@10000 {
>>>           compatible = "nxp,imx95-vpu-core";
>>>           reg = <0x10000 0x10000>;
>>>         };
>>>
>>>         vpucore2: vpu-core@20000 {
>>>           compatible = "nxp,imx95-vpu-core";
>>>           reg = <0x20000 0x10000>;
>>>         };
>>>
>>>         vpucore3: vpu-core@30000 {
>>>           compatible = "nxp,imx95-vpu-core";
>>
>> Why do you need compatible here? Could it be anything else?
> 
> I will update the driver based on the final DT.
> 
>>
>>>           reg = <0x30000 0x10000>;
>>
>> Where is the rest of resources? You created children only for one
>> resource - address space?
> 
> Sorry for the confusion.
> I believe the final example looks like the one below.
> 
> vpu: video-codec@4c480000 {
>         compatible = "nxp,imx95-vpu";
>         reg = <0x0 0x4c480000 0x0 0x50000>;
>         ranges = <0x0 0x0 0x4c480000 0x50000>;
> 
>         vpuctrl: vpu-ctrl@40000 {
>           compatible = "nxp,imx95-vpu-ctrl";
>           reg = <0x40000 0x10000>;
>           clocks = <&scmi_clk 115>,
>                   <&vpu_blk_ctrl IMX95_CLK_VPUBLK_WAVE>;
>           clock-names = "vpu", "vpublk_wave";
>           power-domains = <&scmi_devpd 21>, <&scmi_perf 10>;
>           power-domain-names = "vpumix", "vpuperf";
>           memory-region = <&vpu_boot>;
>           #cooling-cells = <2>;
>           sram = <&sram1>;
>         };
> 
>         vpucore0: vpu-core@00000 {
>           compatible = "nxp,imx95-vpu-core";
>           reg = <0x00000 0x10000>;
>           interrupts = <GIC_SPI 299 IRQ_TYPE_LEVEL_HIGH>;
>           clocks = <&scmi_clk 115>,
>                   <&vpu_blk_ctrl IMX95_CLK_VPUBLK_WAVE>;


These are the same resources for every block so for entire device. Why
they are no in top level node?

>           clock-names = "vpu", "vpublk_wave";
>           power-domains = <&scmi_devpd 21>;

Same here

Everything else also looks duplicated... All my previous comments - from
first email - stand. Don't design DT to match your Linu driver structure.

Best regards,
Krzysztof

  reply	other threads:[~2025-02-20  8:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10  9:07 [PATCH 0/8] Add support for Wave6 video codec driver Nas Chung
2025-02-10  9:07 ` [PATCH 1/8] media: platform: chips-media: wave5: Rename Kconfig parameter Nas Chung
2025-02-10 17:24   ` Krzysztof Kozlowski
2025-02-11  4:23     ` Nas Chung
2025-02-10  9:07 ` [PATCH 2/8] media: v4l2-common: Add YUV24 format info Nas Chung
2025-02-10 14:00   ` Sebastian Fricke
2025-02-11  1:58     ` Nas Chung
2025-02-10  9:07 ` [PATCH 3/8] dt-bindings: media: nxp: Add Wave6 video codec device Nas Chung
2025-02-10 17:30   ` Krzysztof Kozlowski
2025-02-13  7:50     ` Nas Chung
2025-02-13  8:49       ` Krzysztof Kozlowski
2025-02-18  9:21         ` Nas Chung
2025-02-19 12:31           ` Krzysztof Kozlowski
2025-02-20  7:35             ` Nas Chung
2025-02-20  8:32               ` Krzysztof Kozlowski [this message]
2025-02-21  8:29                 ` Nas Chung
2025-02-10  9:07 ` [PATCH 4/8] media: chips-media: wave6: Add Wave6 codec driver Nas Chung
2025-02-10 17:40   ` Krzysztof Kozlowski
2025-02-11  8:28     ` Nas Chung
2025-02-10  9:07 ` [PATCH 5/8] media: chips-media: wave6: Add v4l2 m2m driver Nas Chung
2025-02-17 18:33   ` Nicolas Dufresne
2025-02-19  4:36     ` Nas Chung
2025-02-10  9:07 ` [PATCH 6/8] media: chips-media: wave6: Add Wave6 vpu interface Nas Chung
2025-02-28  8:33   ` [EXT] " Ming Qian
2025-02-10  9:07 ` [PATCH 7/8] media: chips-media: wave6: Add Wave6 control driver Nas Chung
2025-02-10 17:37   ` Krzysztof Kozlowski
2025-02-11  8:55     ` Nas Chung
2025-02-11 20:25   ` kernel test robot
2025-02-12  1:31   ` kernel test robot
2025-02-10  9:07 ` [PATCH 8/8] media: chips-media: wave6: Improve debugging capabilities Nas Chung
2025-02-11 16:43   ` kernel test robot
2025-02-10 13:05 ` [PATCH 0/8] Add support for Wave6 video codec driver Sebastian Fricke
2025-02-11  4:47   ` Nas Chung
2025-02-11  6:07 ` [EXT] " Ming Qian

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=e3403885-ca21-4e67-b117-f40a7a65418b@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-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=robh@kernel.org \
    --cc=sebastian.fricke@collabora.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).