[RFC][PATCH v3 16/16] dt-bindings: Add Google Kinfo
Krzysztof Kozlowski
krzk at kernel.org
Sun Sep 14 04:56:23 PDT 2025
On 12/09/2025 17:08, Eugen Hristev wrote:
> Add documentation for Google Kinfo kmemdump backend driver.
>
> Signed-off-by: Eugen Hristev <eugen.hristev at linaro.org>
> ---
> .../bindings/misc/google,kinfo.yaml | 36 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 37 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/google,kinfo.yaml
>
> diff --git a/Documentation/devicetree/bindings/misc/google,kinfo.yaml b/Documentation/devicetree/bindings/misc/google,kinfo.yaml
> new file mode 100644
> index 000000000000..b1e4fac43586
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/google,kinfo.yaml
> @@ -0,0 +1,36 @@
> +# SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/misc/google,kinfo.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Google Pixel Kinfo debug driver
> +
> +maintainers:
> + - Eugen Hristev <eugen.hristev at linaro.org>
> +
> +description:
> + The Google Pixel Kinfo debug driver uses a supplied reserved memory area
> + to save debugging information on the running kernel.
Bindings should be for hardware, not drivers, so this does not belong to
DT. It might be a dedicated reserved memory node, though.
Best regards,
Krzysztof
More information about the linux-arm-kernel
mailing list