linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Maxime Ripard <mripard@kernel.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 16:22:12 +0200	[thread overview]
Message-ID: <a30067db11e586d8eb2c124abe32052a@manjaro.org> (raw)
In-Reply-To: <20240710-smooth-hypnotic-raccoon-b91fba@houat>

Hello Maxime,

On 2024-07-10 09:13, Maxime Ripard wrote:
> 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.

It all leads to a conclusion that we need better in-kernel support
for delayed firmware loading, instead of drivers implementing various
workarounds, for the layouts in which drivers are built statically
into the kernel image, but the required firmware blobs reside on the
root filesystem.

I'll start working on it, hopefully today. :)


  reply	other threads:[~2024-07-10 14:22 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
2024-07-10 14:22                   ` Dragan Simic [this message]
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=a30067db11e586d8eb2c124abe32052a@manjaro.org \
    --to=dsimic@manjaro.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=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).