All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
	daniel@ffwll.ch, airlied@linux.ie,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	jani.nikula@linux.intel.com, lyude@redhat.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 7/8] drm/display: Move HDMI helpers into display-helper module
Date: Wed, 20 Apr 2022 15:12:45 +0200	[thread overview]
Message-ID: <e0b7e721-9798-b9e6-d5f4-7fd0164a4e8f@suse.de> (raw)
In-Reply-To: <958ddd41-06eb-40b4-a88b-1ac712345fbf@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 2054 bytes --]

Hi

Am 20.04.22 um 14:26 schrieb Javier Martinez Canillas:
> On 4/20/22 14:21, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 20.04.22 um 14:02 schrieb Javier Martinez Canillas:
>>> Hello Thomas,
>>>
>>> On 4/20/22 13:08, Thomas Zimmermann wrote:
>>>
>>> [snip]
>>>
>>>> --- a/drivers/gpu/drm/bridge/synopsys/Kconfig
>>>> +++ b/drivers/gpu/drm/bridge/synopsys/Kconfig
>>>> @@ -1,6 +1,8 @@
>>>>    # SPDX-License-Identifier: GPL-2.0-only
>>>>    config DRM_DW_HDMI
>>>>    	tristate
>>>> +	select DRM_DISPLAY_HDMI_HELPER
>>>> +	select DRM_DISPLAY_HELPER
>>>>    	select DRM_KMS_HELPER
>>>>    	select REGMAP_MMIO
>>>>    	select CEC_CORE if CEC_NOTIFIER
>>>
>>> [snip]
>>>
>>>> +config DRM_DISPLAY_HDMI_HELPER
>>>> +	bool
>>>> +	select DRM_DISPLAY_HELPER
>>>> +	help
>>>> +	  DRM display helpers for HDMI.
>>>> +
>>>
>>> Maybe you mentioned already when we discussed it in v1, but could
>>> you please remember me why we need to select both symbols for the
>>> drivers, even when DRM_DISPLAY_HELPER is already selected here ?
>>>
>>> Or are select operations not transitive ?
>>
>> DRM_DISPLAY_HELPER enables the module itself. It's tristate.
>> DRM_DISPLAY_HDMI_HELPER, DRM_DISPLAY_DP_HELPER, etc are the individual
>> features of the helper module. Each is a boolean.  Drivers can enable
>> them according to their needs.  This split allows linking correctly in
>> all cases, even if some drivers are built-in and others are modules.
>> This didn't always work with the original patches.
>>
> Right, but that wasn't my question. I wondered why for example DRM_DW_HDMI
> Kconfig needs to select both DRM_DISPLAY_HDMI_HELPER and DRM_DISPLAY_HELPER
> since DRM_DISPLAY_HDMI_HELPER already selects DRM_DISPLAY_HELPER.
> 

Oh, well. You found a bug. It should be 'depends on' instead of 'select'.

Best regards
Thomas


-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2022-04-20 13:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 11:08 [PATCH v2 0/8] drm: Introduce display-helper library Thomas Zimmermann
2022-04-20 11:08 ` [PATCH v2 1/8] drm: Put related statements next to each other in Makefile Thomas Zimmermann
2022-04-20 11:08 ` [PATCH v2 2/8] drm: Rename dp/ to display/ Thomas Zimmermann
2022-04-20 11:08 ` [PATCH v2 3/8] drm/display: Introduce a DRM display-helper module Thomas Zimmermann
2022-04-20 11:08 ` [PATCH v2 4/8] drm/display: Split DisplayPort header into core and helper Thomas Zimmermann
2022-04-20 11:08 ` [PATCH v2 5/8] drm/display: Move DSC header and helpers into display-helper module Thomas Zimmermann
2022-04-20 11:08 ` [PATCH v2 6/8] drm/display: Move HDCP " Thomas Zimmermann
2022-04-20 11:08 ` [PATCH v2 7/8] drm/display: Move HDMI " Thomas Zimmermann
2022-04-20 12:02   ` Javier Martinez Canillas
2022-04-20 12:21     ` Thomas Zimmermann
2022-04-20 12:26       ` Javier Martinez Canillas
2022-04-20 13:12         ` Thomas Zimmermann [this message]
2022-04-20 13:22           ` Javier Martinez Canillas
2022-04-20 11:09 ` [PATCH v2 8/8] drm/display: Move SCDC helpers into display-helper library Thomas Zimmermann
2022-04-20 12:06   ` Javier Martinez Canillas

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=e0b7e721-9798-b9e6-d5f4-7fd0164a4e8f@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=javierm@redhat.com \
    --cc=lyude@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.