public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Sui Jingfeng <sui.jingfeng@linux.dev>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2 2/3] drm/loongson: Introduce component framework support
Date: Mon, 27 May 2024 11:22:35 +0200	[thread overview]
Message-ID: <e6762978-d35f-4356-beac-bcb8b36d3ee2@web.de> (raw)
In-Reply-To: <20240526195826.109008-3-sui.jingfeng@linux.dev>

…
> However, the driver needs all of the subcompoments ready to use before

                                       subcomponents?


…
> goes with the PCIe master, sinch they has no dependency on exterinal

                             since they have no dependencies on external?


> modules.
>
> While the outputs drivers, such as encoders and conectors, may has some

            output?                               connectors, might have?


…
> if it need to do so, the master drvier won't bind until all submodules
…


Please improve your change descriptions considerably.

Regards,
Markus

  reply	other threads:[~2024-05-27  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-26 19:58 [PATCH v2 0/3] drm/loongson: Introduce component framework support Sui Jingfeng
2024-05-26 19:58 ` [PATCH v2 1/3] drm/loongson: Add a helper for creating child devices Sui Jingfeng
2024-05-26 20:47   ` Dmitry Baryshkov
2024-05-27  9:07   ` Markus Elfring
2024-05-26 19:58 ` [PATCH v2 2/3] drm/loongson: Introduce component framework support Sui Jingfeng
2024-05-27  9:22   ` Markus Elfring [this message]
2024-05-26 19:58 ` [PATCH v2 3/3] drm/loongson: Add dummy gpu driver as a subcomponent Sui Jingfeng
2024-05-27  9:45   ` Markus Elfring
2024-05-27  8:05 ` [PATCH v2 0/3] drm/loongson: Introduce component framework support 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=e6762978-d35f-4356-beac-bcb8b36d3ee2@web.de \
    --to=markus.elfring@web.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=sui.jingfeng@linux.dev \
    --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