linux-kernel - Re: [PATCH v2] drm/of: Consider the state in which the ep is disabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 14 Oct 2020 09:48:43 +0800
From:   Kever Yang <kever.yang@...k-chips.com>
To:     Sandy Huang <hjc@...k-chips.com>, heiko@...ech.de,
        Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
        Maxime Ripard <mripard@...nel.org>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>
Cc:     huangtao@...k-chips.com, andy.yan@...k-chips.com,
        linux-rockchip@...ts.infradead.org,
        dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] drm/of: Consider the state in which the ep is disabled

Hi Maintainers,

     Does this patch ready to merge?

On 2020/7/7 下午7:25, Sandy Huang wrote:
> don't mask possible_crtcs if remote-point is disabled.
>
> Signed-off-by: Sandy Huang <hjc@...k-chips.com>
> ---
>   drivers/gpu/drm/drm_of.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_of.c b/drivers/gpu/drm/drm_of.c
> index fdb05fbf72a0..565f05f5f11b 100644
> --- a/drivers/gpu/drm/drm_of.c
> +++ b/drivers/gpu/drm/drm_of.c
> @@ -66,6 +66,9 @@ uint32_t drm_of_find_possible_crtcs(struct drm_device *dev,
>   	uint32_t possible_crtcs = 0;
>   
>   	for_each_endpoint_of_node(port, ep) {
> +		if (!of_device_is_available(ep))
> +			continue;
> +
>   		remote_port = of_graph_get_remote_port(ep);
>   		if (!remote_port) {
>   			of_node_put(ep);

Looks good to me.


Reviewed-by: Kever Yang <kever.yang@...k-chips.com>

Thanks,
- Kever