[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169773987935.1461852.15123065300008221603.b4-ty@sntech.de>
Date: Thu, 19 Oct 2023 20:26:11 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: Rob Herring <robh+dt@...nel.org>, Sam Edwards <cfsworks@...il.com>
Cc: Heiko Stuebner <heiko@...ech.de>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Sam Edwards <CFSworks@...il.com>,
Lokesh Poovaragan <loki@...meapis.com>,
linux-rockchip@...ts.infradead.org,
Daniel Kukieła <daniel@...iela.pl>,
Sven Rademakers <sven.rademakers@...il.com>
Subject: Re: [PATCH v2 0/3] Add initial devicetree for Turing RK1
On Wed, 11 Oct 2023 16:58:20 -0600, Sam Edwards wrote:
> This is the second version of my patch to bring in support for the RK3588-based
> Turing RK1 SoM. In my previous cover letter, I perhaps should have specified
> that the RK1 is a little bit unusual in that, though it *is* a true SoM, it is
> targeted toward home-hosting/edge users directly as a compute node, and as a
> result the vast majority of users will be seeing it more like a
> micro-bladeserver, rather than an off-the-shelf part meant to power a larger
> system. This was my rationale for previously sending this as a single .dts,
> targeting that use case.
>
> [...]
Applied, thanks!
[1/3] dt-bindings: vendor-prefixes: add turing
commit: 817bacc3a648cc55a0b07a699c03ecc70309ae50
[2/3] dt-bindings: arm: rockchip: Add Turing RK1
commit: e30ecfcbe4ed3706af67dff5aa1418fba6ba2c29
[3/3] arm64: dts: rockchip: Add Turing RK1 SoM support
commit: 2806a69f3fef61d7353ea8206add8ffb15064b51
I've dropped the mem-supply references from the cpu nodes.
I think some at Collabora is working on upstreaming the
cpufreq driver that will utilize those.
Until then they are not part of the binding, so please add
them via a new patch once the cpufreq support has landed.
Best regards,
--
Heiko Stuebner <heiko@...ech.de>
Powered by blists - more mailing lists