From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
lee.jones@linaro.org
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, arnd@arndb.de,
matthias.bgg@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, nfraprado@collabora.com,
kernel@collabora.com
Subject: Re: [PATCH 2/2] dt-bindings: mfd: syscon: Add support for regmap fast-io
Date: Sat, 2 Apr 2022 13:38:40 +0200 [thread overview]
Message-ID: <8588a941-6d3e-9e14-cb21-d7af29b4b2bd@linaro.org> (raw)
In-Reply-To: <20220401135048.23245-3-angelogioacchino.delregno@collabora.com>
On 01/04/2022 15:50, AngeloGioacchino Del Regno wrote:
> The syscon driver now enables the .fast_io regmap configuration when
> the 'fast-io' property is found in a syscon node.
>
> Keeping in mind that, in regmap, fast_io is checked only if we are
> not using hardware spinlocks, allow the fast-io property only if
> there is no hwlocks reference (and vice-versa).
I have doubts you need a property for this. "fast" is subjective in
terms of hardware, so this looks more like a software property, not
hardware.
I think most of MMIOs inside a SoC are considered fast. Usually also the
syscon/regmap consumer knows which regmap it gets, so knows that it is
fast or not.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> Documentation/devicetree/bindings/mfd/syscon.yaml | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
> index 13baa452cc9d..85a2e83b5861 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
> @@ -83,11 +83,26 @@ properties:
> $ref: /schemas/types.yaml#/definitions/uint32
> enum: [1, 2, 4, 8]
>
> + fast-io:
> + description:
> + Indicates that this bus has a very fast IO, for which
> + acquiring a mutex would be significant overhead.
> + When present, regmap will use a spinlock instead.
Regmap is current implementation behind this, but it's not related to
hardware, so how about removing it from the description? Something like:
"..., for which different locking methods should be used to reduce
overhead (e.g. spinlock instead of mutex)."
> + type: boolean
> +
> hwlocks:
> maxItems: 1
> description:
> Reference to a phandle of a hardware spinlock provider node.
>
> +if:
> + required:
> + - hwlocks
> +then:
> + not:
> + required:
> + - fast-io
> +
> required:
> - compatible
> - reg
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-02 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 13:50 [PATCH 0/2] Allow syscon to use spinlocks with regmap fast_io AngeloGioacchino Del Regno
2022-04-01 13:50 ` [PATCH 1/2] mfd: syscon: Allow using " AngeloGioacchino Del Regno
2022-04-01 13:50 ` [PATCH 2/2] dt-bindings: mfd: syscon: Add support for regmap fast-io AngeloGioacchino Del Regno
2022-04-02 11:38 ` Krzysztof Kozlowski [this message]
2022-04-04 8:40 ` AngeloGioacchino Del Regno
2022-04-04 8:55 ` Krzysztof Kozlowski
2022-04-04 9:39 ` AngeloGioacchino Del Regno
2022-04-04 22:26 ` Nícolas F. R. A. Prado
2022-04-05 6:48 ` Krzysztof Kozlowski
2022-04-05 8:34 ` AngeloGioacchino Del Regno
2022-04-05 8:52 ` AngeloGioacchino Del Regno
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=8588a941-6d3e-9e14-cb21-d7af29b4b2bd@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®