[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLXNMvaT3OU3Y-aYkH+KJA_g1QSOZNJHqvzt21WPy=6UJw@mail.gmail.com>
Date: Thu, 21 Oct 2021 19:56:54 -0700
From: John Stultz <john.stultz@...aro.org>
To: Shuosheng Huang <huangshuosheng@...winnertech.com>
Cc: Sumit Semwal <sumit.semwal@...aro.org>,
Liam Mark <lmark@...eaurora.org>,
Laura Abbott <labbott@...hat.com>,
Brian Starkey <Brian.Starkey@....com>,
Christian Koenig <christian.koenig@....com>,
linux-media <linux-media@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] dma-buf: heaps: init heaps in subsys_initcall
On Thu, Oct 21, 2021 at 6:49 PM Shuosheng Huang
<huangshuosheng@...winnertech.com> wrote:
>
> Some built-in modules will failed to use dma-buf heap to allocate
> memory if the heap drivers are too late to be initialized.
> To fix this issue, move initialization of dma-buf heap drivers in
> subsys_initcall() which is more earlier to be called.
Hey! Thanks so much for sending this out! I appreciate it!
So the change looks pretty straightforward to me, however, the
rationale for it is where we hit problems.
With the upstream kernel, there are not yet any modules that directly
allocate from dmabuf heaps. So in the context of the upstream kernel,
the reasoning doesn't make much sense.
Now, I know folks have their own drivers that want to allocate from
dmabuf heaps, but those haven't been submitted upstream yet.
So maybe can you submit those patches that need this along with this
change so it would make sense as part of a patch series? It would be
trivial to justify including this patch then.
thanks
-john
Powered by blists - more mailing lists