dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Sun, Jing A" <jing.a.sun@intel.com>,
	"Vetter, Daniel" <daniel.vetter@intel.com>,
	Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".
Date: Wed, 12 Oct 2016 17:28:38 +0300	[thread overview]
Message-ID: <877f9dd4kp.fsf@intel.com> (raw)
In-Reply-To: <CACvgo53Q0_G-9KHaTFX=0NskFYnf9vOrV8arTw0gVqnZ8Jrm6w@mail.gmail.com>

On Wed, 12 Oct 2016, Emil Velikov <emil.l.velikov@gmail.com> wrote:
> On 11 October 2016 at 10:33, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> 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.
>>
> Jani, git log suggests you as the unfortunate author of the select
> DRM_MIPI_DSI/select DRM_PANEL hunks in i915 ;-)

/o\

As much as my present self would like to scold my past self for all his
mistakes, I have to remind myself that it is the mistakes that have
given me invaluable experience that my past self didn't have. I can only
hope my future self will have time to fix even a fraction of the
mistakes.

Anyway, as Andrzej pointed out, all configs that select DRM_MIPI_DSI
also depend on DRM, so this problem can't currently occur. Once dsi bus
un-registration gets addressed, we can turn DRM_MIPI_DSI into a tristate
config (i.e. a loadable module).

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-10-12 14:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C5AB7166D8288A4698415C150FD56DBA22E373B0@SHSMSX103.ccr.corp.intel.com>
2016-10-10  8:28 ` [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate" 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
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 [this message]
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=877f9dd4kp.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --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=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;
as well as URLs for NNTP newsgroup(s).