Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: Dragan Simic <dsimic@manjaro.org>
Cc: Andy Yan <andyshrk@163.com>,
	linux-rockchip@lists.infradead.org,
	 dri-devel@lists.freedesktop.org, heiko@sntech.de,
	hjc@rock-chips.com, andy.yan@rock-chips.com,
	 maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
	airlied@gmail.com, daniel@ffwll.ch,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, javierm@redhat.com
Subject: Re: [PATCH] drm/rockchip: cdn-dp: Remove redundant workarounds for firmware loading
Date: Wed, 10 Jul 2024 09:13:17 +0200	[thread overview]
Message-ID: <20240710-smooth-hypnotic-raccoon-b91fba@houat> (raw)
In-Reply-To: <b6d630447e6c69e913b76650d910f895@manjaro.org>

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

On Tue, Jul 09, 2024 at 06:36:08PM GMT, Dragan Simic wrote:
> > > > > As I already wrote earlier, and as the above-linked discussions
> > > > > conclude, solving these issues doesn't belong to any specific driver.
> > > > > It should be resolved within the kernel's firmware loading mechanism
> > > > > instead, and no driver should be specific in that regard.
> > > >
> > > > IT would be good if it can be resolved within the kernel's  firmware
> > > > loading mechanism.
> > > 
> > > ... we'll need this as a systemic solution.
> > 
> > The general policy has been to put drivers that need a firmware as a
> > module, and just never build them statically.
> 
> I totally agree, but if Buildroot builds them statically and provides
> no initial ramdisk, we need a better solution than having various drivers
> attempt to implement their own workarounds.

Buildroot typically allows custom kernel configurations, so it's not
really "enforcing" anything like another distro does.

It is definitely targetted towards very stripped down systems, so I
guess building the drivers statically is a natural choice, but it works
fine with modules too.

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

  reply	other threads:[~2024-07-10  7:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 23:32 [PATCH] drm/rockchip: cdn-dp: Remove redundant workarounds for firmware loading Dragan Simic
2024-07-04  2:10 ` Andy Yan
2024-07-04 10:35   ` [PATCH] " Dragan Simic
2024-07-08  7:46     ` Andy Yan
2024-07-08  9:51       ` Maxime Ripard
2024-07-09  8:17       ` Dragan Simic
2024-07-09  9:10         ` Andy Yan
2024-07-09 10:10           ` Dragan Simic
2024-07-09 10:46             ` Andy Yan
2024-07-09 16:26               ` Dragan Simic
2024-07-09 11:09             ` Maxime Ripard
2024-07-09 16:36               ` Dragan Simic
2024-07-10  7:13                 ` Maxime Ripard [this message]
2024-07-10 14:22                   ` Dragan Simic
2024-07-11 10:51                     ` Maxime Ripard
2024-09-12 12:42 ` walker

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=20240710-smooth-hypnotic-raccoon-b91fba@houat \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=andy.yan@rock-chips.com \
    --cc=andyshrk@163.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=hjc@rock-chips.com \
    --cc=javierm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --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