All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: amadeus@jmu.edu.cn, conor+dt@kernel.org,
	devicetree@vger.kernel.org, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	naoki@radxa.com, robh@kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: disable display subsystem for Radxa E52C
Date: Mon, 11 Aug 2025 15:03:34 +0200	[thread overview]
Message-ID: <2784232.uZKlY2gecq@diego> (raw)
In-Reply-To: <20250811130108.462673-1-amadeus@jmu.edu.cn>

Hi,

Am Montag, 11. August 2025, 15:01:08 Mitteleuropäische Sommerzeit schrieb Chukun Pan:
> > What actual problem does this fix?
> >
> > For example we also enable on-soc iommus all the time, because they're
> > on the soc and don't need board-level properties.
> >
> > The "display-subsystem" without users looks mostly in the same spot.
> >
> > So I do expect a description of what problem gets fixed that this needs
> > to be disabled.
> 
> Disable the display-subsystem to remove this error log:
> [    1.382440] rockchip-drm display-subsystem: [drm:0xffffa3985873555c] *ERROR* No available vop found for display-subsystem.

ok, that makes sense then

> I will improve the commit message in v2. Do I need to remove the Fixes tag?

Nope, please keep the fixes tag

Thanks
Heiko




WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: amadeus@jmu.edu.cn, conor+dt@kernel.org,
	devicetree@vger.kernel.org, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	naoki@radxa.com, robh@kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: disable display subsystem for Radxa E52C
Date: Mon, 11 Aug 2025 15:03:34 +0200	[thread overview]
Message-ID: <2784232.uZKlY2gecq@diego> (raw)
In-Reply-To: <20250811130108.462673-1-amadeus@jmu.edu.cn>

Hi,

Am Montag, 11. August 2025, 15:01:08 Mitteleuropäische Sommerzeit schrieb Chukun Pan:
> > What actual problem does this fix?
> >
> > For example we also enable on-soc iommus all the time, because they're
> > on the soc and don't need board-level properties.
> >
> > The "display-subsystem" without users looks mostly in the same spot.
> >
> > So I do expect a description of what problem gets fixed that this needs
> > to be disabled.
> 
> Disable the display-subsystem to remove this error log:
> [    1.382440] rockchip-drm display-subsystem: [drm:0xffffa3985873555c] *ERROR* No available vop found for display-subsystem.

ok, that makes sense then

> I will improve the commit message in v2. Do I need to remove the Fixes tag?

Nope, please keep the fixes tag

Thanks
Heiko



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2025-08-11 13:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10 10:00 [PATCH 1/3] arm64: dts: rockchip: disable display subsystem for Radxa E52C Chukun Pan
2025-08-10 10:00 ` Chukun Pan
2025-08-10 10:00 ` [PATCH 2/3] arm64: dts: rockchip: mark eeprom as read-only " Chukun Pan
2025-08-10 10:00   ` Chukun Pan
2025-08-10 10:00 ` [PATCH 3/3] arm64: dts: rockchip: improve LED config for " Chukun Pan
2025-08-10 10:00   ` Chukun Pan
2025-08-11  6:30 ` [PATCH 1/3] arm64: dts: rockchip: disable display subsystem " Heiko Stübner
2025-08-11  6:30   ` Heiko Stübner
2025-08-11 13:01   ` Chukun Pan
2025-08-11 13:01     ` Chukun Pan
2025-08-11 13:03     ` Heiko Stübner [this message]
2025-08-11 13:03       ` Heiko Stübner
2025-08-11  7:52 ` (subset) " Heiko Stuebner
2025-08-11  7:52   ` Heiko Stuebner

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=2784232.uZKlY2gecq@diego \
    --to=heiko@sntech.de \
    --cc=amadeus@jmu.edu.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=naoki@radxa.com \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.