Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Coia Prant <coiaprant@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>, 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>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] arm64: dts: rockchip: Add devicetree for the 9Tripod X3568 v4
Date: Fri, 07 Nov 2025 13:45:10 +0800	[thread overview]
Message-ID: <8AD7010C-A0E9-4CF5-B66D-1E1A01CF0B43@gmail.com> (raw)
In-Reply-To: <3719039.iIbC2pHGDl@phil>

On November 7, 2025 6:54:45 AM GMT+08:00, Heiko Stuebner <heiko@sntech.de> wrote:
>Am Montag, 3. November 2025, 18:17:02 Mitteleuropäische Normalzeit schrieb Coia Prant:
>> The 9Tripod X3568 v4 is an RK3568-based SBC, just like the RK3568-EVB.
>> It always uses soldered connections between the X3568CV2/X3568CV3/X3568CV4 core board
>> and the X3568bv4 I/O board.
>> 
>> The differences between the core boards
>> - PCB size, layout
>> - CPU (RKK3568B2/RK3568J)
>> - Memory type (DDR4/LPDDR4/LPDDR4X) and size
>> - eMMC size
>> - DSI/EDP resistor values
>> Although the components vary, they maintain full compatibility.
>> 
>> The X3568 board has multiple hardware revisions, and we currently support v4 (I/O board).
>> 
>> Specification:
>> - SoC: RockChip RK3568 ARM64 (4 cores)
>> - eMMC: 16-128 GB
>> - RAM: 2-16 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) [power/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
>> 
>> Signed-off-by: Coia Prant <coiaprant@gmail.com>
>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3568-9tripod-x3568-v4-video-demo.dtso b/arch/arm64/boot/dts/rockchip/rk3568-9tripod-x3568-v4-video-demo.dtso
>> new file mode 100644
>> index 000000000..e7fa1ca48
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/rockchip/rk3568-9tripod-x3568-v4-video-demo.dtso
>> @@ -0,0 +1,154 @@
>> +// SPDX-License-Identifier: (GPL-2.0-or-later OR MIT)
>> +
>> +// This is a sample reference, due to lack of hardware can not be tested, at your own risk
>
>and I've also dropped the 2nd overlay now.
>Please only ever submit patches for stuff you have actually tested.
>
>We don't really add stuff with "use at your own risk" caveats ;-)
>
>
>Heiko
>
>

Okay.

I'll ask if anyone has a camera and a screen.
This part is extracted from the original equipment tree, and has been corrected by reference to other board.

If I can find a test, I will submit a new patch.

Thanks!
Wish have a good day.

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

  reply	other threads:[~2025-11-07  5:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 17:16 [PATCH v5 0/3] Add devicetree for the 9Tripod X3568 v4 Coia Prant
2025-11-03 17:17 ` [PATCH v5 1/3] dt-bindings: vendor-prefixes: Add 9Tripod Coia Prant
2025-11-04  8:00   ` Krzysztof Kozlowski
2025-11-03 17:17 ` [PATCH v5 2/3] dt-bindings: arm: rockchip: Add 9Tripod X3568 series Coia Prant
2025-11-04  8:01   ` Krzysztof Kozlowski
2025-11-03 17:17 ` [PATCH v5 3/3] arm64: dts: rockchip: Add devicetree for the 9Tripod X3568 v4 Coia Prant
2025-11-06 22:51   ` Heiko Stuebner
2025-11-06 22:54   ` Heiko Stuebner
2025-11-07  5:45     ` Coia Prant [this message]
2025-11-07 11:00   ` Chukun Pan
2025-11-07 11:36     ` Coia Prant
2025-11-13 13:00       ` Chukun Pan
2025-11-06 22:58 ` [PATCH v5 0/3] " Heiko Stuebner

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=8AD7010C-A0E9-4CF5-B66D-1E1A01CF0B43@gmail.com \
    --to=coiaprant@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --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 \
    /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