From: Sui Jingfeng <sui.jingfeng@linux.dev>
To: Markus Elfring <Markus.Elfring@web.de>, dri-devel@lists.freedesktop.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v5 2/2] drm/loongson: Add dummy gpu driver as a subcomponent
Date: Wed, 31 Jul 2024 01:57:32 +0800 [thread overview]
Message-ID: <ce860f0b-2a05-451f-a2e5-90c00070370b@linux.dev> (raw)
In-Reply-To: <139afaab-343e-4cb4-83b7-2695129d27b1@web.de>
Hi,
On 2024/7/29 15:15, Markus Elfring wrote:
> …
>> the driver is loaded, drm/loongson driver still need to wait all of
> needs to wait on …?
>
>
> …
>> design. Therefore, add a dummy driver for the GPU, …
> Is there a need to reconsider the categorisation and usability descriptions
> another bit for such a software component?
For honoring the framework and testing the framework purpose.
The GPU can possibly be the master of the all sub-components, this
definitely need some extra
consideration and negotiation with the DC and the fake master device.
Depend on configuration
and user space expectation. The problem should be solved earlier.
> Regards,
> Markus
--
Best regards,
Sui
next prev parent reply other threads:[~2024-07-30 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 15:28 [PATCH v5 0/2] drm/loongson: Introduce component framework support Sui Jingfeng
2024-07-28 15:28 ` [PATCH v5 1/2] " Sui Jingfeng
2024-07-29 6:15 ` Markus Elfring
2024-07-29 6:40 ` Markus Elfring
2024-07-30 17:46 ` Sui Jingfeng
2024-07-30 18:16 ` Markus Elfring
2024-07-29 7:37 ` Markus Elfring
2024-07-30 17:39 ` Sui Jingfeng
2024-08-03 3:59 ` kernel test robot
2024-07-28 15:28 ` [PATCH v5 2/2] drm/loongson: Add dummy gpu driver as a subcomponent Sui Jingfeng
2024-07-29 7:15 ` Markus Elfring
2024-07-30 17:57 ` Sui Jingfeng [this message]
2024-07-29 7:48 ` Markus Elfring
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=ce860f0b-2a05-451f-a2e5-90c00070370b@linux.dev \
--to=sui.jingfeng@linux.dev \
--cc=Markus.Elfring@web.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@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 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.