mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thierry Reding <thierry.reding@kernel.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Bartosz Golaszewski <brgl@kernel.org>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: soc: tegra: Document Nvidia Tegra modem pwrseq
Date: Wed, 27 May 2026 10:19:58 +0200	[thread overview]
Message-ID: <c97af94f-f2cb-4ea9-b477-33b6893c9461@kernel.org> (raw)
In-Reply-To: <20260523085102.51000-2-clamor95@gmail.com>

On 23/05/2026 10:51, Svyatoslav Ryhel wrote:
> Document the Tegra modem pwseq used by various devices based on the Nvidia
> Tegra SoC, describing its usage. The power sequence provides interaction
> between the modem and SoC-specific interface configurations.
> 
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
>  .../soc/tegra/nvidia,tegra-modem-pwrseq.yaml  | 49 +++++++++++++++++++
>  1 file changed, 49 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/soc/tegra/nvidia,tegra-modem-pwrseq.yaml
> 
> diff --git a/Documentation/devicetree/bindings/soc/tegra/nvidia,tegra-modem-pwrseq.yaml b/Documentation/devicetree/bindings/soc/tegra/nvidia,tegra-modem-pwrseq.yaml
> new file mode 100644
> index 000000000000..3770fd6dc2cf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/tegra/nvidia,tegra-modem-pwrseq.yaml
> @@ -0,0 +1,49 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/tegra/nvidia,tegra-modem-pwrseq.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Nvidia Tegra modem power sequence
> +
> +description:
> +  A configuration sequence used in Tegra SoCs to provide proper interaction
> +  between the application processor and the modem, as well as control over
> +  one of the SoC's USB lines for the modem.
> +
> +maintainers:
> +  - Svyatoslav Ryhel <clamor95@gmail.com>
> +
> +properties:
> +  compatible:
> +    const: nvidia,tegra-modem-pwrseq

There is no such thing as pwrseq. I pointed you to existing code showing
how to do it - PCI or USB. Fake devices won't be accepted.

Best regards,
Krzysztof

  parent reply	other threads:[~2026-05-27  8:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23  8:51 [PATCH v2 0/2] power: sequencing: Add support for " Svyatoslav Ryhel
2026-05-23  8:51 ` [PATCH v2 1/2] dt-bindings: soc: tegra: Document " Svyatoslav Ryhel
2026-05-26  9:51   ` Bartosz Golaszewski
2026-05-26 10:03     ` Svyatoslav Ryhel
2026-05-26 11:14       ` Bartosz Golaszewski
2026-05-26 12:29         ` Svyatoslav Ryhel
2026-05-26 12:34           ` Bartosz Golaszewski
2026-05-26 12:55             ` Svyatoslav Ryhel
2026-05-26 13:14               ` Bartosz Golaszewski
2026-05-26 13:41                 ` Svyatoslav Ryhel
2026-05-27  7:55                   ` Bartosz Golaszewski
2026-05-27  8:26                     ` Krzysztof Kozlowski
2026-05-27  9:06                       ` Svyatoslav Ryhel
2026-05-27  9:15                         ` Bartosz Golaszewski
2026-05-27 10:10                           ` Svyatoslav Ryhel
2026-05-27  9:20                         ` Krzysztof Kozlowski
2026-05-27 10:12                           ` Svyatoslav Ryhel
2026-05-27  8:19   ` Krzysztof Kozlowski [this message]
2026-05-23  8:51 ` [PATCH v2 2/2] power: sequencing: Add support for " Svyatoslav Ryhel
2026-05-29 14:58 ` [PATCH v2 0/2] " Svyatoslav Ryhel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c97af94f-f2cb-4ea9-b477-33b6893c9461@kernel.org \
    --to=krzk@kernel.org \
    --cc=brgl@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®