[PATCH 3/8] dt-bindings: media: nxp: Add Wave6 video codec device
Nas Chung
nas.chung at chipsnmedia.com
Wed Feb 19 23:35:58 PST 2025
Hi, Krzysztof.
>-----Original Message-----
>From: Krzysztof Kozlowski <krzk at kernel.org>
>Sent: Wednesday, February 19, 2025 9:32 PM
>To: Nas Chung <nas.chung at chipsnmedia.com>
>Cc: mchehab at kernel.org; hverkuil at xs4all.nl; sebastian.fricke at collabora.com;
>robh at kernel.org; krzk+dt at kernel.org; conor+dt at kernel.org; linux-
>media at vger.kernel.org; devicetree at vger.kernel.org; linux-
>kernel at vger.kernel.org; linux-imx at nxp.com; linux-arm-
>kernel at lists.infradead.org; jackson.lee <jackson.lee at chipsnmedia.com>;
>lafley.kim <lafley.kim at 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 at 4c480000 {
>> compatible = "nxp,imx95-vpu";
>> reg = <0x0 0x4c480000 0x0 0x50000>;
>> ranges = <0x0 0x0 0x4c480000 0x50000>;
>>
>> vpuctrl: vpu-ctrl at 40000 {
>> compatible = "nxp,imx95-vpu-ctrl";
>> reg = <0x40000 0x10000>;
>> };
>>
>> vpucore0: vpu-core at 00000 {
>> compatible = "nxp,imx95-vpu-core";
>> reg = <0x00000 0x10000>;
>> };
>>
>> vpucore1: vpu-core at 10000 {
>> compatible = "nxp,imx95-vpu-core";
>> reg = <0x10000 0x10000>;
>> };
>>
>> vpucore2: vpu-core at 20000 {
>> compatible = "nxp,imx95-vpu-core";
>> reg = <0x20000 0x10000>;
>> };
>>
>> vpucore3: vpu-core at 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 at 4c480000 {
compatible = "nxp,imx95-vpu";
reg = <0x0 0x4c480000 0x0 0x50000>;
ranges = <0x0 0x0 0x4c480000 0x50000>;
vpuctrl: vpu-ctrl at 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 at 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>;
clock-names = "vpu", "vpublk_wave";
power-domains = <&scmi_devpd 21>;
};
vpucore1: vpu-core at 10000 {
compatible = "nxp,imx95-vpu-core";
reg = <0x10000 0x10000>;
interrupts = <GIC_SPI 299 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&scmi_clk 115>,
<&vpu_blk_ctrl IMX95_CLK_VPUBLK_WAVE>;
clock-names = "vpu", "vpublk_wave";
power-domains = <&scmi_devpd 21>;
};
vpucore2: vpu-core at 20000 {
compatible = "nxp,imx95-vpu-core";
reg = <0x20000 0x10000>;
interrupts = <GIC_SPI 299 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&scmi_clk 115>,
<&vpu_blk_ctrl IMX95_CLK_VPUBLK_WAVE>;
clock-names = "vpu", "vpublk_wave";
power-domains = <&scmi_devpd 21>;
};
vpucore3: vpu-core at 30000 {
compatible = "nxp,imx95-vpu-core";
reg = <0x30000 0x10000>;
interrupts = <GIC_SPI 299 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&scmi_clk 115>,
<&vpu_blk_ctrl IMX95_CLK_VPUBLK_WAVE>;
clock-names = "vpu", "vpublk_wave";
power-domains = <&scmi_devpd 21>;
};
};
Thanks.
Nas.
>
>Best regards,
>Krzysztof
More information about the linux-arm-kernel
mailing list