All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dragan Simic <dsimic@manjaro.org>,
	Jonas Karlman <jonas@kwiboo.se>, Coia Prant <coiaprant@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Coia Prant <coiaprant@gmail.com>
Subject: Re: [PATCH] arm64: dts: rockchip: Add devicetree for the X3568 v4
Date: Sat, 25 Oct 2025 23:03:11 +0200	[thread overview]
Message-ID: <2940731.88bMQJbFj6@phil> (raw)
In-Reply-To: <20251025203711.3859240-1-coiaprant@gmail.com>

Hi,

general comments, I haven't disected the devicetrees yet.


Am Samstag, 25. Oktober 2025, 22:37:11 Mitteleuropäische Sommerzeit schrieb Coia Prant:

Please also provide some description what type of board this is,
not just a list of specs

> Specification:
> - SoC: RockChip RK3568 ARM64 (4 cores)
> - eMMC: 16-128 GB
> - RAM: 2-8 GB
> - Power: DC 12V 2A
> - Ethernet: 2x YT8521SC RGMII (10/100/1000 Mbps)
> - Wireless radio: 802.11b/g/n/ac/ax dual-band
> - LED:
>   Power: AlwaysOn
>   User: GPIO
> - Button:
>   VOL+: SARADC/0 <35k µV>
>   VOL-: SARADC/0 <450k µV>
>   Power/Reset: PMIC RK809
> - CAN
>   CAN/1: 4-pin (PH 2.0)
> - PWM
>   PWM/4: Backlight DSI/0 DSI/1
>   PWM/7: IR Receiver [may not install]
> - UART:
>   UART/2: Debug TTL - 1500000 8N1 (1.25mm)
>   UART/3: TTL (PH 2.0)
>   UART/4: TTL (PH 2.0)
>   UART/8: AP6275S Bluetooth
>   UART/9: TTL (PH 2.0)
> - I2C:
>   I2C/0: PMIC RK809
>   I2C/1: Touchscreen DSI/0 DSI/1
>   I2C/4: Camera
>   I2C/5: RTC@51 PCF8563
> - I2S:
>   I2S/0: miniHDMI Sound
>   I2S/1: RK809 Audio Codec
>   I2S/3: AP6275S Bluetooth Sound
> - SDMMC:
>   SDMMC/0: microSD (TF) slot
>   SDMMC/2: AP6275S SDIO WiFi card
> - Camera: 1x CSI
> - Video: miniHDMI / DSI0 (MIPI/LVDS) / DSI1 (MIPI/EDP)
> - Audio: miniHDMI / MIC on-board / Speaker / SPDIF / 3.5mm Headphones / AP6275S Bluetooth
> - USB:
>   USB 2.0 HOST x2
>   USB 2.0 HOST x3 (4-pin)
>   USB 2.0 OTG x1 (shared with USB 3.0 OTG/HOST) [slot may not install]
>   USB 3.0 HOST x1
>   USB 3.0 OTG/HOST x1
> - SATA: 1x SATA 3.0 with Power/4-pin [slot may not install]
> - PCIe: 1x PCIe 3.0 x2 (x4 connecter) [clock/slot may not install]
> 
> Link:
> - https://appletsapi.52solution.com/media/X3568V4%E5%BC%80%E5%8F%91%E6%9D%BF%E7%A1%AC%E4%BB%B6%E6%89%8B%E5%86%8C.pdf
> - https://blog.gov.cooking/archives/research-ninetripod-x3568-v4-and-flash.html

2nd link ends in a 404 error, page not found


> Signed-off-by: Coia Prant <coiaprant@gmail.com>
> Tested-by: Coia Prant <coiaprant@gmail.com>


When you submit a patch, we expect you to have tested it, so tere
is no need to have a separate tested-by line :-) .


> ---
>  arch/arm64/boot/dts/rockchip/Makefile         |  11 +
>  .../rockchip/rk3568-x3568-camera-demo.dtso    |  82 ++
>  .../boot/dts/rockchip/rk3568-x3568-v4.dts     | 884 ++++++++++++++++++
>  .../dts/rockchip/rk3568-x3568-video-demo.dtso | 141 +++

please name your boards including the ninetree name, because x3568 is way
too generic, so
rk3568-ninetree-x3568 .....

Additionally, from that PDF above, it seems this is a system-on-module?
X3568CV2 + baseboard? If so, please split this into a dtsi + dts.
See all the other system-on-modules for reference.

Additionally, you'll need to have a 2nd patch to add the board to
Documentation/devicetree/bindings/arm/rockchip.yaml

And also possily a 3rd patch to add ninetree to
Documentation/devicetree/bindings/vendor-prefixes.yaml


Heiko




WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dragan Simic <dsimic@manjaro.org>,
	Jonas Karlman <jonas@kwiboo.se>, Coia Prant <coiaprant@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Coia Prant <coiaprant@gmail.com>
Subject: Re: [PATCH] arm64: dts: rockchip: Add devicetree for the X3568 v4
Date: Sat, 25 Oct 2025 23:03:11 +0200	[thread overview]
Message-ID: <2940731.88bMQJbFj6@phil> (raw)
In-Reply-To: <20251025203711.3859240-1-coiaprant@gmail.com>

Hi,

general comments, I haven't disected the devicetrees yet.


Am Samstag, 25. Oktober 2025, 22:37:11 Mitteleuropäische Sommerzeit schrieb Coia Prant:

Please also provide some description what type of board this is,
not just a list of specs

> Specification:
> - SoC: RockChip RK3568 ARM64 (4 cores)
> - eMMC: 16-128 GB
> - RAM: 2-8 GB
> - Power: DC 12V 2A
> - Ethernet: 2x YT8521SC RGMII (10/100/1000 Mbps)
> - Wireless radio: 802.11b/g/n/ac/ax dual-band
> - LED:
>   Power: AlwaysOn
>   User: GPIO
> - Button:
>   VOL+: SARADC/0 <35k µV>
>   VOL-: SARADC/0 <450k µV>
>   Power/Reset: PMIC RK809
> - CAN
>   CAN/1: 4-pin (PH 2.0)
> - PWM
>   PWM/4: Backlight DSI/0 DSI/1
>   PWM/7: IR Receiver [may not install]
> - UART:
>   UART/2: Debug TTL - 1500000 8N1 (1.25mm)
>   UART/3: TTL (PH 2.0)
>   UART/4: TTL (PH 2.0)
>   UART/8: AP6275S Bluetooth
>   UART/9: TTL (PH 2.0)
> - I2C:
>   I2C/0: PMIC RK809
>   I2C/1: Touchscreen DSI/0 DSI/1
>   I2C/4: Camera
>   I2C/5: RTC@51 PCF8563
> - I2S:
>   I2S/0: miniHDMI Sound
>   I2S/1: RK809 Audio Codec
>   I2S/3: AP6275S Bluetooth Sound
> - SDMMC:
>   SDMMC/0: microSD (TF) slot
>   SDMMC/2: AP6275S SDIO WiFi card
> - Camera: 1x CSI
> - Video: miniHDMI / DSI0 (MIPI/LVDS) / DSI1 (MIPI/EDP)
> - Audio: miniHDMI / MIC on-board / Speaker / SPDIF / 3.5mm Headphones / AP6275S Bluetooth
> - USB:
>   USB 2.0 HOST x2
>   USB 2.0 HOST x3 (4-pin)
>   USB 2.0 OTG x1 (shared with USB 3.0 OTG/HOST) [slot may not install]
>   USB 3.0 HOST x1
>   USB 3.0 OTG/HOST x1
> - SATA: 1x SATA 3.0 with Power/4-pin [slot may not install]
> - PCIe: 1x PCIe 3.0 x2 (x4 connecter) [clock/slot may not install]
> 
> Link:
> - https://appletsapi.52solution.com/media/X3568V4%E5%BC%80%E5%8F%91%E6%9D%BF%E7%A1%AC%E4%BB%B6%E6%89%8B%E5%86%8C.pdf
> - https://blog.gov.cooking/archives/research-ninetripod-x3568-v4-and-flash.html

2nd link ends in a 404 error, page not found


> Signed-off-by: Coia Prant <coiaprant@gmail.com>
> Tested-by: Coia Prant <coiaprant@gmail.com>


When you submit a patch, we expect you to have tested it, so tere
is no need to have a separate tested-by line :-) .


> ---
>  arch/arm64/boot/dts/rockchip/Makefile         |  11 +
>  .../rockchip/rk3568-x3568-camera-demo.dtso    |  82 ++
>  .../boot/dts/rockchip/rk3568-x3568-v4.dts     | 884 ++++++++++++++++++
>  .../dts/rockchip/rk3568-x3568-video-demo.dtso | 141 +++

please name your boards including the ninetree name, because x3568 is way
too generic, so
rk3568-ninetree-x3568 .....

Additionally, from that PDF above, it seems this is a system-on-module?
X3568CV2 + baseboard? If so, please split this into a dtsi + dts.
See all the other system-on-modules for reference.

Additionally, you'll need to have a 2nd patch to add the board to
Documentation/devicetree/bindings/arm/rockchip.yaml

And also possily a 3rd patch to add ninetree to
Documentation/devicetree/bindings/vendor-prefixes.yaml


Heiko



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  parent reply	other threads:[~2025-10-25 21:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-25 20:37 [PATCH] arm64: dts: rockchip: Add devicetree for the X3568 v4 Coia Prant
2025-10-25 20:37 ` Coia Prant
2025-10-25 20:38 ` kernel test robot
2025-10-25 21:03 ` Heiko Stuebner [this message]
2025-10-25 21:03   ` Heiko Stuebner
2025-10-26  9:43 ` kernel test robot
2025-10-26  9:43   ` kernel test robot
2025-10-28  3:36 ` Shawn Lin
2025-10-28  3:36   ` Shawn Lin
2025-10-28  4:03   ` Coia Prant
2025-10-28  4:03     ` Coia Prant
2025-10-29  0:20     ` Shawn Lin
2025-10-29  0:20       ` Shawn Lin
2025-10-29  4:50       ` Coia Prant
2025-10-29  4:50         ` Coia Prant

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=2940731.88bMQJbFj6@phil \
    --to=heiko@sntech.de \
    --cc=coiaprant@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=stable@vger.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.