public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Sun\, Jing A" <jing.a.sun@intel.com>, Takashi Iwai <tiwai@suse.de>
Cc: "airlied\@linux.ie" <airlied@linux.ie>, "Vetter\,
	Daniel" <daniel.vetter@intel.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel\@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"a.hajda\@samsung.com" <a.hajda@samsung.com>,
	Thierry Reding <treding@nvidia.com>,
	Emil Velikov <emil.l.velikov@gmail.com>
Subject: RE: [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".
Date: Tue, 11 Oct 2016 12:33:32 +0300	[thread overview]
Message-ID: <87lgxvqlg3.fsf@intel.com> (raw)
In-Reply-To: <C5AB7166D8288A4698415C150FD56DBA22E37ABB@SHSMSX103.ccr.corp.intel.com>

On Tue, 11 Oct 2016, "Sun, Jing A" <jing.a.sun@intel.com> wrote:
> It's needed that DRM Driver module could be removed and reloaded after
> kernel booting on the projects that I have been working on, and I hope
> such module type change could be accepted. Looks like Iwai has similar
> change request as well. Would you please review it and let us know if
> any concerns?

Looking at the Kconfig, selecting CONFIG_DRM_MIPI_DSI is against the
recommendations of Documentation/kbuild/kconfig-language.txt:

	select should be used with care. select will force
	a symbol to a value without visiting the dependencies.
	By abusing select you are able to select a symbol FOO even
	if FOO depends on BAR that is not set.
	In general use select only for non-visible symbols
	(no prompts anywhere) and for symbols with no dependencies.
	That will limit the usefulness but on the other hand avoid
	the illegal configurations all over.

Indeed, you may end up with CONFIG_DRM_MIPI_DSI=y and CONFIG_DRM=m,
which violates DRM_MIPI_DSI dependency on CONFIG_DRM. This is broken and
should be fixed. The suggested patch does *not* fix this issue.

Interestingly, I am able to reload i915 and drm. Our CI has tests for
i915 unload/reload, but does not check drm. In any case the config
problem should not impact the reloadability of i915.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center

  parent reply	other threads:[~2016-10-11  9:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10  7:31 [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate" Sun, Jing A
2016-10-10  8:28 ` Jani Nikula
2016-10-10  9:57   ` Takashi Iwai
2016-10-11  8:40     ` Sun, Jing A
2016-10-11  9:17       ` Andrzej Hajda
2016-10-11  9:33       ` Jani Nikula [this message]
2016-10-11  9:53         ` Andrzej Hajda
2016-10-12  3:08           ` Sun, Jing A
2016-10-12  6:51             ` Daniel Vetter
2016-10-12  9:04               ` Sun, Jing A
2016-10-12 10:52                 ` Jani Nikula
2016-10-12 11:28         ` Emil Velikov
2016-10-12 14:28           ` Jani Nikula
2016-10-20 13:20             ` Andrzej Hajda
2016-10-20 13:44               ` Jani Nikula
2016-10-21 12:19                 ` Daniel Vetter

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=87lgxvqlg3.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=jing.a.sun@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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