From: Krzysztof Kozlowski <krzk@kernel.org>
To: Coia Prant <coiaprant@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
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,
stable@vger.kernel.org
Subject: Re: [PATCH v2 3/3] arm64: dts: rockchip: Add devicetree for the NineTripod X3568 v4
Date: Sun, 26 Oct 2025 09:36:51 +0100 [thread overview]
Message-ID: <b4395d23-9004-4a01-942f-060876312317@kernel.org> (raw)
In-Reply-To: <20251026062831.4045083-7-coiaprant@gmail.com>
On 26/10/2025 07:28, Coia Prant wrote:
> The NineTripod X3568 v4 is an RK3568-based SBC, just like the RK3568-EVB.
> It always uses soldered connections between the X3568CV2 core board and the X3568bv4 IO board.
>
> The X3568 board has multiple hardware revisions, and we currently support v4.
>
> 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
>
> Signed-off-by: Coia Prant <coiaprant@gmail.com>
> Cc: stable@vger.kernel.org
While adding vendor prefix could fall into adding quirks (it's not...),
but how is new support supposed to be bugfix or quirk?
That's definitely not right.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-26 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 6:28 [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add NineTripod Coia Prant
2025-10-26 6:28 ` [PATCH v2 2/3] dt-bindings: arm: rockchip: Add NineTripod X3568 series Coia Prant
2025-10-26 8:35 ` Krzysztof Kozlowski
2025-10-26 6:28 ` [PATCH v2 3/3] arm64: dts: rockchip: Add devicetree for the NineTripod X3568 v4 Coia Prant
2025-10-26 8:36 ` Krzysztof Kozlowski [this message]
2025-10-26 8:35 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add NineTripod Krzysztof Kozlowski
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=b4395d23-9004-4a01-942f-060876312317@kernel.org \
--to=krzk@kernel.org \
--cc=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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox