linux-kernel - Re: [PATCH v4 2/4] Bring in other reserved-memory files

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL_JsqKVRoB4W31yuSQxc5hVt2pV6zY9y-scqdoxKLpFpe349Q@mail.gmail.com>
Date:   Tue, 29 Aug 2023 16:05:04 -0500
From:   Rob Herring <robh@...nel.org>
To:     Simon Glass <sjg@...omium.org>
Cc:     devicetree@...r.kernel.org, Dhaval Sharma <dhaval@...osinc.com>,
        Mark Rutland <mark.rutland@....com>,
        Gua Guo <gua.guo@...el.com>, Tom Rini <trini@...sulko.com>,
        U-Boot Mailing List <u-boot@...ts.denx.de>,
        ron minnich <rminnich@...il.com>,
        Ard Biesheuvel <ardb@...nel.org>,
        Lean Sheng Tan <sheng.tan@...ements.com>,
        Maximilian Brune <maximilian.brune@...ements.com>,
        Chiu Chasel <chasel.chiu@...el.com>,
        lkml <linux-kernel@...r.kernel.org>,
        Yunhui Cui <cuiyunhui@...edance.com>,
        linux-acpi@...r.kernel.org, Guo Dong <guo.dong@...el.com>
Subject: Re: [PATCH v4 2/4] Bring in other reserved-memory files

On Tue, Aug 29, 2023 at 2:18 PM Simon Glass <sjg@...omium.org> wrote:
>
> Add those files from v6.5 which are already converted to yaml.
>
> Signed-off-by: Simon Glass <sjg@...omium.org>
> ---
>
> Changes in v4:
> - New patch
>
>  .../schemas/reserved-memory/framebuffer.yaml  |  52 +++++++
>  .../reserved-memory/google,open-dice.yaml     |  46 ++++++
>  .../reserved-memory/memory-region.yaml        |  40 +++++
>  .../nvidia,tegra210-emc-table.yaml            |  31 ++++
>  .../nvidia,tegra264-bpmp-shmem.yaml           |  47 ++++++
>  dtschema/schemas/reserved-memory/phram.yaml   |  47 ++++++
>  .../schemas/reserved-memory/qcom,cmd-db.yaml  |  46 ++++++
>  .../reserved-memory/qcom,rmtfs-mem.yaml       |  55 +++++++
>  dtschema/schemas/reserved-memory/ramoops.yaml | 144 ++++++++++++++++++
>  .../reserved-memory/shared-dma-pool.yaml      |  97 ++++++++++++
>  10 files changed, 605 insertions(+)

I don't think I want all of these in dtschema. Certainly not vendor
specific ones. Generally, if it's not something we'd put in the spec,
then I don't want it in dtschema. The u-boot stuff so far has been an
exception.

Probably a good rule is if it has a compatible, then it doesn't go
into dtschema. Though there's some exceptions already.

>  create mode 100644 dtschema/schemas/reserved-memory/framebuffer.yaml

Maybe

>  create mode 100644 dtschema/schemas/reserved-memory/google,open-dice.yaml

No

>  create mode 100644 dtschema/schemas/reserved-memory/memory-region.yaml

Yes

>  create mode 100644 dtschema/schemas/reserved-memory/nvidia,tegra210-emc-table.yaml
>  create mode 100644 dtschema/schemas/reserved-memory/nvidia,tegra264-bpmp-shmem.yaml

No

>  create mode 100644 dtschema/schemas/reserved-memory/phram.yaml

Depends on mtd.yaml in the kernel, so no.

>  create mode 100644 dtschema/schemas/reserved-memory/qcom,cmd-db.yaml
>  create mode 100644 dtschema/schemas/reserved-memory/qcom,rmtfs-mem.yaml

No.

>  create mode 100644 dtschema/schemas/reserved-memory/ramoops.yaml

Probably not.

>  create mode 100644 dtschema/schemas/reserved-memory/shared-dma-pool.yaml

Maybe.

Rob