From: Wilken Gottwalt <wilken.gottwalt@posteo.net>
To: Maxime Ripard <maxime@cerno.tech>
Cc: linux-kernel@vger.kernel.org, Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Baolin Wang <baolin.wang7@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>
Subject: Re: [PATCH v5 2/2] hwspinlock: add sun6i hardware spinlock support
Date: Thu, 7 Jan 2021 09:43:14 +0100 [thread overview]
Message-ID: <20210107094314.4cfd5756@monster.powergraphx.local> (raw)
In-Reply-To: <20210106101542.zziwdyhq7arysrsj@gilmour>
On Wed, 6 Jan 2021 11:15:42 +0100
Maxime Ripard <maxime@cerno.tech> wrote:
> On Wed, Dec 23, 2020 at 12:35:10PM +0100, Wilken Gottwalt wrote:
> > Adds the sun6i_hwspinlock driver for the hardware spinlock unit found in
> > most of the sun6i compatible SoCs.
> >
> > This unit provides at least 32 spinlocks in hardware. The implementation
> > supports 32, 64, 128 or 256 32bit registers. A lock can be taken by
> > reading a register and released by writing a 0 to it. This driver
> > supports all 4 spinlock setups, but for now only the first setup (32
> > locks) seem to exist in available devices. This spinlock unit is shared
> > between all ARM cores and the embedded companion core. All of them can
> > take/release a lock with a single cycle operation. It can be used to
> > sync access to devices shared by the ARM cores and the companion core.
> >
> > There are two ways to check if a lock is taken. The first way is to read
> > a lock. If a 0 is returned, the lock was free and is taken now. If an 1
> > is returned, the caller has to try again. Which means the lock is taken.
> > The second way is to read a 32bit wide status register where every bit
> > represents one of the 32 first locks. According to the datasheets this
> > status register supports only the 32 first locks. This is the reason the
> > first way (lock read/write) approach is used to be able to cover all 256
> > locks in future devices. The driver also reports the amount of supported
> > locks via debugfs.
> >
> > Signed-off-by: Wilken Gottwalt <wilken.gottwalt@posteo.net>
>
> Reviewed-by: Maxime Ripard <mripard@kernel.org>
Does it mean the driver is okay and I only need to fix the bindings
documentation? If so, would you prefer an updated patch set or only the
documentation patch in a new version?
> Thanks!
> Maxime
next prev parent reply other threads:[~2021-01-07 8:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 11:34 [PATCH v5 0/2] hwspinlock: add sun6i hardware spinlock support Wilken Gottwalt
2020-12-23 11:34 ` [PATCH v5 1/2] dt-bindings: hwlock: add sun6i_hwspinlock Wilken Gottwalt
2020-12-23 22:49 ` Rob Herring
2021-01-06 10:14 ` Maxime Ripard
2021-01-07 8:36 ` Wilken Gottwalt
2021-02-07 9:07 ` Wilken Gottwalt
2021-02-09 18:48 ` Maxime Ripard
2020-12-23 11:35 ` [PATCH v5 2/2] hwspinlock: add sun6i hardware spinlock support Wilken Gottwalt
2021-01-06 10:15 ` Maxime Ripard
2021-01-07 8:43 ` Wilken Gottwalt [this message]
2021-01-08 8:57 ` Maxime Ripard
2021-01-07 17:43 ` Bjorn Andersson
2021-01-08 8:50 ` Wilken Gottwalt
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=20210107094314.4cfd5756@monster.powergraphx.local \
--to=wilken.gottwalt@posteo.net \
--cc=baolin.wang7@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.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