Re: [PATCH] dt-bindings: Drop kernel copy of common reserved-memory bindings
On Fri, 13 Oct 2023 15:08:49 -0500, Rob Herring wrote: > The common reserved-memory bindings have recently been copied from the > kernel tree into dtschema. The preference is to host common, stable > bindings in dtschema. As reserved-memory is documented in the DT Spec, > it meets the criteria. > > The v2023.09 version of dtschema is what contains the reserved-memory > schemas we depend on, so bump the minimum version to that. Otherwise, > references to these schemas will generate errors. > > Signed-off-by: Rob Herring > --- > Documentation/devicetree/bindings/Makefile| 2 +- > .../remoteproc/renesas,rcar-rproc.yaml| 2 +- > .../bindings/reserved-memory/framebuffer.yaml | 52 - > .../reserved-memory/memory-region.yaml| 40 > .../reserved-memory/reserved-memory.txt | 2 +- > .../reserved-memory/reserved-memory.yaml | 181 -- > .../reserved-memory/shared-dma-pool.yaml | 97 -- > .../bindings/sound/mediatek,mt8188-afe.yaml | 2 +- > 8 files changed, 4 insertions(+), 374 deletions(-) > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/memory-region.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml > Applied, thanks!
Re: [PATCH] dt-bindings: Drop kernel copy of common reserved-memory bindings
Hi Rob, kernel test robot noticed the following build errors: [auto build test ERROR on robh/for-next] [also build test ERROR on krzk-dt/for-next remoteproc/rproc-next broonie-sound/for-next linus/master v6.6-rc6 next-20231018] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Rob-Herring/dt-bindings-Drop-kernel-copy-of-common-reserved-memory-bindings/20231017-125913 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20231013200851.347042-1-robh%40kernel.org patch subject: [PATCH] dt-bindings: Drop kernel copy of common reserved-memory bindings config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20231019/202310191537.20z1aolb-...@intel.com/config) compiler: aarch64-linux-gcc (GCC) 13.2.0 reproduce: (https://download.01.org/0day-ci/archive/20231019/202310191537.20z1aolb-...@intel.com/reproduce) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot | Closes: https://lore.kernel.org/oe-kbuild-all/202310191537.20z1aolb-...@intel.com/ All errors (new ones prefixed by >>): sort: -:2: disorder: 2023.8.dev2+gd5e5147 >> ERROR: dtschema minimum version is v2023.9 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] dt-bindings: Drop kernel copy of common reserved-memory bindings
On Fri, Oct 13, 2023 at 03:08:49PM -0500, Rob Herring wrote: > The common reserved-memory bindings have recently been copied from the > kernel tree into dtschema. The preference is to host common, stable > bindings in dtschema. As reserved-memory is documented in the DT Spec, > it meets the criteria. > > The v2023.09 version of dtschema is what contains the reserved-memory > schemas we depend on, so bump the minimum version to that. Otherwise, > references to these schemas will generate errors. > > Signed-off-by: Rob Herring > --- > Documentation/devicetree/bindings/Makefile| 2 +- > .../remoteproc/renesas,rcar-rproc.yaml| 2 +- > .../bindings/reserved-memory/framebuffer.yaml | 52 - > .../reserved-memory/memory-region.yaml| 40 > .../reserved-memory/reserved-memory.txt | 2 +- > .../reserved-memory/reserved-memory.yaml | 181 -- > .../reserved-memory/shared-dma-pool.yaml | 97 -- > .../bindings/sound/mediatek,mt8188-afe.yaml | 2 +- > 8 files changed, 4 insertions(+), 374 deletions(-) > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/memory-region.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml > > diff --git a/Documentation/devicetree/bindings/Makefile > b/Documentation/devicetree/bindings/Makefile > index 8b395893bd85..3e886194b043 100644 > --- a/Documentation/devicetree/bindings/Makefile > +++ b/Documentation/devicetree/bindings/Makefile > @@ -6,7 +6,7 @@ DT_MK_SCHEMA ?= dt-mk-schema > DT_SCHEMA_LINT = $(shell which yamllint || \ >echo "warning: python package 'yamllint' not installed, skipping" >&2) > > -DT_SCHEMA_MIN_VERSION = 2022.3 > +DT_SCHEMA_MIN_VERSION = 2023.9 > > PHONY += check_dtschema_version > check_dtschema_version: > diff --git > a/Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml > b/Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml > index 4bea679a0f61..5c280117dc93 100644 > --- a/Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml > +++ b/Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml > @@ -31,7 +31,7 @@ properties: >remoteproc device. This is variable and describes the memories shared > with >the remote processor (e.g. remoteproc firmware and carveouts, rpmsg >vrings, ...). > - (see ../reserved-memory/reserved-memory.yaml) > + (see reserved-memory/reserved-memory.yaml in dtschema project) Reviewed-by: Mathieu Poirier > > required: >- compatible > diff --git > a/Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml > b/Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml > deleted file mode 100644 > index 851ec24d6142.. > --- a/Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml > +++ /dev/null > @@ -1,52 +0,0 @@ > -# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > -%YAML 1.2 > > -$id: http://devicetree.org/schemas/reserved-memory/framebuffer.yaml# > -$schema: http://devicetree.org/meta-schemas/core.yaml# > - > -title: /reserved-memory framebuffer node > - > -maintainers: > - - devicetree-s...@vger.kernel.org > - > -allOf: > - - $ref: reserved-memory.yaml > - > -properties: > - compatible: > -const: framebuffer > -description: > > - This indicates a region of memory meant to be used as a framebuffer for > - a set of display devices. It can be used by an operating system to keep > - the framebuffer from being overwritten and use it as the backing memory > - for a display device (such as simple-framebuffer). > - > -unevaluatedProperties: false > - > -examples: > - - | > -/ { > -compatible = "foo"; > -model = "foo"; > -#address-cells = <1>; > -#size-cells = <1>; > - > -chosen { > -framebuffer { > -compatible = "simple-framebuffer"; > -memory-region = <>; > -}; > -}; > - > -reserved-memory { > -#address-cells = <1>; > -#size-cells = <1>; > -ranges; > - > -fb: framebuffer@8000 { > -compatible = "framebuffer"; > -reg = <0x8000 0x007e9000>; > -}; > -}; > -}; > -... > diff --git > a/Documentation/devicetree/bindings/reserved-memory/memory-region.yaml > b/Documentation/devicetree/bindings/reserved-memory/memory-region.yaml > deleted file mode 100644 > index 592f180e6b0d.. > --- a/Documentation/devicetree/bindings/reserved-memory/memory-region.yaml > +++ /dev/null > @@ -1,40 +0,0 @@ > -# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > -%YAML 1.2 > > -$id:
Re: [PATCH] dt-bindings: Drop kernel copy of common reserved-memory bindings
On Fri, 13 Oct 2023 at 13:45, Rob Herring wrote: > > The common reserved-memory bindings have recently been copied from the > kernel tree into dtschema. The preference is to host common, stable > bindings in dtschema. As reserved-memory is documented in the DT Spec, > it meets the criteria. > > The v2023.09 version of dtschema is what contains the reserved-memory > schemas we depend on, so bump the minimum version to that. Otherwise, > references to these schemas will generate errors. > > Signed-off-by: Rob Herring > --- > Documentation/devicetree/bindings/Makefile| 2 +- > .../remoteproc/renesas,rcar-rproc.yaml| 2 +- > .../bindings/reserved-memory/framebuffer.yaml | 52 - > .../reserved-memory/memory-region.yaml| 40 > .../reserved-memory/reserved-memory.txt | 2 +- > .../reserved-memory/reserved-memory.yaml | 181 -- > .../reserved-memory/shared-dma-pool.yaml | 97 -- > .../bindings/sound/mediatek,mt8188-afe.yaml | 2 +- > 8 files changed, 4 insertions(+), 374 deletions(-) > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/memory-region.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml > delete mode 100644 > Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml > Reviewed-by: Simon Glass
[PATCH] dt-bindings: Drop kernel copy of common reserved-memory bindings
The common reserved-memory bindings have recently been copied from the kernel tree into dtschema. The preference is to host common, stable bindings in dtschema. As reserved-memory is documented in the DT Spec, it meets the criteria. The v2023.09 version of dtschema is what contains the reserved-memory schemas we depend on, so bump the minimum version to that. Otherwise, references to these schemas will generate errors. Signed-off-by: Rob Herring --- Documentation/devicetree/bindings/Makefile| 2 +- .../remoteproc/renesas,rcar-rproc.yaml| 2 +- .../bindings/reserved-memory/framebuffer.yaml | 52 - .../reserved-memory/memory-region.yaml| 40 .../reserved-memory/reserved-memory.txt | 2 +- .../reserved-memory/reserved-memory.yaml | 181 -- .../reserved-memory/shared-dma-pool.yaml | 97 -- .../bindings/sound/mediatek,mt8188-afe.yaml | 2 +- 8 files changed, 4 insertions(+), 374 deletions(-) delete mode 100644 Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml delete mode 100644 Documentation/devicetree/bindings/reserved-memory/memory-region.yaml delete mode 100644 Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml delete mode 100644 Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml diff --git a/Documentation/devicetree/bindings/Makefile b/Documentation/devicetree/bindings/Makefile index 8b395893bd85..3e886194b043 100644 --- a/Documentation/devicetree/bindings/Makefile +++ b/Documentation/devicetree/bindings/Makefile @@ -6,7 +6,7 @@ DT_MK_SCHEMA ?= dt-mk-schema DT_SCHEMA_LINT = $(shell which yamllint || \ echo "warning: python package 'yamllint' not installed, skipping" >&2) -DT_SCHEMA_MIN_VERSION = 2022.3 +DT_SCHEMA_MIN_VERSION = 2023.9 PHONY += check_dtschema_version check_dtschema_version: diff --git a/Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml index 4bea679a0f61..5c280117dc93 100644 --- a/Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml +++ b/Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml @@ -31,7 +31,7 @@ properties: remoteproc device. This is variable and describes the memories shared with the remote processor (e.g. remoteproc firmware and carveouts, rpmsg vrings, ...). - (see ../reserved-memory/reserved-memory.yaml) + (see reserved-memory/reserved-memory.yaml in dtschema project) required: - compatible diff --git a/Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml b/Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml deleted file mode 100644 index 851ec24d6142.. --- a/Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml +++ /dev/null @@ -1,52 +0,0 @@ -# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) -%YAML 1.2 -$id: http://devicetree.org/schemas/reserved-memory/framebuffer.yaml# -$schema: http://devicetree.org/meta-schemas/core.yaml# - -title: /reserved-memory framebuffer node - -maintainers: - - devicetree-s...@vger.kernel.org - -allOf: - - $ref: reserved-memory.yaml - -properties: - compatible: -const: framebuffer -description: > - This indicates a region of memory meant to be used as a framebuffer for - a set of display devices. It can be used by an operating system to keep - the framebuffer from being overwritten and use it as the backing memory - for a display device (such as simple-framebuffer). - -unevaluatedProperties: false - -examples: - - | -/ { -compatible = "foo"; -model = "foo"; -#address-cells = <1>; -#size-cells = <1>; - -chosen { -framebuffer { -compatible = "simple-framebuffer"; -memory-region = <>; -}; -}; - -reserved-memory { -#address-cells = <1>; -#size-cells = <1>; -ranges; - -fb: framebuffer@8000 { -compatible = "framebuffer"; -reg = <0x8000 0x007e9000>; -}; -}; -}; -... diff --git a/Documentation/devicetree/bindings/reserved-memory/memory-region.yaml b/Documentation/devicetree/bindings/reserved-memory/memory-region.yaml deleted file mode 100644 index 592f180e6b0d.. --- a/Documentation/devicetree/bindings/reserved-memory/memory-region.yaml +++ /dev/null @@ -1,40 +0,0 @@ -# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) -%YAML 1.2 -$id: http://devicetree.org/schemas/reserved-memory/memory-region.yaml# -$schema: http://devicetree.org/meta-schemas/core.yaml# - -title: Reserved Memory Region - -maintainers: - - devicetree-s...@vger.kernel.org - -description: | - Regions in the /reserved-memory node may be referenced by other device - nodes by adding a memory-region property to the device node. -