public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 3/3] drm: clean cached display info
Date: Thu, 29 Dec 2016 16:22:04 +0530	[thread overview]
Message-ID: <460c863e-5a16-ef6f-786f-a5a0df714b2c@intel.com> (raw)
In-Reply-To: <fd46316a-b0d4-7c1b-38e1-283d4769c68e@synopsys.com>

Regards

Shashank


On 12/29/2016 3:35 PM, Jose Abreu wrote:
> Hi Shashank,
>
>
> On 29-12-2016 05:53, Sharma, Shashank wrote:
>> Regards
>>
>> Shashank
>>
>>
>> On 12/27/2016 3:07 PM, Daniel Vetter wrote:
>>> On Thu, Dec 22, 2016 at 10:21:25AM +0000, Jose Abreu wrote:
>>>> Hi Shashank,
>>>>
>>>>
>>>> On 21-12-2016 15:29, Shashank Sharma wrote:
>>>>> This patch adds a small helper function, which clears the
>>>>> cached
>>>>> information about a hot-pluggable display, from connector.
>>>>> On event
>>>>> This will run on event of a hot-unplug, keeping the
>>>>> connector's display
>>>>> info up-to-date, avoiding any errors due to invalid cached
>>>>> data.
>>>>>
>>>>> Cc: Jose Abreu <joabreu@synopsys.com>
>>>>>
>>>>> Suggested-by: Jose Abreu <joabreu@synopsys.com>
>>>>> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
>>>>> ---
>>>>>    drivers/gpu/drm/drm_probe_helper.c | 20 ++++++++++++++++++++
>>>>>    1 file changed, 20 insertions(+)
>>>>>
>>>>> diff --git a/drivers/gpu/drm/drm_probe_helper.c
>>>>> b/drivers/gpu/drm/drm_probe_helper.c
>>>>> index 7cff91e..9e97b45 100644
>>>>> --- a/drivers/gpu/drm/drm_probe_helper.c
>>>>> +++ b/drivers/gpu/drm/drm_probe_helper.c
>>>>> @@ -164,6 +164,18 @@ void
>>>>> drm_kms_helper_poll_enable_locked(struct drm_device *dev)
>>>>>    }
>>>>>      /**
>>>>> + * drm_helper_clear_display_info - clean cached display
>>>>> information for
>>>>> + * hot pluggable displays, on event of hot-unplug
>>>>> + * @connector: connector under event
>>>>> + */
>>>>> +void drm_helper_clear_display_info(struct drm_connector
>>>>> *connector)
>>>>> +{
>>>>> +    struct drm_display_info *info = &connector->display_info;
>>>>> +
>>>>> +    memset(info, 0, sizeof(*info));
>>>>> +}
>>>>> +
>>>>> +/**
>>>>>     * drm_helper_probe_single_connector_modes - get complete
>>>>> set of display modes
>>>>>     * @connector: connector to probe
>>>>>     * @maxX: max width for modes
>>>>> @@ -288,6 +300,14 @@ int
>>>>> drm_helper_probe_single_connector_modes(struct drm_connector
>>>>> *connector,
>>>>>            DRM_DEBUG_KMS("[CONNECTOR:%d:%s] disconnected\n",
>>>>>                connector->base.id, connector->name);
>>>>>            drm_mode_connector_update_edid_property(connector,
>>>>> NULL);
>>>>> +
>>>>> +        /*
>>>>> +         * Connector status change to disconnected, time to
>>>>> clean
>>>>> +         * cached display information
>>>>> +         */
>>>>> +        if (connector->status ==
>>>>> connector_status_disconnected)
>>>>> +            drm_helper_clear_display_info(connector);
>>>>> +
>>>> I don't know if this is the right place to do this because it is
>>>> a helper and I don't know if it is used by all the drivers. We
>>>> may need something more general that is always called when
>>>> probing modes, or force drivers that don't use the helper to use
>>>> the drm_helper_clear_display_info function. As I told you
>>>> before,
>>>> I'm new to dri-devel so we need more comments.
>>> Seems reasonable to me, since afaik all drivers do use the
>>> probe helpers.
>>> -Daniel
>> This was my understanding too. Jose, you think there would be
>> any drivers who dont use this probe ?
>> - Shashank
> I found only one driver that don't use this helper: vmwgfx. But,
> this driver does not seem to use EDID fields, it has a list of
> preferred video modes and manually adds these modes.
>
> So, I think it is safe to add this in the helper as long as
> future drivers that use EDID use this helper also. Maybe a small
> comment about this should be added in the helper declaration.
>
> Best regards,
> Jose Miguel Abreu
Sure, I will add a comment and publish a new patchset.
Shashank
>>>> Best regards,
>>>> Jose Miguel Abreu
>>>>
>>>>>            verbose_prune = false;
>>>>>            goto prune;
>>>>>        }
>>>> _______________________________________________
>>>> Intel-gfx mailing list
>>>> Intel-gfx@lists.freedesktop.org
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_intel-2Dgfx&d=DgIC-g&c=DPL6_X_6JkXFx7AXWqB0tg&r=WHDsc6kcWAl4i96Vm5hJ_19IJiuxx_p_Rzo2g-uHDKw&m=1G5dnBp7Y6VEifpEnDT2wKFoDRBXnxGXAnA-4883H74&s=y1M2ce128zpR_lBDPSgS_JGm-HoPIJjneK2s3tkrvyo&e=

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-12-29 10:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 15:29 [PATCH v3 1/3] drm: Create new structure for HDMI info Shashank Sharma
2016-12-21 15:29 ` [PATCH v3 2/3] drm: parse hf-vsdb Shashank Sharma
2016-12-22 10:10   ` Jose Abreu
2016-12-21 15:29 ` [PATCH v3 3/3] drm: clean cached display info Shashank Sharma
2016-12-22 10:21   ` Jose Abreu
2016-12-27  9:37     ` [Intel-gfx] " Daniel Vetter
2016-12-29  5:53       ` Sharma, Shashank
2016-12-29 10:05         ` Jose Abreu
2016-12-29 10:52           ` Sharma, Shashank [this message]
2016-12-21 16:15 ` ✓ Fi.CI.BAT: success for series starting with [v3,1/3] drm: Create new structure for HDMI info Patchwork
2016-12-22 10:02 ` [PATCH v3 1/3] " Jose Abreu
2016-12-22 11:56   ` [Intel-gfx] " Ville Syrjälä
2016-12-23  2:57     ` Sharma, Shashank

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=460c863e-5a16-ef6f-786f-a5a0df714b2c@intel.com \
    --to=shashank.sharma@intel.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox