The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mikko Perttunen <mperttunen@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Thierry Reding <thierry.reding@kernel.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: display: tegra: Add channel/syncpoint range properties
Date: Mon, 29 Jun 2026 13:02:59 +0900	[thread overview]
Message-ID: <xLshrt-qQoOT-VB3QjfvBA@nvidia.com> (raw)
In-Reply-To: <20260626-sceptical-aardvark-from-mars-cedf81@quoll>

On Friday, June 26, 2026 7:26 PM Krzysztof Kozlowski wrote:
> On Thu, Jun 25, 2026 at 06:26:43PM +0900, Mikko Perttunen wrote:
> > On Thursday, June 25, 2026 5:36 PM Krzysztof Kozlowski wrote:
> > > On Mon, Jun 22, 2026 at 05:22:51PM +0900, Mikko Perttunen wrote:
> > > > Channels and syncpoints available may be limited when other system
> > > 
> > > What are channels and syncpoints?
> > 
> > Very host1x-specific hardware resources. Somewhat close to GPU channels
> > and semaphores / fences if you're familiar with those.
> > 
> > > 
> > > > components are using them. Add properties nvidia,channels and
> > > > nvidia,syncpoints to limit the range of usable channels and/or
> > > > syncpoints.
> > > 
> > > Why isn't this deducible from the compatible?
> > 
> > When Host1x is partitioned, the hypervisor (or other software entity
> > with access to the non-vm host1x register regions) can configure which
> > channels and syncpoints are available to each partition arbitrarily.
> 
> So you will have different boards for the same SoC with different
> values?
> 

Yes -- even the same board will have different values depending on the
use case of the system. The hypervisor or bootloader has to update the
properties according to the configuration it has programmed in the
hardware.

I will update the commit message with clarification.

> > 
> > How that partitioning was done is not discoverable through hardware
> > directly, so we need to pass that information through device tree.
> > 
> > > 
> > > Also, nvidia,channels is too broad/generic. This is not ADC, right? And
> > > channels is a common term in IIO. And in few other cases.
> > 
> > It's not ADC. Yes, it's a common term in a lot of contexts. I can call
> > it nvidia,host1x-channels if you prefer but that seems a bit redundant
> > given the context.
> 
> host1x is indeed poor, but maybe there is some way to be a bit more
> descriptive? message-channels?

I would prefer to keep these as is -- anyone working with host1x will
know what 'channels' and 'syncpoints' mean, and changing the name could
cause confusion since the name would not match other code or
documentation discussing these.

I can update the binding documentation with some more explanation about
what these properties mean.

Thank you
Mikko

> 
> Best regards,
> Krzysztof
> 





  reply	other threads:[~2026-06-29  4:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22  8:22 [PATCH 0/4] Support partitioned Host1x Mikko Perttunen
2026-06-22  8:22 ` [PATCH 1/4] dt-bindings: display: tegra: Make non-vm registers optional Mikko Perttunen
2026-06-25  8:34   ` Krzysztof Kozlowski
2026-06-25  9:17     ` Mikko Perttunen
2026-06-26 10:21       ` Krzysztof Kozlowski
2026-06-22  8:22 ` [PATCH 2/4] dt-bindings: display: tegra: Add channel/syncpoint range properties Mikko Perttunen
2026-06-25  8:36   ` Krzysztof Kozlowski
2026-06-25  9:26     ` Mikko Perttunen
2026-06-26 10:26       ` Krzysztof Kozlowski
2026-06-29  4:02         ` Mikko Perttunen [this message]
2026-06-22  8:22 ` [PATCH 3/4] gpu: host1x: Support running without hv/common registers Mikko Perttunen
2026-06-22  8:22 ` [PATCH 4/4] gpu: host1x: Allow limiting usable channel and syncpoint ranges Mikko Perttunen

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=xLshrt-qQoOT-VB3QjfvBA@nvidia.com \
    --to=mperttunen@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=thierry.reding@kernel.org \
    --cc=tzimmermann@suse.de \
    /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