From: Stanislav Jakubek <stano.jakubek@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: firmware: brcm,kona-smc: convert to YAML
Date: Mon, 8 May 2023 11:41:33 +0200 [thread overview]
Message-ID: <20230508094133.GA10980@standask-GA-A55M-S2HP> (raw)
In-Reply-To: <0ce9003a-5dd2-8dd0-2fa8-96ceaf954d50@linaro.org>
On Mon, May 08, 2023 at 11:23:52AM +0200, Krzysztof Kozlowski wrote:
> On 08/05/2023 10:10, Stanislav Jakubek wrote:
> > Convert Broadcom Kona family Secure Monitor bounce buffer bindings
> > to DT schema.
> >
> > Changes during conversion:
> > - move from misc to firmware subdirectory
> > - add used, but previously undocumented SoC-specific compatibles
> > - drop deprecated compatibles (they've been deprecated for ~10 years)
> >
> > Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
> > ---
> >
> > Changes in V2:
> > - move to firmware subdirectory (Krzysztof)
> > - drop deprecated compatibles (Krzysztof)
> > - adjusted commit message to reflect the above changes
> >
> > .../bindings/firmware/brcm,kona-smc.yaml | 40 +++++++++++++++++++
> > .../bindings/misc/brcm,kona-smc.txt | 15 -------
> > 2 files changed, 40 insertions(+), 15 deletions(-)
> > create mode 100644 Documentation/devicetree/bindings/firmware/brcm,kona-smc.yaml
> > delete mode 100644 Documentation/devicetree/bindings/misc/brcm,kona-smc.txt
> >
> > diff --git a/Documentation/devicetree/bindings/firmware/brcm,kona-smc.yaml b/Documentation/devicetree/bindings/firmware/brcm,kona-smc.yaml
> > new file mode 100644
> > index 000000000000..16c7928a0daa
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/firmware/brcm,kona-smc.yaml
> > @@ -0,0 +1,40 @@
> > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/firmware/brcm,kona-smc.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Broadcom Kona family Secure Monitor bounce buffer
> > +
> > +description:
> > + A bounce buffer used for non-secure to secure communications.
> > +
> > +maintainers:
> > + - Florian Fainelli <f.fainelli@gmail.com>
> > +
> > +properties:
> > + compatible:
> > + oneOf:
>
> You do not need oneOf.
Nice catch! Seems I forgot to remove it when removing the deprecated
compatibles. Will fix in V3.
Stanislav
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-05-08 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 8:10 [PATCH v2] dt-bindings: firmware: brcm,kona-smc: convert to YAML Stanislav Jakubek
2023-05-08 9:23 ` Krzysztof Kozlowski
2023-05-08 9:41 ` Stanislav Jakubek [this message]
2023-05-08 9:27 ` Rob Herring
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=20230508094133.GA10980@standask-GA-A55M-S2HP \
--to=stano.jakubek@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
/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).