From: Wilken Gottwalt <wilken.gottwalt@posteo.net>
To: Bastian Germann <bage@debian.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <andersson@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/3] Enable hwlock on Allwinner A64
Date: Wed, 15 Feb 2023 05:01:25 +0000 [thread overview]
Message-ID: <20230215060125.0e06312e@posteo.net> (raw)
In-Reply-To: <d483ea28-feed-41d1-f9b6-4abfcfe42874@debian.org>
On Tue, 14 Feb 2023 22:55:45 +0100
Bastian Germann <bage@debian.org> wrote:
> Am 14.02.23 um 01:18 schrieb Andre Przywara:
> > So are there Linux/Crust patches out there that use this device?
>
> I do not know of any. I was just investigating the chip and checked the parts that I could easily
> use in Linux.
Easily using it is, well, a bit questionable. The only reason to use this is
for syncing access to hardware between the ARM and the embedded OpenRISC core.
Like Andre wrote, it only makes sense if you want to etablish some form of
shared access between Linux and the Crust firmware. Using this in Linux only
instead of the common spinlocks won't be fun, that hwspinlock unit is slower.
greetings,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-15 5:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 23:19 [PATCH 0/3] Enable hwlock on Allwinner A64 Bastian Germann
2023-02-13 23:19 ` [PATCH 1/3] dt-bindings: hwlock: sun6i: Add missing #hwlock-cells Bastian Germann
2023-02-14 0:04 ` Andre Przywara
2023-02-14 8:08 ` Krzysztof Kozlowski
2023-02-14 16:12 ` Rob Herring
2023-02-15 14:07 ` Rob Herring
2023-02-16 8:39 ` Bastian Germann
2023-02-13 23:19 ` [PATCH 2/3] dt-bindings: hwlock: sun6i: Add missing names Bastian Germann
2023-02-14 0:07 ` Andre Przywara
2023-02-14 8:09 ` Krzysztof Kozlowski
2023-02-14 9:45 ` Wilken Gottwalt
2023-02-14 12:12 ` Andre Przywara
2023-02-14 12:39 ` Krzysztof Kozlowski
2023-02-14 12:37 ` Krzysztof Kozlowski
2023-02-14 18:11 ` Andre Przywara
2023-02-16 8:15 ` Krzysztof Kozlowski
2023-02-14 12:38 ` Krzysztof Kozlowski
2023-02-13 23:19 ` [PATCH 3/3] arm64: dts: allwinner: a64: Add hwspinlock node Bastian Germann
2023-02-14 0:12 ` Andre Przywara
2023-02-14 0:18 ` [PATCH 0/3] Enable hwlock on Allwinner A64 Andre Przywara
2023-02-14 21:55 ` Bastian Germann
2023-02-15 5:01 ` Wilken Gottwalt [this message]
2023-02-14 20:57 ` (subset) " Bjorn Andersson
2023-02-15 22:31 ` Andre Przywara
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=20230215060125.0e06312e@posteo.net \
--to=wilken.gottwalt@posteo.net \
--cc=andersson@kernel.org \
--cc=andre.przywara@arm.com \
--cc=bage@debian.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).