From: Andrzej Hajda <a.hajda@samsung.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Daniel Vetter <daniel@ffwll.ch>, Takashi Iwai <tiwai@suse.de>
Cc: Thierry Reding <treding@nvidia.com>, dri-devel@lists.freedesktop.org
Subject: Re: Why drm-mipi-dsi is built-in only?
Date: Mon, 01 Aug 2016 20:04:55 +0200 [thread overview]
Message-ID: <579F8F47.2080305@samsung.com> (raw)
In-Reply-To: <87fuqotwrl.fsf@intel.com>
On 08/01/2016 03:59 PM, Jani Nikula wrote:
> Cc Andrzej, Thierry
>
> On Fri, 22 Jul 2016, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Fri, Jul 22, 2016 at 04:30:24PM +0200, Takashi Iwai wrote:
>>> Hi,
>>>
>>> is there any reason drm-mipi-dsi can't be a module? It's fixed as a
>>> built-in since its Kconfig is bool.
>> Probably none except embedded folks eshew modules ;-) Submit patch, I'll
>> apply.
> Possibly this?
>
> postcore_initcall(mipi_dsi_bus_init);
If I remember correctly, the only reason for this is to have mipi_dsi bus
registered before mipi_dsi drivers, which usually are registered
at module initcall. But maybe bus registration can be performed at
first mipi_dsi driver registration. This way we could modularize it.
Regards
Andrzej
>
>
> BR,
> Jani.
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-01 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 14:30 Why drm-mipi-dsi is built-in only? Takashi Iwai
2016-07-22 16:55 ` Daniel Vetter
2016-08-01 13:59 ` Jani Nikula
2016-08-01 18:04 ` Andrzej Hajda [this message]
2016-08-02 8:36 ` Thierry Reding
2016-08-02 10:47 ` Andrzej Hajda
2016-08-02 11:47 ` Thierry Reding
2016-08-02 11:55 ` Takashi Iwai
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=579F8F47.2080305@samsung.com \
--to=a.hajda@samsung.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=tiwai@suse.de \
--cc=treding@nvidia.com \
/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