public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Tomeu Vizoso <tomeu@tomeuvizoso.net>
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Heiko Stuebner <heiko@sntech.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: Issues with DRM_ACCEL_ROCKET (Oops, power-domain, probe-ordering)
Date: Wed, 10 Dec 2025 18:47:42 +0800	[thread overview]
Message-ID: <e7b2ceaf-1fbd-4f02-9d75-be4feab724e3@rock-chips.com> (raw)
In-Reply-To: <CAAObsKABYQnw9rUfxwTS-yiQSoH9rdxZ_ffUBtp2H3tMJqMb7w@mail.gmail.com>

Hello Tomeu,

On 12/10/2025 2:50 PM, Tomeu Vizoso wrote:
> On Tue, Dec 9, 2025 at 10:31 AM Chaoyi Chen <chaoyi.chen@rock-chips.com> wrote:
>>
>> Hello Tomeu,
>>
>> On 12/9/2025 2:55 PM, Tomeu Vizoso wrote:
>>> On Tue, Dec 2, 2025 at 8:00 AM Chaoyi Chen <chaoyi.chen@rock-chips.com> wrote:
>>
>> [...]
>>
>>>
>>> This need was questioned during the review process, and during my
>>> stress testing I didn't find a need for core 0 to be treated
>>> specially. So it was considered unneeded complexity and the code was
>>> dropped.
>>>
>>
>> Oh, I just noticed that the commit comment in the devicetree still
>> contains a relevant description.
>>
>>> My testing involves running the supported models as a whole, and also
>>> their individual operations as individual tests. I run them in 8
>>> parallel processes, in batches so we have continuous bring up and down
>>> of clients.
>>>
>>> I'm a bit surprised that that testing worked stably but we have still
>>> failures in some setups.
>>
>> Could you please describe the failures that still exist? Thank you.
> 
> I was referring to the ones that Quentin reported when starting this thread.
> 

I believe this pmdomain patch can alleviate some of the problems [0]. 

However, the problem Quentin mentioned still exists. For example, if
there is an invalid device on core0, while core1 and core2 are valid, 
accessing the relevant data on core0 will cause problems. Quentin's
patch can fix this, but he doesn't seem to have time for it lately...

[0] https://lore.kernel.org/all/20251205064739.20270-1-rmxpzlb@gmail.com/

> Regards,
> 
> Tomeu
> 
> 

-- 
Best, 
Chaoyi

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

  reply	other threads:[~2025-12-10 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28 18:41 Issues with DRM_ACCEL_ROCKET (Oops, power-domain, probe-ordering) Quentin Schulz
2025-12-01  6:24 ` Chaoyi Chen
2025-12-02  7:00   ` Chaoyi Chen
2025-12-09  6:55     ` Tomeu Vizoso
2025-12-09  9:31       ` Chaoyi Chen
2025-12-10  6:50         ` Tomeu Vizoso
2025-12-10 10:47           ` Chaoyi Chen [this message]
2025-12-10 16:39             ` Tomeu Vizoso
2025-12-12 10:25               ` Quentin Schulz

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=e7b2ceaf-1fbd-4f02-9d75-be4feab724e3@rock-chips.com \
    --to=chaoyi.chen@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=quentin.schulz@cherry.de \
    --cc=sebastian.reichel@collabora.com \
    --cc=tomeu@tomeuvizoso.net \
    /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