From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8A8342D372D; Mon, 9 Feb 2026 17:03:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770656594; cv=none; b=oZ50Jk/ZdxQyGREvsaoUx1CnuCRCRYTnfV+Hhyjg9kAq/7As8rp9cwy7Z1TH2T4NjY/SQBWNlst64dWcSzPiQ99IIfHHqI/xSEfP4qmpMeZryqSoXBnaY9NjcwfyQF5k+UW6aT9SKFPTcOcDYyxFNlK0r2PTNo9XjQBqJhlGds0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770656594; c=relaxed/simple; bh=1FlN9TgpQmPj8I8PTCTKarky+VJebIipTUTRMn/3hIc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=b/kddX/PfV88kYGW7ThmQRSqjqOk6fYqLKlJJKPOkWw2yJGZh/Yi2hhau8fnJBzzh1qs94+3A4tXj5N2k9MLaV7slv+oEpqeh4Fb45yye+Wj90UYZeQsdkKuYDEzFwWH3xEfZnGAeY2OWQ+4zK6EVjM0Q3uo56TaiYNlLbora6E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=FbOtU+Wr; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="FbOtU+Wr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3FF41C116C6; Mon, 9 Feb 2026 17:03:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770656594; bh=1FlN9TgpQmPj8I8PTCTKarky+VJebIipTUTRMn/3hIc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=FbOtU+Wr1aWTYmmrzFfk5lc6Cjs1UKPd3rgkhGDCIt8t0JFq+GQd5maIxkpAho/tW LWeki2XsKYMeCTSLqHQpzSsnYsp867TWhzC0qD3YuwBOaQb7zRGSETc7N8761kfy9X 0WnhAwHdsFGuduHq1m3vW3pn5XLgTBquj9h0H9RPw7pGC04HHHowGklziC9/v5u14Z A4HPIilkkaqFakyWgUqC6OKHE2pc4PGD4icy0x5Mk/TXcA5Ebt1xYs2daShegT14mA 8zAutYY7tqw2nuqESjPDrWZCjXXOZzsneZUypbvbYcMvD6e+6OlJVrXWCkbSK0imTg G47ebwzNFKM4Q== Date: Mon, 9 Feb 2026 11:03:13 -0600 From: Rob Herring To: Aaron Kling Cc: Bjorn Andersson , Konrad Dybcio , Krzysztof Kozlowski , Conor Dooley , Kumar Sharma , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Kuldeep Singh Subject: Re: [PATCH 1/3] dt-bindings: firmware: Add tz-log doc Message-ID: <20260209170313.GA1401643-robh@kernel.org> References: <20260129-sm8550-abl-dtbo-v1-0-abca3be14024@gmail.com> <20260129-sm8550-abl-dtbo-v1-1-abca3be14024@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260129-sm8550-abl-dtbo-v1-1-abca3be14024@gmail.com> On Thu, Jan 29, 2026 at 01:46:30AM -0600, Aaron Kling wrote: > From: Kuldeep Singh > > Add device-tree bindings for qcom tz-log. Exposes a debug > interface for accessing and displaying diagnostic information > related to secure code(Trustzone/QSEE). $vendor * $firmware-component would be a lot of bindings which doesn't scale. This should be something cross-vendor and cross-component. > > Signed-off-by: Kuldeep Singh > Signed-off-by: Aaron Kling > --- > .../devicetree/bindings/firmware/qcom,tz-log.yaml | 66 ++++++++++++++++++++++ > 1 file changed, 66 insertions(+) > > diff --git a/Documentation/devicetree/bindings/firmware/qcom,tz-log.yaml b/Documentation/devicetree/bindings/firmware/qcom,tz-log.yaml > new file mode 100644 > index 0000000000000000000000000000000000000000..e5c67ca1546c2d10f4c3b5979bf7b8a1a7dd2132 > --- /dev/null > +++ b/Documentation/devicetree/bindings/firmware/qcom,tz-log.yaml > @@ -0,0 +1,66 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/firmware/qcom,tz-log.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: TZLOG (Trust Zone log) > + > +maintainers: > + - Vikas Kumar Sharma > + > +description: > + This exposes a debug interface for accessing and displaying diagnostic information > + related to secure code (Trustzone/QSEE). > + > +properties: > + compatible: > + const: qcom,tz-log > + > + reg: > + maxItems: 1 > + > + qcom,hyplog-enabled: > + type: boolean > + description: Indicates(boolean) if driver supports HYP logger service. > + > + hyplog-address-offset: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Register offset to get the HYP log base address. > + > + hyplog-size-offset: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Register offset to get the HYP log size parameter. > + > + rmlog-address: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Register offset to get resource manager log base address. > + > + rmlog-size: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Register offset to get the resource manager log size parameter. > + > + tmecrashdump-address-offset: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Define tme crashump DDR region starting offset. Wouldn't 'reg' for all of this? Though I have no clue what's in 'reg' region. > + > +required: > + - compatible > + - reg > + > +additionalProperties: false > + > +examples: > + - | > + soc { > + #address-cells = <2>; > + #size-cells = <2>; > + > + qcom_tzlog: tz-log@146bf720 { > + compatible = "qcom,tz-log"; > + reg = <0x0 0x146bf720 0x0 0x3000>; > + qcom,hyplog-enabled; > + hyplog-address-offset = <0x410>; > + hyplog-size-offset = <0x414>; > + }; > + }; > > -- > 2.52.0 >