[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230214001805.6ead683d@slackpad.lan>
Date: Tue, 14 Feb 2023 00:18:05 +0000
From: Andre Przywara <andre.przywara@....com>
To: Bastian Germann <bage@...ian.org>
Cc: Wilken Gottwalt <wilken.gottwalt@...teo.net>,
Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <andersson@...nel.org>,
Baolin Wang <baolin.wang@...ux.alibaba.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Chen-Yu Tsai <wens@...e.org>,
Samuel Holland <samuel@...lland.org>,
linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-sunxi@...ts.linux.dev,
devicetree@...r.kernel.org
Subject: Re: [PATCH 0/3] Enable hwlock on Allwinner A64
On Tue, 14 Feb 2023 00:19:27 +0100
Bastian Germann <bage@...ian.org> wrote:
Hi Bastian,
> The allwinner,sun6i-a31-hwspinlock compatible driver can be used with
> the Allwinner A64 chip. Add the wiring required to enable it.
>
> The device tree schema needs some work to verify everything that is
> needed by the sun6i hwlock driver.
>
> The hwlock device was verified to be available with this series applied
> on a Pinebook.
The changes look fine, but are there any actual users of this device?
The missing binding bits you fixed demonstrate that a driver/binding
without actual users can create problems.
So are there Linux/Crust patches out there that use this device?
Cheers,
Andre
>
> Bastian Germann (3):
> dt-bindings: hwlock: sun6i: Add missing #hwlock-cells
> dt-bindings: hwlock: sun6i: Add missing names
> arm64: dts: allwinner: a64: Add hwspinlock node
>
> .../hwlock/allwinner,sun6i-a31-hwspinlock.yaml | 14 ++++++++++++++
> arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 10 ++++++++++
> 2 files changed, 24 insertions(+)
>
Powered by blists - more mailing lists