public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	linux-kernel@vger.kernel.org,
	DRI <dri-devel@lists.freedesktop.org>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: manual merge of the mali-dp tree with the drm-misc tree
Date: Thu, 3 Nov 2016 17:19:58 +0000	[thread overview]
Message-ID: <20161103171958.GA17265@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <20161025112044.1a866eaa@canb.auug.org.au>

On Tue, Oct 25, 2016 at 11:20:44AM +1100, Stephen Rothwell wrote:
> Hi Liviu,

Hi Stephen,

> 
> Today's linux-next merge of the mali-dp tree got a conflict in:
> 
>   drivers/gpu/drm/arm/malidp_planes.c
> 
> between commit:
> 
>   ea0e1ce20f73 ("drm/arm: Use per-plane rotation property")
> 
> from the drm-misc tree and commit:
> 
>   9ebb89762c30 ("drm: mali-dp: Refactor plane initialisation")
> 
> from the mali-dp tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.

Sorry for delay in answering, I was on holiday.

I have revamped the mali-dp tree and rebased it on the newer
version of drm-next (which includes the drm-misc change) and pushed the
updated patch in my tree.

Best regards,
Liviu


> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc drivers/gpu/drm/arm/malidp_planes.c
> index abaca03b9d36,9020c0d8399c..000000000000
> --- a/drivers/gpu/drm/arm/malidp_planes.c
> +++ b/drivers/gpu/drm/arm/malidp_planes.c
> @@@ -254,23 -284,33 +284,30 @@@ int malidp_de_planes_init(struct drm_de
>   		if (ret < 0)
>   			goto cleanup;
>   
> + 		drm_plane_helper_add(&plane->base,
> + 				     &malidp_de_plane_helper_funcs);
> + 		plane->hwdev = malidp->dev;
> + 		plane->layer = &map->layers[i];
> + 
> + 		/* Skip the features which the SMART layer doesn't have */
> + 		if (id == DE_SMART)
> + 			continue;
> + 
>  -		if (!drm->mode_config.rotation_property) {
>  +		/* SMART layer can't be rotated */
>  +		if (id != DE_SMART) {
>   			unsigned long flags = DRM_ROTATE_0 |
>   					      DRM_ROTATE_90 |
>   					      DRM_ROTATE_180 |
>   					      DRM_ROTATE_270 |
>   					      DRM_REFLECT_X |
>   					      DRM_REFLECT_Y;
>  -			drm->mode_config.rotation_property =
>  -				drm_mode_create_rotation_property(drm, flags);
>  +			drm_plane_create_rotation_property(&plane->base,
>  +							   DRM_ROTATE_0,
>  +							   flags);
>   		}
>   
> - 		drm_plane_helper_add(&plane->base,
> - 				     &malidp_de_plane_helper_funcs);
> - 		plane->hwdev = malidp->dev;
> - 		plane->layer = &map->layers[i];
>  -		if (drm->mode_config.rotation_property)
>  -			drm_object_attach_property(&plane->base.base,
>  -						   drm->mode_config.rotation_property,
>  -						   DRM_ROTATE_0);
>  -
> + 		malidp_hw_write(malidp->dev, MALIDP_ALPHA_LUT,
> + 				plane->layer->base + MALIDP_LAYER_COMPOSE);
>   	}
>   
>   	kfree(formats);
> 

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-11-03 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25  0:20 linux-next: manual merge of the mali-dp tree with the drm-misc tree Stephen Rothwell
2016-11-03 17:19 ` Liviu Dudau [this message]
2016-11-04  5:38   ` Stephen Rothwell
2016-11-04 15:48     ` Liviu Dudau
2016-11-04 16:55       ` Stephen Rothwell
2016-11-04 16:56         ` Liviu Dudau
  -- strict thread matches above, loose matches on Subject: below --
2018-03-05 23:52 Stephen Rothwell

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=20161103171958.GA17265@e106497-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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