From: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: access-controllers: add controller configuration property
Date: Tue, 20 Aug 2024 11:35:55 +0200 [thread overview]
Message-ID: <b86b33d3-2ab2-49a7-a7cb-d005dc4491d6@foss.st.com> (raw)
In-Reply-To: <20240716161427.237825-1-gatien.chevallier@foss.st.com>
On 7/16/24 18:14, Gatien Chevallier wrote:
> Add a pattern property that allows to define several controller
> configuration in the device tree. It allows run-time controller
> reconfiguration for an authorized entity as in OP-TEE OS [1].
>
> Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
> Link: https://github.com/OP-TEE/optee_os/pull/6946 [1]
> ---
> .../access-controllers/access-controllers.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/access-controllers/access-controllers.yaml b/Documentation/devicetree/bindings/access-controllers/access-controllers.yaml
> index 99e2865f0e46..88824719bb73 100644
> --- a/Documentation/devicetree/bindings/access-controllers/access-controllers.yaml
> +++ b/Documentation/devicetree/bindings/access-controllers/access-controllers.yaml
> @@ -58,6 +58,13 @@ properties:
> A list of access controller specifiers, as defined by the
> bindings of the access-controllers provider.
>
> +patternProperties:
> + ".*(?<=)-access-conf$":
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + description:
> + Contains a list of inseparable access controller specifiers that forms
> + an access controller configuration.
> +
> additionalProperties: true
>
> examples:
> @@ -81,4 +88,15 @@ examples:
> <&bus_controller 1 3 5>;
> access-controller-names = "clock", "bus";
> };
> +
> + uart5: serial@60200 {
> + reg = <0x60200 0x400>;
> + clocks = <&clk_serial2>;
> + access-controllers = <&bus_controller 0 0 0>, <&bus_controller 1 0 0>,
> + <&clock_controller 2 3>;
> + default-access-conf = <&bus_controller 0 10 0>,
> + <&bus_controller 1 10 0>;
> + shared-access-conf = <&bus_controller 0 256 4>,
> + <&bus_controller 1 256 4>;
> + };
> };
Hi,
Looking back at this, I think it would be coherent to declare a
dedicated cell definition for this property. It makes little sense
to base it on the #access-controllers-cells as there could be
different arguments. Maybe #access-conf-cells.
Then, I should change the description as this property should describe
a list of access controller configuration entries. This list can contain
references to one or more controller.
What are your thoughts?
Best regards,
Gatien
prev parent reply other threads:[~2024-08-20 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 16:14 [PATCH] dt-bindings: access-controllers: add controller configuration property Gatien Chevallier
2024-08-20 9:35 ` Gatien CHEVALLIER [this message]
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=b86b33d3-2ab2-49a7-a7cb-d005dc4491d6@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=Oleksii_Moisieiev@epam.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).