Merge tag 'devicetree-for-5.18' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux

DT_EXTRACT_EX ?= dt-extract-example

DT_MK_SCHEMA ?= dt-mk-schema

DT_SCHEMA_LINT = $(shell which yamllint)

DT_SCHEMA_LINT = $(shell which yamllint || \

  echo "warning: python package 'yamllint' not installed, skipping" >&2)

DT_SCHEMA_MIN_VERSION = 2021.2.1

DT_SCHEMA_MIN_VERSION = 2022.3

PHONY += check_dtschema_version

check_dtschema_version:

$(obj)/%.example.dts: $(src)/%.yaml check_dtschema_version FORCE

	$(call if_changed,extract_ex)

# Use full schemas when checking %.example.dts

DT_TMP_SCHEMA := $(obj)/processed-schema-examples.json

find_all_cmd = find $(srctree)/$(src) \( -name '*.yaml' ! \

		-name 'processed-schema*' ! \

		-name '*.example.dt.yaml' \)

		-name 'processed-schema*' \)

ifeq ($(DT_SCHEMA_FILES),)

find_cmd = $(find_all_cmd)

else

find_cmd = echo $(addprefix $(srctree)/, $(DT_SCHEMA_FILES))

endif

find_cmd = $(find_all_cmd) | grep -F "$(DT_SCHEMA_FILES)"

CHK_DT_DOCS := $(shell $(find_cmd))

quiet_cmd_yamllint = LINT    $(src)

      cmd_yamllint = ($(find_cmd) | \

# Disable undocumented compatible checks until warning free

override DT_CHECKER_FLAGS ?=

$(obj)/processed-schema-examples.json: $(DT_DOCS) $(src)/.yamllint check_dtschema_version FORCE

$(obj)/processed-schema.json: $(DT_DOCS) $(src)/.yamllint check_dtschema_version FORCE

	$(call if_changed_rule,chkdt)

ifeq ($(DT_SCHEMA_FILES),)

# Unless DT_SCHEMA_FILES is specified, use the full schema for dtbs_check too.

# Just copy processed-schema-examples.json

$(obj)/processed-schema.json: $(obj)/processed-schema-examples.json FORCE

	$(call if_changed,copy)

DT_SCHEMA_FILES = $(DT_DOCS)

else

# If DT_SCHEMA_FILES is specified, use it for processed-schema.json

$(obj)/processed-schema.json: DT_MK_SCHEMA_FLAGS := -u

$(obj)/processed-schema.json: $(DT_SCHEMA_FILES) check_dtschema_version FORCE

	$(call if_changed,mk_schema)

endif

always-$(CHECK_DT_BINDING) += processed-schema-examples.json

always-$(CHECK_DTBS)       += processed-schema.json

always-$(CHECK_DT_BINDING) += $(patsubst $(src)/%.yaml,%.example.dts, $(DT_SCHEMA_FILES))

always-$(CHECK_DT_BINDING) += $(patsubst $(src)/%.yaml,%.example.dt.yaml, $(DT_SCHEMA_FILES))

always-y += processed-schema.json

always-$(CHECK_DT_BINDING) += $(patsubst $(srctree)/$(src)/%.yaml,%.example.dts, $(CHK_DT_DOCS))

always-$(CHECK_DT_BINDING) += $(patsubst $(srctree)/$(src)/%.yaml,%.example.dtb, $(CHK_DT_DOCS))

# Hack: avoid 'Argument list too long' error for 'make clean'. Remove most of

# build artifacts here before they are processed by scripts/Makefile.clean

clean-files = $(shell find $(obj) \( -name '*.example.dts' -o \

			-name '*.example.dt.yaml' \) -delete 2>/dev/null)

			-name '*.example.dtb' \) -delete 2>/dev/null)

          arm,hbi = <0x249>;

          interrupt-parent = <&gic>;

          gic: interrupt-controller {

              interrupt-controller;

              #interrupt-cells = <3>;

          };

          /*

           * This CCI node corresponds to a CCI component whose control

           * registers sits at address 0x000000002c090000.

The capacities-dmips-mhz or DMIPS/MHz values (scaled to 1024)

are 1024 and 578 for cluster0 and cluster1. Further normalization

is done by the operating system based on cluster0@max-freq=1100 and

custer1@max-freq=850, final capacities are 1024 for cluster0 and

446 for cluster1 (576*850/1100).

cluster1@max-freq=850, final capacities are 1024 for cluster0 and

446 for cluster1 (578*850/1100).

cpus {

	#address-cells = <2>;

          - ti,am4372

  cpu-release-addr:

    $ref: '/schemas/types.yaml#/definitions/uint64'

    oneOf:

      - $ref: '/schemas/types.yaml#/definitions/uint32'

      - $ref: '/schemas/types.yaml#/definitions/uint64'

    description:

      The DT specification defines this as 64-bit always, but some 32-bit Arm

      systems have used a 32-bit value which must be supported.

      Required for systems that have an "enable-method"

        property value of "spin-table".

      On ARM v8 64-bit systems must be a two cell

        property identifying a 64-bit zero-initialised

        memory location.

  cpu-idle-states:

    $ref: '/schemas/types.yaml#/definitions/phandle-array'

    items:

      maxItems: 1

    description: |

      List of phandles to idle state nodes supported

      by this cpu (see ./idle-states.yaml).

* QEMU Firmware Configuration bindings for ARM

QEMU's arm-softmmu and aarch64-softmmu emulation / virtualization targets

provide the following Firmware Configuration interface on the "virt" machine

type:

- A write-only, 16-bit wide selector (or control) register,

- a read-write, 64-bit wide data register.

QEMU exposes the control and data register to ARM guests as memory mapped

registers; their location is communicated to the guest's UEFI firmware in the

DTB that QEMU places at the bottom of the guest's DRAM.

The authoritative guest-side hardware interface documentation to the fw_cfg

device can be found in "docs/specs/fw_cfg.txt" in the QEMU source tree.

Required properties:

- compatible: "qemu,fw-cfg-mmio".

- reg: the MMIO region used by the device.

  * Bytes 0x0 to 0x7 cover the data register.

  * Bytes 0x8 to 0x9 cover the selector register.

  * Further registers may be appended to the region in case of future interface

    revisions / feature bits.

Example:

/ {

	#size-cells = <0x2>;

	#address-cells = <0x2>;

	fw-cfg@9020000 {

		compatible = "qemu,fw-cfg-mmio";

		reg = <0x0 0x9020000 0x0 0xa>;

	};

};