From: sashiko-bot@kernel.org
To: "Samuel Holland" <samuel@sholland.org>
Cc: conor+dt@kernel.org, robh@kernel.org, linux-leds@vger.kernel.org,
lee@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: rockchip: Add LincStation E1
Date: Sat, 11 Jul 2026 19:35:37 +0000 [thread overview]
Message-ID: <20260711193538.0971A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260711192842.845048-5-samuel@sholland.org>
> LincStation E1 is an entry-level NAS device powered by the RK3568B2 SoC
> with two 3.5" HDD slots (behind a SATA port multiplier) and two m.2 2280
> slots for SSDs (each PCIe 3.0 x1). Other major features include:
> - 4 GiB DRAM / 64 GB eMMC
> - RTL8125 2.5 Gb Ethernet
> - Fn-Link 6222B-SRC Wi-Fi 5 / Bluetooth module
> - 1 USB 5 Gbps + 2 USB high speed ports
> - HDMI output
>
> Each HDD slot provides a GPIO input for disk presence detection and an
> output for power control. Since the disks are behind a port multiplier,
> there is no way to describe them in the devicetree, so the disk power
> is enabled at all times by GPIO hogs, and the detection inputs are used
> only as LED triggers.
>
> The board contains several pairs of amber/white LEDs for power, disk,
> m.2 slot, and network status. These are configured to use triggers when
> possible. The PWM fan uses a relatively aggressive fan curve to keep
> the hard disks within a safe temperature range. It may benefit from
> further tuning.
>
> The pinhole reset button is multiplexed between the SoC reset pin and
> an ADC input. The mux is configured here to drive the SoC reset pin, as
> this works reliably without polling by software. The adc-keys
> description is included for use by a devicetree overlay if desired.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260711192842.845048-1-samuel@sholland.org?part=4
prev parent reply other threads:[~2026-07-11 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 19:28 [PATCH 0/4] Add devicetree for LincPlus LincStation E1 Samuel Holland
2026-07-11 19:28 ` [PATCH 1/4] dt-bindings: leds: Document "gpio" trigger Samuel Holland
2026-07-11 19:32 ` sashiko-bot
2026-07-11 19:28 ` [PATCH 2/4] dt-bindings: vendor-prefixes: Add techvision Samuel Holland
2026-07-11 19:29 ` sashiko-bot
2026-07-11 19:28 ` [PATCH 3/4] dt-bindings: arm: rockchip: Add LincStation E1 Samuel Holland
2026-07-11 19:30 ` sashiko-bot
2026-07-11 19:28 ` [PATCH 4/4] arm64: dts: " Samuel Holland
2026-07-11 19:35 ` sashiko-bot [this message]
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=20260711193538.0971A1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=sashiko-reviews@lists.linux.dev \
/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